# Agents can propose. Authority lives elsewhere. 2ok is a domain-neutral Rust foundation for making an agent's proposed work reviewable, authorizable and independently enforceable. The resource—not the agent—makes the final decision to act. Early-stage software. Two experimental Rust foundations; no live protected-execution service, authenticated approvals or production security guarantee. - 01 Propose An agent drafts an intent and an exact, reviewable change. - 02 Verify Independent evidence is checked against the intended revision. - 03 Authorize A qualified actor and policy grant narrowly scoped permission. - 04 Enforce independent authority An independent resource verifies permission and produces a receipt. Separation is a requirement of the proposed system, not a property granted by this website. ## Agents suggest changes Not trusted just because a model generated them. ## Independent systems decide Approval records and policies cannot replace enforcement. ## Outcomes must be observed A trace or simulation alone is never a verified effect. ## Composable governance. Explicit trust boundaries. Implement a small foundation before claiming a complete platform. Status reflects reviewed public work, not unfinished branches. ### Identity & delegation Validated principal records and narrowing delegation scopes; no credential issuer, hosted identity provider or runtime authorization. ### Evidence & digests Bounded evidence records, providers and versioned digests; does not establish truth, approval or protected execution. ### Specifications Immutable reviewed revisions, exact change proposals and versioned contracts. Work outside main does not advance public status. ### Approval & policy Exact-resource decisions, independent policy and verifiable human approvals. No operational approval service is exposed. ### Protected execution One-use resource-scoped leases, resource-side re-verification, receipts and uncertain-outcome recovery. ### Review checkpoints Durable task pause, independent review and safe resume; queuing a task never grants execution authority. ## Distinct profiles, explicit authority. ### Development / YOLO Normal local agent edits, builds and tests remain fast. Shadow policy is advisory; unrestricted agents on one host are not contained. ### Commissioning / engineer-directed Time-limited, target-scoped engineer sessions support rapid iteration. Engineer access never automatically delegates credentials to agents. ### Managed / production Independently controlled endpoints own credentials, verify execution leases, reject replay and record receipts. Approval is not functional safety. ## One architecture, three placements. Proposed deployment patterns, not currently shipped services. Split processes only for an actual trust or operational boundary. ### Local Windows + WSL2 + Docker Proposed APIs, identity, PostgreSQL, policy and workers in containers; native connector where needed. One laptop cannot resist full host compromise. ### Customer on-premises Same interfaces with locally managed identity and audit, independently administered connector host and segmented protected-resource network. ### Cloud + on-premises edge Core governance in the cloud when useful; protected credentials, connectivity and authoritative execution stay behind the customer-controlled edge. ## Prove one portable end-to-end slice. No second standalone platform or copied consumer backlog. Start with a synthetic resource and validate strong enforcement at the resource, not the agent prompt. - 01 Now Standalone Rust identity/delegation and evidence slices; explicit publication and boundary tests. - 02 MVP Synthetic proposal → independent verification → exact engineer approval → trusted dummy connector → receipt; reject replay/mismatch/uncertain effects. - 03 Next Immutable specification revisions and small event-backed policy/transaction API, reusing mature policy/identity/storage components. - 04 Then Passkey-backed approval and durable task pause/resume, with authoritative verification outside the agent. - 05 Proof Move connector onto independently managed hardware without changing the versioned protocol. ## Help agents discover the design, not execute it. 7 public, domain-independent topics share one manifest for standalone HTML, Markdown, llms indexes, sitemap and discovery catalog. Compatible browsers may expose optional read-only WebMCP tools for search, capabilities, roadmap, profiles and site map. The website never approves transactions, receives credentials, opens local resources or starts remote execution. Local, read-only search of the rendered site and public docs, sharing the WebMCP index. No query is sent to a server. ## Source first. Claims second. Inspect the standalone Rust foundations and their tests. Operational APIs, real human approvals and protected execution are future work and require separately controlled infrastructure. ## Public links - [Understand the architecture ↗](/architecture/) - [What is actually implemented ↗](/status/) - [View source ↗](https://github.com/x2ot/2ok) - [Full roadmap ↗](/roadmap/) - [Core-owned roadmap ↗](https://github.com/x2ot/2ok/blob/main/docs/migration-roadmap.md) - [Proposed service interfaces ↗](/interfaces/) - [agents · current For agents 2ok is reusable, domain-independent governance building blocks; a website is not an approval server.](/overview/) - [deployment · design Deployment topologies One versioned API across laptop, on-prem and cloud/edge placements, with candid trust assumptions.](/deployment/) - [security · design Operating profiles and ergonomics Development speed, engineer-supervised sessions and managed enforcement are distinct modes.](/profiles/) - [Agent entry point](/for-agents/) - [Machine-oriented Markdown](/for-agents.md) - [Compact index](/llms.txt) - [Expanded public context](/llms-full.txt) - [Discovery catalog](/.well-known/ai-catalog.json) - [HTML site map](/sitemap.xml) Status: experimental. This public page is informational, not operational authority.