Spock roadmap — milestone tracker

[softmarshmallow]

Note

This issue originally belonged to an earlier, never-built incarnation of this repository. It is intentionally retained and repurposed as Spock's pinned issue #1.

This is a navigation-level milestone tracker, not the language specification and not a promise of dates. Current behavior is defined by docs/spec/; design history and proposed changes live in docs/rfd/. The sequencing record is RFD 0009.

Shipped foundation

• Rust parser, checker, contract IR, embedded SQLite runtime, REST, and GraphQL table slice (RFD 0008)
• Deliberate fn surface, named refusals, read/write polarity, and explicit unchecked escape boundary (RFD 0011, RFD 0012)
• Contract-owned TypeScript/GraphQL generation and implemented value constraints (RFD 0010, RFD 0013)
• Prototype actor seam, Studio, and contract-carried documentation (current v0 specification, RFD 0015, RFD 0016)
• Governed file storage and the shared filtered-read query layer (RFD 0018, RFD 0021)
• Installable multi-platform npm distribution and the initial one-command Spock + Uhura framework host (RFD 0020, RFD 0022)

Active checkpoints

Language and runtime

• Design, ratify, and ship filtered/bulk write surfaces on the existing predicate IR (RFD 0021)
• Settle the auth milestone beyond the current development actor/impersonation seam (RFD 0009, track 7)
• Resolve the long-term development reload and state-continuity model; retain the implemented backend-pinned interim policy until then (RFD 0023)
• Decide the v1 horizon through RFDs: policy/RLS, Postgres engine-flip timing, and view (RFD 0009, track 10)
• Decide the reproducible generated-seed-asset workflow (RFD: deterministic generated assets for storage-backed seeds #8)

Framework and deployment

• Study and define self-hostable Spock artifacts and user-owned CI deployment across the web, authority, and durable-state boundaries (RFD study: self-hostable artifacts and user-owned deployment #19)

Community and governance

• Land the governance bootstrap: conduct rules, contribution routing, the Language Design Committee, working groups, prospective RFD stages, and governed review (887fc51)
• Seat a second independent voting committee member, ending founder-only language decisions
• Seat a third voting committee member, ending the bootstrap provision
• Establish an independent confidential conduct-reporting and appeal path

Tracking rules

• A checked item means the result is verifiably shipped; it does not make this issue normative.
• An unchecked item is a checkpoint, not an accepted design, staffing promise, release date, or implementation authorization.
• Language changes still require the repository's RFD process, and current behavior still comes from the specification.
• Mark implementation complete only when code, conformance tests, user documentation, and affected specifications agree.
• Priorities may change when dogfood or working-group evidence changes the plan; update the linked durable record with the reason.

Related trackers

• RFD: deterministic generated assets for storage-backed seeds #8 — deterministic generated assets for storage-backed seeds
• Contributor guide: run the Spock-backed Instagram demo #10 — living contributor guide for the Spock-backed Instagram demo