Private Capability Liquidity

Private data.Public capability.

Make private knowledge useful to others. Define what they can ask, control what can leave, and keep the source under your control.

EXAMPLE A bounded call, seen from the outside.
01 / PUBLIC INTERFACEv1.1.0

Private code risk

Check code for explicit risk patterns.

Array total
function total(items) {
  return items.reduce((sum, item) => sum + item.price, 0);
}
Requested
verdict · category · disclosure
Request lifetime
120s
Expires (ET)
—
OWNER-CONTROLLED CELL◇ Controlled access
Private sourcefixed inside
◇ Request arrives3 declared · 0 permitted
0° · Front100%
02 / PERMITTED ANSWER

Only permitted fields leave.

◇

Preparing the example.

Record after releaseRequest · policy · result · trace
Execution details

One saved example supplies the request, policy, result and Capsule. Playback and stage selection preserve its ID, time, digests and disclosure history. The animation uses presentation time. Open Console to run a new request.

Capabilities

From private knowledge to a useful answer.

One scenario. A public interface, a bounded question, and a permitted answer.
Interface declarationv1.1.0

private-code-risk

IN
code-text
Retained source

Internal risk experience

OUT
verdictcategorydisclosure
Withheld
sourcecredentialsinternalRulesmemory
120s request lifetimeOwner controlled

Define the capability

Declare a task interface with accepted inputs, allowed outputs, forbidden fields and a clear access lifetime.

RequestArray total
code-text
function total(items) {
  return items.reduce((sum, item) => sum + item.price, 0);
}
Illustrative request checksScopependingEntrypendingOutputpending
Request only
verdictcategorydisclosure

Check code for explicit risk patterns.

Choose a capability

Ask a bounded question

Choose a capability, send a limited task, and let the request and output checks decide what can return.

Allowed answerPreparing
ResultPreparing… Allowed fields only
Use the answer to

decide what needs a code review.

Inspect the permitted answer

Read the actual output fields, policy version, disclosure change and trace. Integrity checks cover the recorded content.

Example
Execution details

These views share one public sample and its saved result. Playback creates no new call or ledger entry. Inspect opens the corresponding Capsule with its saved policy, time and digests.

Capability scenarios

Private knowledge. Useful answers.

01Engineering / v1.1.0
Private code risk

Check code for explicit risk patterns.

code-text
function run(userInput) {
  return eval(userInput);
}
Public ruledynamic execution
Verdictreview
Input presets for Private code risk

Input & result

USE THE ANSWERDecide what needs a code review.

PERMITTED OUTPUTverdict · category · disclosure

Inspect interface
02Compliance / v1.1.0
Restricted policy

Classify whether proposed sharing includes restricted material.

Share the published product documentation with the project team.

RequestRuleAllowRestrict
Public rulepublic sample scope
Verdictpermitted
Input presets for Restricted policy

Input & result

USE THE ANSWERCheck whether a task crosses a boundary.

PERMITTED OUTPUTverdict · category · disclosure

Inspect interface
03Research / v1.1.0
Private research

Compare lexical overlap between two summaries separated by a line containing --- .

TEXT 1

Battery storage efficiency improves in urban microgrids.

TEXT 2

Battery storage efficiency improves across urban microgrids.

Public rulehigh overlap
Verdictaligned
Input presets for Private research

Input & result

USE THE ANSWERCompare the wording of two research summaries.

PERMITTED OUTPUTverdict · category · disclosure

Inspect interface
04Operations / v1.1.0
Operating history

Classify supplied operational log text.

Oct 25, 2026 · 05:00:00 EDT request timeout
Oct 25, 2026 · 05:01:00 EDT retry failed
Oct 25, 2026 · 05:02:00 EDT critical error
Public rulerepeated incident
Verdictreview
Input presets for Operating history

Input & result

USE THE ANSWERDecide what to investigate in an event log.

PERMITTED OUTPUTverdict · category · disclosure

Inspect interface
05Personalization / v1.1.0
Personal context

Select the format directly expressed in a user preference.

“I prefer short, concise replies with the next step first.”

compact
balanced
expanded
Public ruleexplicit format preference
Selectioncompact
Input presets for Personal context

Input & result

USE THE ANSWERAdapt a response to an explicit preference.

PERMITTED OUTPUTselection · category · disclosure

Inspect interface
06Evaluation / v2.0.0
Proprietary evaluator

Score whether a proposal states a goal, a metric and a deadline.

01Goal02Metric03Deadline
Exact score3/33 declared criteria · aggregate result
Public rulecriteria met
Exact score3/32–3 criteria
Input presets for Proprietary evaluator

Input & result

USE THE ANSWEREvaluate a candidate against declared criteria.

PERMITTED OUTPUTscore · scoreBand · category · disclosure

Inspect interface

Examples · Select an alternate input to compare its public rule match and actual bounded answer.

Execution details

These deterministic public rules illustrate each interface. Sample selection does not issue a request or write a ledger event. Research compares lexical overlap. Exact scores and coarse bands are shown only when present in that sample’s output.

Protocol

Use the answer. Keep the source.

A public capability. An owner-controlled Cell. A bounded result.
Capability, Cell boundary, roles and generated artifacts

↓ caller forms a bounded task

↓ match and check

Private source stays in Vault.

↓ only after output check

↓ record this call

Broker · Guardian · Vault

Ownership

Keep the source. Share the capability.

The same controlled source can support another useful answer.

Two questions use one controlled source. Each receives its own bounded answer and record, while the owner keeps the underlying knowledge and the terms for the next call.

One source · two calls

Private code risk

Internal risk experiencestays inside

Request 1

Array total

function total(items) {
  return items.reduce((sum, item) => sum + item.price, 0);
}
120s TTL

Request verdict · category · disclosure

OWNER-CONTROLLED CELL◇ Controlled access
Private sourcefixed inside
◇ Request arrives3 declared · 3 permitted
0° · Front100%
The source stays fixed.3 declared fields · each call has its own result and record.
01

Awaiting this call

Array total

The first bounded answer appears after its output check.

Record after releaseOne Capsule for this input
02

Awaiting this call

Dynamic execution

A second input uses the same controlled source.

Record after releaseOne Capsule for this input
Allowed outputs

The outlet admits only declared, requested and currently permitted fields.

Read more

Example

Call 1 of 2 · Request arrives

Execution details

Two public inputs run through the same sample adapter once and are cached as separate records. Playback, sample selection and owner-control illustrations preserve their IDs, times, digests and disclosure history. Inspect opens the corresponding local example record. To submit a new request, use Console.

Economic model

Value follows accepted work.

Task terms connect delivery to interface validity, record integrity and agreed business acceptance. Fees can follow accepted work under the agreement.

About these terms

Acceptance conditions are declarations. This local example does not execute payment.

Read the economic model

Example run

Watch a bounded call.

Follow one recorded request from Intent to Capsule. Inspect its policy, allowed answer and execution record.

Example

private-code-risk · preparing record.

Preparing the example record.

Public sample rules create this teaching record once. Playback does not create a new call or ledger entry.

Cell lifecycle

A capability. Under your control.

Define the contract, make its scope clear, and control future access.

  1. 01Define

    Declare the task.

    Declare accepted inputs, allowed outputs and forbidden fields. Broker sees the task; Guardian sees the policy; Vault keeps the source.

    Interface
    private-code-risk
    Lifetime
    120s per request
    Source
    Retained under owner control
    Capability contractExample
    private-code-risk

    Check code for explicit risk patterns.

    Accepted inputcode-text
    Owner boundarySource stays inside
    Declared outputverdictcategorydisclosure
    Retained insidesource · credentials · internalRules · memory

    The declaration fixes what callers may ask and which fields may return.

    Start with the useful task, rather than the private source.
  2. 02Validate

    Check the contract.

    Validate the Manifest and bind a version to its digest. A valid declaration does not certify an execution environment.

    Manifest validationDraft
    01 · ManifestNormalized interfaceaccepts · returns · disclosure
    02 · VersionDraftCompile to bind
    03 · DigestSHA-256Awaiting validation
    Compile the shared draft to form its policy digest.
    Continue in Console →
    Draft · compile to validate this declaration.
    Validation scope

    Compilation checks the declaration and computes its SHA-256 digest. It does not certify a private runtime or publish the capability. Editing updates the shared draft.

    Manifest → version → digest. The validated declaration stays stable.
  3. 03Make available

    Make the capability callable.

    Discover what can be asked. A local example can run here; a published interface still needs its own execution adapter.

    Make availablePublic interfaces
    Discoverable declarationprivate-code-risk
    1. ExamplePublic rules · this browser
    2. Registered interfaceOwner declaration · registry record
    3. Execution adapterConnection and enforcement checked separately
    Execution details

    A registry entry makes an owner declaration discoverable. It does not automatically connect a private executor. Choosing an example opens a request draft.

    Make the interface discoverable while retaining the source.
  4. 04Guard

    Adapt to disclosure pressure.

    Related calls can tighten later disclosure. Explore a sample model without changing the real local ledger.

    Disclosure boundaryTeaching view
    Declared interfaceOutput boundary
    verdictPermitted
    categoryPermitted
    disclosurePermitted
    3 declared · 3 permitted0 released · teaching view
    Pressure
    23 / 100
    Release threshold
    72 / 100
    Threshold distance
    49 points
    The declared fields remain permitted at this pressure.
    Independent simulation · how fields are evaluated

    These sliders change no ledger. Declared fields come from the compiled Manifest. Real calls also intersect permitted fields with requested returns; released fields come only from the actual result. Successful calls use the policy’s rolling 24h window.

    Fields, precision and rolling windows →
    Preview spends nothing. Replay preserves the recorded call.
  5. 05Revoke

    Close access. Keep the record.

    Revoke local example access to block new calls. Discovery and the form reflect that boundary. Existing records remain available to inspect.

    RevocationTeaching view
    New requestrequest →Stays outside
    Entry closedFuture access stops here
    Same controlled sourceRemains inside
    Earlier results & records · outside the boundary0 saved
    No saved records for this Cell yet.Revocation preserves every existing result, Capsule and budget event.
    Example accessOpen · policy checks apply
    Illustration & owner action

    The closed entry above explains revocation. Scrolling changes no access. Only this explicit button changes local example access; restoration grants future access without rewriting records. Registry revocation remains a separate signed owner action.

    Registry revocation remains a separate signed owner action.
Capability contractExample
private-code-risk

Check code for explicit risk patterns.

Accepted inputcode-text
Owner boundarySource stays inside
Declared outputverdictcategorydisclosure
Retained insidesource · credentials · internalRules · memory

The declaration fixes what callers may ask and which fields may return.

Start with the useful task, rather than the private source.

Owner control

Five steps from a declared task to controlled access.

Open the Console
  1. DefineDeclare the task.
  2. ValidateCheck the contract.
  3. Make availableMake the capability callable.
  4. GuardAdapt to disclosure pressure.
  5. RevokeClose access. Keep the record.

Console

A request. Its rules. Its record.

Edit the Manifest, run a bounded task, and inspect what changed. Public sample rules run in your browser.
OCLITH/private-code-riskConsoleExpand
New request · Draft

Private code risk

Valid
Execution pathReady for your request

Select a stage to inspect its role, then run the request to see its actual checks.

Draft · No result has been attached to this request.

Requested return fields

Expires Policy lifetime 120s

Advanced diagnostics & access

Explicit tests for request and output boundaries. Each test run creates its own recorded result.

Stored as the same UTC instant; the editor uses America/New_York.

Requests are checked against the current capability policy.

The same capability, request, trace and Capsule power the walkthrough and workbench. Owner publishing uses a separate signed session.

Open full Console →

Questions

Questions.

Explore the protocol or inspect the Console.

Make private knowledge callable.

A clear task. A bounded answer. An inspectable record.