Documentation
Make private knowledge callable.
Start with a task, define the boundary, and follow one bounded request from intent to record, then manage its ongoing access.
Start with a complete example
Open Private code risk to inspect a task, its accepted input, allowed outputs and policy. Then open it in the Console, edit the sample input and run it.
The result follows the input. A clean snippet and a dynamic execution pattern produce different bounded classifications. Submitted code is treated as text and is never executed.
Define the boundary
A Capability names a useful task. A Cell defines the accepted inputs, allowed outputs, withheld fields, lifetime and limits. Broker, Guardian and Vault are the cooperating roles that match, check and process the task.
Manage cumulative disclosure
Repeated related calls can reveal more than a single answer. Explore the public sample budget model, output filtering, expiry and revocation in the Console. Browser sample state is not a global authorization boundary.
Inspect one actual record
A successful run creates a Proof Capsule covering its redacted intent, compiled public policy, permitted result, trace and budget change. Copy or download it, verify its hashes, and replay the same recorded run.
Publish as an owner
Compile and review a Manifest before using the owner workspace. Wallet connection, signed login, publication and revocation are separate actions. The server checks owner authorization and the public directory reads this deployment's actual registry records.
Examples stay separate from Published entries. A failed registry request shows a specific error and a retry action. It does not turn a browser sample into a public registration.
Value follows accepted work
The protocol organizes fees around accepted work and inspectable evidence. This site implements policy declarations and local samples; it does not perform payments or financial settlement.
Notes
Follow the project notes for explanations of the mechanism, share a bounded example for review, and use these protocol documents as the common vocabulary for capability interfaces and evidence.
Execution details
The six built-in cases use public deterministic rules in your browser. They demonstrate callable interfaces, boundary checks, sample budgets and record integrity. They do not provide a private backend, trusted execution attestation or proof that an unseen private computation is correct.
Explore the Manifesto, Cells directory, or project notes for more context.