Zain Dana HarperBounds · private capability

Trust verification for agentic work.

Bounds verifies agent actions, runtime observations, public claims, sensitive-file hygiene, fixture safety, release inventories, and tamper-evident proof chains.

It is the boundary checker around the capability constellation: detect drift, record evidence, and stop unsafe release paths.

controlled private system · public-safe summary · checked 2026-08-28

Verification spine.

Bounds trust verification map A diagram showing agent action and runtime observations flowing through sensors, claim gates, and proof-chain release decisions. observeRuntime sensorCheckbounds evidenceReceipt gateRelease
Bounds is shown as a verification spine rather than an offensive tool. It gives hiring and partner reviewers a visible control model for private workflows.
Bounds public contract
FieldPublic-safe statementBoundary
InputsSession facts, file changes, git state, claims, fixtures, runtime observations, and release candidates.No private corpus or secret publication.
OutputsDrift findings, claim status, secret-scan results, release inventory, and proof chain.No claim that a pass is third-party certification.
UseControls agent work before publication, submission, or private handoff.No substitute for lawful authorization.

Release boundary.

A pass is evidence, not permission.

Bounds can record that a route passed local checks. It does not create legal authority, recipient approval, independent audit status, or permission to publish controlled material.