Value follows accepted work.
A protocol view of capability declaration, bounded work, acceptance and fees, with a clear separation from payment implementation.
Useful work within a rule
Private Capability Liquidity means that the usefulness of private knowledge can circulate without transferring the source itself. An owner declares a task and its boundary. A caller discovers the capability and requests a permitted result. The resulting work can be inspected against an agreed interface.
The capability is the callable product. Broker, Guardian and Vault describe cooperating roles in that work. They are not financial product categories.
A bounded work cycle
- Declare: define the task, interface, disclosure policy, expiry and limits.
- Register: publish the reviewed declaration under an authenticated owner.
- Request: submit a bounded task with a permitted return schema.
- Check: accept only output and evidence that meet the agreed policy.
- Account: organize fees around work that satisfies those conditions.
Rejected requests and outputs that fail their contract do not enter the corresponding successful work settlement flow.
The current implementation
The Console compiles settlement.condition and settlement.status together with the other policy fields. New declarations distinguish output conformity, record integrity and agreed business acceptance, with status declaration. These are acceptance terms, not evidence that the business conditions have been evaluated. Compiling a Manifest, running a sample or publishing a registry record does not transfer funds.
This deployment does not implement payment collection, token settlement, payouts, yields, buybacks, burns, staking or dividends. Its Capsule is an integrity record rather than a financial settlement receipt.
Wallet signatures authenticate owner operations. They are requested only for sign in. The explicit publish operation registers the reviewed Manifest through this deployment's server. It is separate from a transaction or payment.
Separate configuration boundaries
A token address, registry service and settlement program are different configuration choices. Supplying a contract address cannot automatically activate a capability network or authorize settlement.
Production settlement would require an agreed fee schedule, settlement service, authorization, dispute handling and a verified rule for valid work. No success state in this site stands in for those missing financial operations.
Measure what happened
Static protocol roles and example policies can be counted directly. Local runs can report their actual request IDs and results. The directory can report records returned by its registry.
These measures remain distinct. Built-in examples are not network registrations. API request totals are not private task completions. The interface does not infer revenue, adoption or success rates from sample activity.