Anything can make a request. Nothing can assert that it was allowed.
Authority is not a field an API client fills in. Commands entering the platform carry requested intent only — the decision, the authority, the recording time and the evidence receipt are all derived inside the trusted boundary.
A proposal is not an instruction. Only your bank sends the file.
Certified and complete. Available for approval — and approval alone sends nothing; the file is released by your bank.
Certified, with limitations that are stated rather than hidden.
Routed to a named reviewer before it can proceed.
Readiness failed. The system declines rather than guessing — missing price, unknown limit scope, unresolved classification conflict.
Three promises, not a nine-column matrix.
The full rights framework governs our own corpus and lives in the security appendix. What applies to you is short.
Pyligent Agents
The harness this runs inside is published — the orchestration framework, the agent contracts and the governance kernel. It is released so the architecture can be reviewed rather than taken on trust, and so a reviewer can check that the properties described on this page are the ones the code actually enforces.
Propose, certify, dispose. Typed artifacts. Provenance invariants. The four terminal states and the right to abstain. The command boundary described above.
Venue ingest, the movement cap, the scoring policy and the instruction file. Runs inside the harness; not part of it.
Cloning the repository does not produce a collateral service. It produces the control plane a collateral service would have to run inside — which is the point: the part you are asked to trust is the part you can read.