Skip to content

Qualify a Rust private-state reader with existing recovery semantics #251

Description

@0thernet

Implement a product-owned Rust state-kernel executable for the existing schemaVersion 1 read-file and read-file-if-present operations. Preserve exact root marker, private ownership, directory/leaf identities, synchronous bounded responses, and definitely-orphaned quarantine maintenance currently performed during reads.

Keep TypeScript production routing and all existing write/CAS owners unchanged until independent parity review, native macOS/Linux qualification, immutable binary/package provenance, source-closure admission and current Required CI pass. No provider/auth/data migration is included.

Qualification uses synthetic isolated roots and adversarial filesystem/child schedules; reads are explicitly maintenance-capable. Windows, remaining state operations, default routing and the CLI five-asset distribution change remain separately named activation gates. A fixture-only executable is an implementation increment, not completion of the production migration.

Activity

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions