# OCLITH notes

Private capability, disclosure boundaries, records and owner control. Read as markdown.

- [Blog home (HTML)](https://www.oclith.dev/blog/)

- [Define the boundary before the call.](https://www.oclith.dev/blog/boundary-before-execution.md) — Inputs, outputs, expiry and cumulative limits form an inspectable contract.
- [One call. One inspectable record.](https://www.oclith.dev/blog/one-call-one-record.md) — A Capsule connects the redacted intent, policy, result, trace and budget change of an actual run.
- [Discovery with an owner and a boundary.](https://www.oclith.dev/blog/owner-controlled-discovery.md) — Keep examples separate from public declarations, and make publication an explicit owner action.
- [Private knowledge. Public capability.](https://www.oclith.dev/blog/private-capability-liquidity.md) — How a callable task lets useful work move while its source remains under owner control.
- [A public sample needs a clear scope.](https://www.oclith.dev/blog/public-sample-private-runtime.md) — What the browser workbench implements, and what a private execution adapter must enforce.
- [Value follows valid work.](https://www.oclith.dev/blog/valid-work-and-fees.md) — Capability accounting starts with an agreed task, a permitted answer and an inspectable record.