8000 Phase 1: establish the governed Rust application skeleton · Issue #4 · Mnehmos/MathOS · GitHub
[go: up one dir, main page]

Skip to content

Phase 1: establish the governed Rust application skeleton #4

Closed

Description

@Mnehmos

Product outcome

Establish the first real production foundation required by SPEC.md. This issue does not represent MathOS 1.0 completion.

Acceptance criteria

  • The binding product specification exists at repository root as SPEC.md.
  • Previous Python work is identified as legacy migration input and cannot imply a 1.0 release.
  • One real Rust mcl binary loads configuration and uses the actual persistence path.
  • mcl init creates a SQLite database in WAL mode and a content-addressed artifact store.
  • The initial forward migration creates the required physical tables and FTS5 index.
  • Artifact writes are atomic, SHA-256 addressed, verified on read, and reject traversal.
  • mcl health and mcl doctor report structured, actionable results.
  • Mutation options include dry run, actor attribution, and idempotency keys where meaningful.
  • Unit and integration tests exercise the real database and artifact store.
  • CI checks formatting, warnings-denied lint, Rust tests, migration behavior, and retained legacy regression tests.
  • ADR, implementation status, blockers, and release checklist are maintained.
  • Exact validation commands and outcomes are recorded before commit.

Trust checks

  • No proof or research status mutation is introduced.
  • No model provider, arbitrary shell, raw SQL, or unrestricted file-write interface is introduced.
  • No placeholder handler is counted as implemented.
  • A missing Lean toolchain is reported honestly and does not become fake verifier success.

Out of scope

Formal claim records, Lean authority, MCP transport, product pilots, portable releases, and full 1.0 acceptance remain later acceptance criteria unless implemented and verified separately.

Activity

  1. Mnehmos commented on Jul 19, 2026

    @Mnehmos
    OwnerAuthor

    Remote preservation update: the governed product contract and Rust storage foundation are now on draft PR #11. Local commits 3f7a94f and a0565f3 correspond to remote commits b74f901 and a917061. The remote head tree is byte-identical to the local tracked tree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0