Repository navigation
Phase 2: implement immutable canonical records and deterministic identities #5
Description
Product outcome
Implement the smallest complete canonical-record slice required by sections 8 and 9 of SPEC.md. This issue does not implement mathematical proof authority or satisfy MathOS 1.0.
Acceptance criteria
- Stable object IDs use UUIDv7.
- Record versions are immutable and identified by
SHA256(schema_version || NUL || canonical_json(payload)). - Canonical JSON has deterministic key ordering, number handling, Unicode behavior, and whitespace, with golden vectors.
- The logical API uses exhaustive typed record kinds rather than arbitrary status strings.
- Create and version operations are transactional.
- Versioning requires an expected head hash and returns a structured conflict without overwriting newer work.
- Retrying the same idempotency key returns the existing result.
- Exact lookup by stable ID and version hash works.
- FTS5 receives the explicitly supplied searchable projection for committed heads.
- Actor attribution is persisted.
- Unit, property-style, integration, restart, and concurrent conflict tests exercise the real SQLite path.
- Implementation status and exact validation evidence are updated.
Trust checks
- There is no direct proved or disproved status mutation.
- Source claims and formalizations remain distinct record kinds.
- Old record versions cannot be rewritten.
- Canonical hashes exclude timestamps, paths, host names, and row IDs.
- Failed compare-and-swap writes do not change the head.
Out of scope
Typed graph-edge validation, run event chains, MCP transport, Lean verification, pedagogy, exports, and product pilots remain separate deliverables unless explicitly tested here.
Activity
Mnehmos commentedon Jul 19, 2026
Local implementation checkpoint completed on
feat/spec-driven-rust-rebuildat commitc8bbe2d(not yet pushed because the requiredghCLI is unavailable in the work environment).Validated locally:
This is not MathOS 1.0 completion. The issue remains open until the branch is published and remote CI verifies Linux, Windows, and the pinned Lean setup.
Mnehmos commentedon Jul 19, 2026
Remote preservation update: local commit
c8bbe2dwas replayed as remote commitd69f13don draft PR #11. The earlier local hash remains useful only for the ephemeral checkout;d69f13dis the durable GitHub identity.