Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

tool / candidate

Terminal courier — usage

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

Status: proposedLifecycle: candidate

Record status

Record ID
tool:terminal-courier
Parent lifecycle
candidate
Page lane
usage
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.

Workflow use

  1. Review the applicable security engineering, Supabase, Cloudflare operations, or current-work packet field guide
  2. Check principal gates before destructive remediation, money or purchasing, credential changes, public deployment, or legal filing
  3. Do not manufacture Antonio's authority
  4. Do not treat confidence as permission
  5. Do not convert a proposal into an effect

Related jobs

  • Security engineering
  • Architecture and implementation
  • SRE and incident command
  • Fleet operations
  • Receipt-backed handoffs

Field guides

  • Security field guides
  • Supabase field guide
  • Cloudflare operations
  • Current-work packets

Project contexts

No additional candidate record is attached.

Usage records

  • Receipt-backed handoff
  • Current-work packet

Lane-specific verified instrument aids

No compatible verified instrument is admitted for the usage lane.

Compatibility here means a bounded proposal aid. It does not verify the tool, its implementation, or an external result.

Usage boundary

This usage lane is proposal-only. Implementation, connection, qualification, deployment, publication, provider access, credentials, and authority remain unproven and held.

  • Destructive remediation requires a principal gate.
  • Money or purchasing requires a principal gate.
  • Credential changes require a principal gate.
  • Public deployment requires a principal gate.
  • Legal filing requires a principal gate.
  • Antonio's authority must not be manufactured.
  • Confidence must not be treated as permission.
  • A proposal must not be converted into an effect.
  • Implementation, connection, qualification, deployment, and authority are unproven.

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