Roadmap

Jump to bottom Edit New page

hyperpolymath edited this page May 27, 2026 · 1 revision

Roadmap

Canonical source: ROADMAP.adoc in main. The wiki view summarises the key milestones.

Near term (3–6 months)

Registry growth

Register the remaining hyperpolymath Julia packages as they reach a published 0.1.0 tag.
Backfill semver compat ranges as upstream packages stabilise.

Tooling

Adopt the standards changelog-reusable.yml workflow so CHANGELOG.md is generated from conventional commits.
Promote the Idris2 contract-testing harness from ad-hoc to a reusable pattern that validates Registry.toml correctness automatically.

Documentation

Wiki pages for: registry usage, package authorship, governance, release process. ✓ (this is what you're reading)
Inline cross-links between README package table, individual package READMEs, and Registry.toml repo URLs.

Medium term (6–12 months)

Mirror surface

Activate the mirror workflow to push to GitLab, Codeberg, Sourcehut, Disroot, Gitea, Radicle. Workflow already wired via standards mirror-reusable.yml; per-forge toggled via repo-level vars.<FORGE>_MIRROR_ENABLED Actions variables.

Quality gates

Verify every registered package carries: SPDX header, REUSE-compliant LICENSES/, OpenSSF Scorecard ≥ 7, no banned-language files.
Registry-level CI job that fails Registry.toml additions whose upstream fails the above.

Federation

Publish the registry as a JuliaHub-compatible mirror so packages can be discovered via standard Julia tooling.

Long term (12+ months)

Verified registry

Every package entry carries an attestation of its build provenance (SLSA Level 3+).
Registry.toml is append-only with cryptographic signing of the registry head — supports offline verification of "this version was in the registry at this time."

Cross-language indexing

Aggregate the hyperpolymath per-language registries (Idris2, Rust, OCaml, Coq, Lean, Agda, Haskell, Zig, Elixir, Julia) behind a single discovery surface, driven by .machine_readable/6a2/ECOSYSTEM.a2ml.

Non-goals

Not a fork of JuliaRegistries/General. Mature, externally-relevant packages belong in General. This registry is the proving ground.
Not a host of package source code. Packages live in their own repos; Registry.toml repo URLs are the source of truth.

How to influence the roadmap

Open an issue with the feature-request template.
For larger directional shifts, discuss in the Discussions section before opening a PR.
ADRs (under docs/decisions/) document accepted strategic shifts.