What does OpenScion
actually implement?
A source-checked snapshot of the independent community implementation, with a clear line between working code and the architecture it aims to build.
Capability matrix
| Capability | Status at this revision | What that means |
|---|---|---|
| Content-addressed objects & changesets | Implemented | Basic engine and validation exist. |
| Directory import, commit & clone | Locally checked | Full and single-directory clone round-trips passed. |
| Compare-and-swap refs | Locally checked | A stale writer was refused. Automatic rebase is not implemented. |
| Persistent repository storage | Not implemented | Objects, history and refs are lost on process restart. |
| HTTP authentication & access control | Not implemented | The tested ref routes accepted requests without credentials. |
| History, diff & ancestry queries | Planned | Listed as the next delivery phase. |
| Server-side rebase & landing | Planned | No complete concurrent landing workflow in this revision. |
| Git history ingestion & cache tiers | Planned | Directory import is not a migration of Git history. |
What we checked locally
We ran the existing Rust workspace tests and a small functional smoke check against generated files on loopback HTTP. Complete and sparse clones, commit and re-clone, and stale-write rejection worked. Unauthenticated ref reads and writes returned HTTP 200. After restarting the process, the prior main ref returned HTTP 404.
The check used debug binaries. It was not a performance benchmark, a production deployment, or a complete security audit. Read the machine-readable test record.
Architecture is not an implementation inventory
The project describes a client → node daemon → regional cache → authoritative server design. Those tiers should not be assumed to exist in this snapshot. The HTTP layer currently wraps one in-memory repository with a process-wide read/write lock.
Review the pinned roadmap, HTTP router, and repository engine. Re-check a later revision before making an adoption decision.
Choose your next step
For the complete review, read OpenScion status. For operational requirements, read the hosting evaluation. To compare performance fairly, use the benchmark methodology.