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

tool / candidate

Assurance preflight — usage

The distinct usage record for Assurance preflight. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID
tool:assurance-preflight
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. Identify the related job and operational context
  2. Check applicable principal gates
  3. Verify that authority is evidenced rather than inferred
  4. Separate confidence from permission
  5. Prepare receipt-backed handoff information
  6. Stop before any unverified or gated 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

  • Destructive remediation
  • Money or purchasing
  • Credential changes
  • Public deployment
  • Legal filing

Usage records

  • Security engineering record
  • Architecture and implementation record
  • SRE and incident command record
  • Fleet operations record
  • Receipt-backed handoff record
  • Evidence for applicable principal gates

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.

  • Manufacturing authority
  • Treating confidence as permission
  • Converting a proposal into an effect
  • Proceeding with destructive remediation without an applicable gate review
  • Changing credentials without verified authority
  • Public deployment without verified approval
  • Money or purchasing activity without verified approval
  • Legal filing without verified approval

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

  • source_record:tool:assurance-preflight
  • agents/index.html#stan