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

tool / candidate

# Terminal courier — boundaries

The distinct boundaries 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**: contract boundaries

**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.

## Hazards and failure states

- The tool is observed in the agent catalog, but implementation is unproven.

- Connection, qualification, and deployment are unproven.

- The tool may be mistaken for an authority-bearing executor.

- Confidence may be incorrectly treated as permission.

- Antonio's authority must not be manufactured.

- Destructive remediation, money or purchasing, credential changes, public deployment, and legal filing require explicit authority and approval records.

- Missing or stale current-work packets can cause scope or dependency errors.

- Receipt absence or validation failure makes a handoff unverified.

- Failure to distinguish proposal from effect could create unauthorized operational changes.

## Claims potentially allowed after source review

- The catalog identifies a tool named Terminal courier.

- Stan is listed as the owner agent.

- Stan's listed owner role is Chief Security and Engineering Officer.

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

- The source record lists 5 principal gates and 3 never-rules.

## Claims held

- Implementation status

- Connection status

- Qualification status

- Deployment status

- Operational capability

- Authority to execute any gated action

- Antonio's authority

- Current reliability or performance

- Customer use or effects

- Provider or infrastructure identity

## Source gates and never-rules

The source record provides 5 principal gates and 3 never-rules. This page does not infer or add to those counts.

- Destructive remediation

- Money or purchasing

- Credential changes

- Public deployment

- Legal filing

- Manufacture Antonio's authority

- Treat confidence as permission

- Convert a proposal into an effect

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