Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 13 additions & 10 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

A next-generation version control system built around a snapshot-and-tag model
(Jujutsu-inspired), with per-file permissions, native committed secrets, and
in-memory clones as the long-term thesis. Across 33 shipped phases, this
in-memory clones as the long-term thesis. Across 34 shipped phases, this
repository now proves that thesis end to end:

1. **In-memory virtual worktrees** (the agent wedge) — fork N parallel worktrees
Expand All @@ -11,17 +11,19 @@ repository now proves that thesis end to end:
2. **Native committed secrets** — env vars / keys committed into repo state,
encrypted at rest and in transit, decrypted only in an authorized execution
context. **Implemented (Phase 2).**
3. **Per-file permissions** — individual paths encrypted to a chosen set of
recipients (randomized sealing since Phase 33, with dual-read of older
convergent ciphertext), merged/replayed/revoked/rewrapped without ever
writing plaintext to the object store. **Implemented (Phase 7, hardened
through Phases 15-17 and 33.)**
3. **Per-file and per-branch permissions** — individual paths encrypted to a
chosen set of recipients (randomized sealing since Phase 33, with dual-read
of older convergent ciphertext), merged/replayed/revoked/rewrapped without
ever writing plaintext to the object store; and whole **private branches**
(Phase 34) whose commits, trees, file paths, and messages are all sealed —
opaque to non-recipients until an atomic `sc branch publish`. **Implemented
(Phase 7, hardened through Phases 15-17 and 33; per-branch in Phase 34.)**
4. **A full persistent collaborative VCS** on top of those three pillars:
durable `.sc/` repos, branches, three-way merge, history editing
(cherry-pick/rebase/amend/undo), durable multi-invocation agent sessions,
signed commits with session-transcript provenance, sparse and partial
checkouts, and local/ssh/HTTP+TLS/Git network transports. **Implemented
(Phases 3-33.)**
(Phases 3-34.)**

The system builds on / interoperates with Git rather than replacing it: it
imports an existing Git repo's `HEAD` in-process (via `gix`), exports history
Expand Down Expand Up @@ -143,9 +145,10 @@ auto-merge, a commit-time secret scanner, secret/permission lifecycle
(rotation, escrow, revocation tombstones, bulk rewrap), signed commits with
sealed session-transcript provenance, sparse and partial checkouts, and local,
ssh-native, sc-native HTTP/TLS (with bearer-token auth and listener resource
limits), and Git (including hosted GitHub) network transports. All 33 phases
are implemented and tested; `demo/` holds 25 independent end-to-end proofs,
one per major capability. Remaining follow-ons (transparent lazy-fetch,
limits), and Git (including hosted GitHub) network transports, plus private
branches sealed to a recipient set until publish. All 34 phases are
implemented and tested; `demo/` holds 26 independent end-to-end proofs, one
per major capability. Remaining follow-ons (transparent lazy-fetch,
per-case gap-tolerant merge on partial clones, CA-path validation alongside
TOFU pinning, rotate-for-paths, and similar hardening items) are tracked in
[ROADMAP.md](ROADMAP.md)'s Deferred section rather than being open MVP scope.
2 changes: 1 addition & 1 deletion docs/THREAT-MODEL.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ This document consolidates, in one place, the **deliberate security boundaries**
of src-control's cryptographic features — the things it does *not* defend against
by design. They are drawn from the per-phase ADRs (linked below); this page
exists so a newcomer evaluating whether to trust real data to the system does not
have to read 40 ADRs to find the caveats.
have to read 44 ADRs to find the caveats.

> **Status: pre-1.0, not independently audited.** These are MVP implementations
> reviewed by the project's own process only. Do not commit production secrets to
Expand Down
Loading