Start
Your first workspace
Attach a directory read-only, inspect what Intralock found, and build the first catalog without a write.
Documentation
Read the system before you run it.
These pages follow the same order as the specification: what the product guarantees, how the workspace is laid out, what each interface exposes, and what evidence a release must produce. Start with a read-only directory; change nothing until you understand the approval path.
Concepts
Architecture
Filesystem truth, reconciled catalog, domain services, and interface parity.
Concepts
Workspace format
Manifest, reserved paths, identity, lock snapshots, and homepage regions.
Build
CLI reference
Commands, global flags, JSON output, and exit codes for scripting.
Build
REST API
Versioned routes, logical IDs, idempotency, preconditions, and problem details.
Build
MCP & agents
Tool catalog, resources, prompts, tasks, and the boundary between guidance and authority.
Operate
Security model
Trust zones, traversal containment, prompt injection, and the four-object approval chain.
Operate
Backup & restore
Snapshots, integrity checks, export formats, and recovery rehearsal requirements.
Reference
Master specification
The canonical contract: 79 sections, acceptance catalog, and delivery phases.
Reading map
Five paths through the spec.
If you are evaluating the product, read Parts A and D. If you are implementing it, read B, C, and F. If you are operating it, read G and H. If you are testing conformance, read Part J. If you are deciding what to build first, read Part K.
| Path | Sections |
|---|---|
| Evaluate | 1–8 (product), 25–30 (interface & design) |
| Implement | 9–24 (format, data, graph), 31–50 (authority, protocols) |
| Operate | 51–64 (security, reliability, performance, release) |
| Conform | 63–64, Part J capability catalog, 76 (definition of done) |
| Sequence | 66–72 (phase plan), 79 (canonical implementation order) |
Status. Version 1.0.0 is a proposed canonical design. Nothing on this site claims a shipped release; the pages describe required behavior and the evidence a conforming implementation must produce.