Source: https://guthlabs.ai/docs/tools/terminal-courier/ tool / candidate # Terminal courier Proposal-only contract for routing security, engineering, operations, fleet, and receipt-backed handoff work through bounded terminal-mediated workflows. The observed catalog entry does not prove implementation, connection, qualification, deployment, or authority. It must not create effects or treat confidence as permission. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: tool:terminal-courier **Parent lifecycle**: candidate **Page lane**: contract **Lane lifecycle**: proposed **Owner**: Stan **Owner role**: Chief Security and Engineering Officer **Owner status**: Not separately recorded **Qualification result**: NOT RUN · held for evidence and human review **Working browser surface:** [Tools — overview]() — Inspect the tool contract, usage, boundaries, and proposed qualification checks. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held. ## Bounded contract Proposal-only contract for routing security, engineering, operations, fleet, and receipt-backed handoff work through bounded terminal-mediated workflows. The observed catalog entry does not prove implementation, connection, qualification, deployment, or authority. It must not create effects or treat confidence as permission. ### Owners - Stan - Chief Security and Engineering Officer ### Inputs - Security engineering requests - Architecture and implementation requests - SRE and incident-command requests - Fleet operations requests - Receipt-backed handoff requests - Current-work packets - Relevant security, Supabase, and Cloudflare operational context - Explicit authorization and approval records for any gated action ### Outputs - Proposal for a bounded terminal workflow - Validated or rejected handoff packet - Receipt-backed status summary - Dependency and authorization checklist - Failure-state report - Escalation request to the responsible owner ## Required or proposed record references The list defines expected records; it does not assert that any record instance exists. - Source record for tool:terminal-courier - Request identity and scope - Current-work packet or equivalent context - Owner and approver identity - Authorization record for the requested action - Command or handoff receipt - Validation result - Failure and escalation record ## Route contract The links below are this site's admitted canonical public records. Source-lane route suggestions are proposals only and are not represented as live or canonical until separately admitted. [01**overview**/docs/tools/terminal-courier/]()[02**usage**/docs/tools/terminal-courier/usage/]()[03**boundaries**/docs/tools/terminal-courier/boundaries/]()[04**qualification**/docs/tools/terminal-courier/qualification/]() ### Held source-proposed extensions - /docs/terminal-courier/bounded-purpose: Define terminal courier as a proposal-only routing and handoff contract, including explicit non-authority and non-effect boundaries. - /docs/terminal-courier/gates-and-approvals: Explain the five principal gates, required authorization records, and the refusal path when authority is absent. - /docs/terminal-courier/receipt-backed-handoffs: Specify receipt, validation, ownership, and escalation records for permitted handoffs. - /docs/terminal-courier/failure-states: Catalog unavailable implementation, missing connection, failed qualification, undeployed status, ambiguous scope, missing authority, and validation failure. - /docs/security-field-guides: Explain how the proposal maps to security engineering work and principal gates without asserting execution authority. - /docs/operations/current-work-packets: Define the receipt-backed handoff and current-work packet records required for proposal tracking. - /docs/operations/field-guide-routing: Distinguish when Security, Supabase, Cloudflare operations, or Current-work packets are the relevant documentation route. - /docs/tools/terminal-courier/identity — source-backed identity, ownership, known unknowns, and catalog limits. - /docs/tools/terminal-courier/qualification — deterministic qualification matrix, evidence requirements, and hold conditions. - /docs/tools/terminal-courier/workflows — proposal, authorization, execution, and receipt state model for related jobs. - /docs/tools/terminal-courier/gates — destructive remediation, money or purchasing, credential changes, public deployment, and legal filing controls. - /docs/tools/terminal-courier/security — never-rules, threat cases, fail-closed behavior, and incident evidence. - /docs/tools/terminal-courier/accessibility — keyboard, focus, labels, status announcements, contrast, reduced motion, and error recovery requirements for documentation and any future interface. - /docs/tools/terminal-courier/privacy — data minimization, retention questions, secret handling, redaction, and logging boundaries. - /docs/tools/terminal-courier/abuse — misuse cases, rate-limit questions, destructive-command containment, and non-escalation tests. - /docs/tools/terminal-courier/sources — exact source record, provenance, unsupported claims, and citation rules. - /docs/tools/terminal-courier/authority — authority evidence, delegation boundaries, and the prohibition on manufacturing Antonio's authority. - /docs/tools/terminal-courier/receipts — receipt schema, handoff verification, and distinction between intent, proposal, execution, and observed effect. These extension paths are not generated by this record and must not be treated as resolving routes. ## Sources and evidence These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment. - `source_record:tool:terminal-courier` - `agents/index.html#stan`