Private knowledge. Public capability.
Publish a purpose
Private knowledge often has value because it can answer a precise question. A codebase can support a risk classification. A policy can support a bounded decision. A history of operations can help classify an incident pattern.
The useful interface does not have to be a copy of the source. It can be the task, its accepted inputs, its permitted result and the conditions under which it may run.
OCLITH calls that idea Private Capability Liquidity: make the usefulness of knowledge discoverable, callable and composable while its owner continues to control the source.
A capability and its Cell
A capability names a purpose. A Cell defines the boundary around that purpose: which input it accepts, which output it may return, which content it must withhold, how long a request remains valid and how repeated calls affect disclosure.
This distinction gives callers a clear interface and gives owners a policy they can inspect and change. It also makes the execution boundary a concrete engineering obligation. A Manifest is a declaration. The execution environment must enforce it.
Begin with a bounded question
The private-code-risk example accepts a code snippet and returns a limited classification. Its public rules check explicit text patterns. The example does not execute the submitted code or claim to be a complete audit.
Open it in the Console, change the input and compare the result. Then inspect the requested fields, policy version and record. A different input should lead to a different permitted answer, while the declared boundary remains visible.
Keep the control with the owner
Publishing a capability is different from giving a caller unrestricted access. Future access can expire or be revoked. Prior permitted outputs and their records remain inspectable.
The current site demonstrates that lifecycle with public browser samples and owner registered declarations. It does not turn frontend sample rules into private execution. That separation is part of making the mechanism understandable and testable.