docs(state): reconcile STATE.a2ml with reality — operational, not 0% (G26) - #43
Merged
Merged
Conversation
…nal, not 0% (G26)
STATE.a2ml claimed `completion-percentage = 0` and `phase = "In development"`,
which is false: the registry has 37 packages registered (Registry.toml) and a
green validation gate (ci/validate.jl + registry-validate.yml). Updated to
`completion-percentage = 85` / `phase = "operational"` with an inline note of
the residuals (AutoMerge automation = G23; identity canonicalization = G22), and
refreshed last-updated.
The `project`/`name` fields are left as the pre-rename identity
("HyperpolymathRegistry") on purpose: the functional registry name is
"JuliaProfessionalRegistry" and the repo slug is "julia-professional-registry",
and reconciling the three is a CLADE-level identity rename that must be
coordinated with gv-clade-index (G22) — not swept in one file in isolation. An
inline NOTE records that.
Verified: STATE.a2ml still TOML-parses (Julia stdlib) and retains its identity
field; the 37-package count is from Registry.toml.
hyperpolymath
marked this pull request as ready for review
July 1, 2026 11:48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
STATE.a2mlclaimedcompletion-percentage = 0andphase = "In development"— false for a registry that has 37 packages registered and a green validation gate. This reconciles the state checkpoint with reality (G26). It deliberately does not touch the project identity name (that's the separate G22 identity rename — see note below).Changes
.machine_readable/6a2/STATE.a2ml:completion-percentage0 → 85,phase"In development" → "operational", refreshedlast-updated, with an inline note of the residuals (AutoMerge automation = G23; identity canonicalization = G22).project/namefields are left as the pre-rename identity (HyperpolymathRegistry) rather than swept in isolation.RSR Quality Checklist
Required
.envfiles includedAs Applicable — Registry Changes
As Applicable — Documentation / Infra Changes
.machine_readable/6a2/STATE.a2mlupdated (project state changed)Testing
julia -e 'using TOML; TOML.parsefile(".machine_readable/6a2/STATE.a2ml")'→ parses OK;completion-percentage=85,phase=operational, identityprojectfield retained.37 packagescount ground-truthed fromRegistry.toml [packages].Flagged separately (G22 — identity rename, NOT in this PR): the registry has three names in play —
JuliaProfessionalRegistry(Registry.toml, canonical),HyperpolymathRegistry(CLADEcanonical-name+ ~48 doc refs +[forges]pointing at a nonexistenthyperpolymath/HyperpolymathRegistry), andjulia-professional-registry(repo slug). Canonicalizing is a CLADE-level identity rename whose authoritative record lives ingv-clade-index(out of this session's scope), so it needs owner coordination rather than a unilateral in-repo sweep.🤖 Generated with Claude Code
Generated by Claude Code