Agent harness · local code proof
A useful agent knows when to stop.
This is a public, sanitized view of a small Client Intake Gate I built locally. It checks required fields and types, blocks requests flagged as containing secrets or lacking consent, and routes higher-risk scopes for a person's decision. Explore the recorded synthetic cases below.
These are recorded results, not a live browser execution, client deployment, provider integration or security certification. The secret flag is supplied by the caller; this demo does not scan raw content for credentials. A “ready” result permits an unsent draft only.
The decision path
Check before anything moves.
- 01Validate fields and typesMalformed input cannot proceed.
- 02Stop on declared secrets or absent consentFlagged input remains blocked.
- 03Route risk to a personProduction changes and larger scopes require review.
- 04Draft, never sendOnly the safe synthetic case reaches an unsent draft.
Recorded decisions
Open a case. Inspect the reason.
Each item shows the request, input conditions, decision and only permitted next step. The fixtures contain no real credentials or contact records.
DEMO-001Map a two-system reporting workflow and prepare an unsent draft handover.Ready for an unsent draft
Consent present · no secret · no production change · £950 example budget
- Why
- Required fields and safety checks passed.
- Allowed next step
- Prepare an unsent draft only.
DEMO-002Connect a production billing webhook and switch it live.Needs human approval
Consent present · no secret · production change · £1,900 example budget
- Why
- The request includes a production change.
- Allowed next step
- Stage the scope for operator review.
DEMO-003Use the pasted API key to inspect a private account.Blocked
Consent present · secret declared · no production change · £500 example budget
- Why
- The input declares credentials or secrets.
- Allowed next step
- Request a redacted resubmission.
DEMO-004Send onboarding messages to imported contacts.Blocked
Consent absent · no secret · no production change · £400 example budget
- Why
- Contact consent is not present.
- Allowed next step
- Obtain operator-confirmed consent.
DEMO-005Prepare a scoped multi-system automation proposal.Needs human approval
Consent present · no secret · no production change · £3,600 example budget
- Why
- The example budget meets the configured human-review threshold.
- Allowed next step
- Stage the scope for operator review.
DEMO-006Incomplete fixture used to prove validation.Invalid input
Consent present · budget, secret and production-change fields missing
- Why
- Three required fields are missing.
- Allowed next step
- Correct the input before any further step.
Verification boundary
Real tests. Limited claim.
The local Python implementation passed nine unit tests, including malformed input and flag checks, on 26 September 2026. The recorded input hash below lets the operator detect fixture drift. This browser page displays reviewed decisions; it does not call Python or touch an account.
Fixture SHA-256 · 6a06337c894f8f6086324fa89d4c61131c0c624c8935717a5d15f168da7bca3d