lean

Continuity Admission Historical Name

The private excavation and qualification campaign used the path someone/Someone.lean and namespace Someone. After exact public-transfer ratification, the public integration rename gate moved that one authoritative implementation to:

The historical name remains in frozen source manifests and campaign records because those documents identify exact private Git objects. It is provenance, not a second public implementation or compatibility namespace.

The public claim is exactly:

Continuity.Admission provides identity-bound continuity admission on the reachable fragment.

It does not establish authenticated identity, durable revocation, substrate rebinding, retained route history, typed refusal, obligations, or operational-Continuity correspondence.

The machine-readable declaration correspondence is docs/V15-CONTINUITY-ADMISSION-CORRESPONDENCE.tsv. It binds every one of the 1,005 source and qualification declarations to its public name and records type, proof/value, and axiom identity after reversing only the namespace alpha-renaming.