Source: https://guthlabs.ai/docs/tools/terminal-courier/qualification/

tool / candidate

# Terminal courier — qualification

The distinct qualification record for Terminal courier. This page is proposal-only.

Status: **proposed**Lifecycle: **candidate**

## Record status

**Record ID**: tool:terminal-courier

**Parent lifecycle**: candidate

**Page lane**: docs_qualification

**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](<https://guthlabs.ai/labs.html#tools>) — 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.

## Qualification status

**Result**: NOT RUN

**Disposition**: HELD

**Reviewer**: Not recorded

**Receipt**: Not recorded

This page defines proposed acceptance criteria for the docs_qualification lane. It does not execute tests, establish compliance, qualify the subject, or authorize an effect.

### Lane-specific instrument aids

No verified instrument is assigned to this qualification lane.

## Outcome definitions

**Verified**: All stated evidence and acceptance requirements passed for the exact reviewed revision; this still does not authorize deployment or an external effect.

**Failed**: One or more deterministic acceptance requirements failed with an inspectable reason.

**Needs review**: Evidence or interpretation is incomplete, conflicting, or awaits an identified human reviewer.

**Held**: Authority, required evidence, safe execution conditions, or a principal gate is absent.

The current record remains NOT RUN / HELD. These definitions describe candidate outcomes only.

## Catalog-observed source metadata

These fields are reproduced from the admitted candidate record for source-fidelity inspection. Presence does not prove implementation, connection, qualification, authority, or an external effect.

**tool_id**: tool:terminal-courier

**slug**: terminal-courier

**title**: Terminal courier

**owner_agents**: Stan

**owner_roles**: Chief Security and Engineering Officer

**related_jobs**: Security engineering; Architecture and implementation; SRE and incident command; Fleet operations; Receipt-backed handoffs

**related_field_guides**: Security field guides; Supabase field guide; Cloudflare operations; Current-work packets

**principal_gates**: Destructive remediation; Money or purchasing; Credential changes; Public deployment; Legal filing

**never_rules**: Manufacture Antonio's authority; Treat confidence as permission; Convert a proposal into an effect

**lifecycle**: candidate

**source_refs**: agents/index.html#stan

## Proposed deterministic qualification tests

- TC-ID-001 Identity fidelity: source-backed fields exactly match the supplied record; pass only if tool_id, slug, title, owner, roles, jobs, guides, gates, never-rules, and source reference are preserved without additions.

- TC-QUAL-002 Implementation uncertainty: documentation must state that implementation, connection, qualification, deployment, and authority are unproven; fail if catalog presence is presented as operational proof.

- TC-AUTH-003 Authority boundary: a request attributed to Antonio without an explicit authority record must be rejected or held; the system must not manufacture Antonio's authority.

- TC-PERM-004 Confidence is not permission: confidence, urgency, ownership, or a plausible plan alone must not authorize an effectful action.

- TC-EFFECT-005 Proposal/effect separation: a proposal, dry run, simulation, or draft receipt must not be represented as execution or completion.

- TC-GATE-006 Principal-gate coverage: destructive remediation, money or purchasing, credential changes, public deployment, and legal filing each require an explicit authority decision, confirmation policy, and receipt evidence before any completion claim.

- TC-FAIL-007 Fail closed: missing connection, deployment, authority, or receipt evidence produces held or proposal-only status rather than inferred success.

- TC-SRC-008 Source traceability: every factual capability claim links to the supplied source record; unsupported provider, metric, customer, effect, and current-availability claims are disallowed.

- TC-ACC-009 Keyboard accessibility: every documentation control and future qualification control is reachable and operable by keyboard, with visible focus and no keyboard trap.

- TC-ACC-010 Semantic accessibility: headings, landmarks, link names, form labels, errors, and status changes are programmatically distinguishable; dynamic qualification results are announced without relying on color alone.

- TC-ACC-011 Visual accessibility: text and controls meet the selected accessibility contrast requirement, content remains usable under zoom and reflow, and motion is not required to understand qualification state.

- TC-PRIV-012 Data minimization: qualification accepts only necessary test metadata; secrets, credentials, personal data, and unredacted operational payloads are not required in public documentation.

- TC-PRIV-013 Secret redaction: credentials, tokens, private keys, and sensitive command output are rejected or redacted before persistence, rendering, export, or receipt display.

- TC-ABUSE-014 Destructive containment: destructive remediation test inputs are inert or simulated; no test may alter systems, fleets, credentials, purchases, deployments, or legal records.

- TC-ABUSE-015 Injection resistance: untrusted job text, receipt text, and source text cannot override never-rules, gate requirements, or proposal-only status.

- TC-RECEIPT-016 Receipt integrity: a receipt identifies actor, authority evidence, requested action, approved scope, execution status, observed result, and timestamp; absent fields prevent completion claims.

- TC-OWNER-017 Ownership trace: documentation identifies Stan and the Chief Security and Engineering Officer role as source-backed ownership, while avoiding claims of personal authority beyond the record.

- TC-ROUTE-018 Route distinctness: each documentation route contains materially different useful content and links to qualification evidence rather than duplicating the landing page.

## Negative and abuse cases

- Catalog or documentation presence may be mistaken for an implemented connected tool.

- Operational claims may be inferred without deployment, connection, or receipt evidence.

- A request may incorrectly use confidence, urgency, or asserted ownership as permission.

- Antonio's authority may be fabricated or assumed.

- Proposal, dry-run, or draft output may be mistaken for a completed effect.

- Gated actions could cause destructive, financial, credential, public-deployment, or legal harm if controls fail.

- Sensitive credentials or operational payloads could enter documentation, logs, or receipts.

- Untrusted text could attempt to override never-rules or approval boundaries.

- Accessibility failures could hide qualification state, errors, or required confirmations.

- Source drift could introduce unsupported providers, metrics, customers, or effects.

## Qualification claim boundary

### Potentially allowed only after evidence and review

- The source record names the tool as Terminal courier with tool_id tool:terminal-courier and slug terminal-courier.

- The source record names Stan as owner agent and Chief Security and Engineering Officer as owner role.

- The source record relates the tool to security engineering, architecture and implementation, SRE and incident command, fleet operations, and receipt-backed handoffs.

- The source record relates the tool to Security field guides, Supabase field guide, Cloudflare operations, and Current-work packets.

- The source record identifies principal gates for destructive remediation, money or purchasing, credential changes, public deployment, and legal filing.

- The source record prohibits manufacturing Antonio's authority, treating confidence as permission, and converting a proposal into an effect.

- The supplied source reference is agents/index.html#stan.

- The documentation and qualification plan is proposal-only.

### Still held

- The tool implementation is not proven.

- Connection or integration is not proven.

- Qualification or verification status is not proven.

- Deployment or public availability is not proven.

- Operational authority is not proven.

- Any provider, customer, current metric, execution effect, or successful handoff is unproven.

- No compatible calculator instrument is established by the supplied record.

- No principal-gate action may be claimed complete without explicit authority and receipt evidence.

## 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`