private knowledge can be useful without leaving.
A document, model, policy or operating history can answer a task without becoming an unrestricted download. OCLITH starts with that distinction. Publish what the knowledge can do, define what a caller can ask, and keep the original material under the control of its owner.
three roles. one bounded call.
Broker matches the capability and minimizes the request. Guardian checks permission, time, disclosure and budget, then checks the output again. Vault processes the task where its source is controlled. These roles cooperate around work; they are not product tiers or financial products.
a Cell makes the boundary explicit.
A capability names a clear purpose: check, compare, classify, select or score. Its Cell declares accepted input, allowed result fields, withheld content, expiry and invocation limits. An owner publishes an interface and a rule, rather than the raw source. Callers can inspect the boundary before making a request.
one answer is not the whole disclosure.
Related calls can accumulate information. Privacy Budget therefore considers call history, requested detail and source overlap. The Console uses a public sample scoring model to mask fields, reduce precision or reject a call. This is a disclosure assessment example, not a differential privacy guarantee. Production limits must be enforced by the execution service.
a record connects the actual work.
A Proof Capsule relates a request, policy, allowed result, trace and budget change. Recalculating its SHA-256 digests checks covered content integrity. It does not prove that an unseen source is authentic, a computation is correct, a TEE was used or a payment settled. Evidence should state exactly what can be checked.
let value move. keep the source.
Private Capability Liquidity is the ability to discover, invoke and compose useful work around private knowledge. A permitted answer or classification can flow to the next task while ownership stays with the source holder. What becomes liquid is the usefulness of the knowledge, within an explicit boundary.
valid work comes before fees.
Declare a capability. Accept a bounded task. Check the agreed result and its record. Organize fees around work that satisfies the contract. Rejected or nonconforming work does not enter the corresponding successful settlement flow. This site explains that economic model; it does not perform payments, payouts or token settlement.
a declaration needs an enforcing environment.
Network access, memory restrictions and disclosure rules describe an intended boundary. A private execution adapter must enforce that boundary. Frontend sample rules are visible to the caller. Browser state is not global authorization. A digest is not a confidentiality guarantee. Useful systems keep these distinctions visible instead of inventing assurance.
discovery. execution. evidence.
Discovery exposes the task and its public policy. Execution handles only the information needed for a bounded request. Evidence describes the outcome without becoming another raw data channel. The Cells directory separates built-in examples from real published declarations, and local records stay distinct from network activity.
follow the call. stop at the boundary.
Intent validates the request. Broker reduces and matches it. Guardian checks the policy. Vault performs the task. Guardian validates its candidate output. Capsule records the permitted result. A failure stops at the stage that rejected it. Replay presents the same record and does not spend the budget or create a new identity.
close access. keep the record.
An owner controls the declaration and future access. A signed owner session authorizes publication and revocation. Registry revocation changes the entry’s discovery state; execution services must enforce it for new work. Revocation does not delete private source material, erase an earlier permitted answer or prove that every running task has stopped. Prior records remain inspectable.
make it callable. make it inspectable.
Begin with a complete Manifest and a reproducible example. Edit the request, compile the rule, run the sample and examine its actual trace. Copy, export and verify the corresponding Capsule. The current Console implements those actions with public deterministic browser rules. Private backends, runtime attestation and payment services remain separate integrations, each requiring its own evidence.