Receipt-backed handoffs — tools

The distinct tools record for Receipt-backed handoffs. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: job:stan:receipt-backed-handoffs
Parent lifecycle: candidate
Page lane: package
Lane lifecycle: proposed
Owner: Stan
Owner role: Chief Security and Engineering Officer
Owner status: VERIFIED
Qualification result: NOT RUN · held for evidence and human review

Working browser surface: Agent jobs — builder overview — Inspect the package and stage a local project. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

Authoritative package lane tools and interfaces

Canonical tools-page assignments

Assurance preflight (skill · required) — Checks evidence, scope, risks, reversibility, and readiness before a handoff is recorded.
Terminal courier (skill · required) — Prepares bounded terminal-oriented handoff material while keeping execution and effects subject to authority review.
Receipt ledger (record · required) — Preserves a durable receipt for what was prepared, its sources, recipient, status, and held effects.
Source-bound recall (skill · required) — Keeps summaries and continuity notes tied to source records and revisions instead of unsupported memory.
Security field guides (guide · required) — Provides the declared security procedure context for bounded engineering handoffs.
Supabase field guide (guide · optional) — Relevant only when the handoff concerns Supabase-related work; it does not establish a connected provider or database authority.
Cloudflare operations (guide · optional) — Relevant only when the handoff concerns Cloudflare operations; it does not establish deployment or provider authority.
Current-work packets (guide · required) — Defines the continuity-oriented packet structure for current state, next actions, risks, and evidence.
Notebook (interface · required) — Owns local notes, deadlines, projects, guides, approvals, and agent-log review surfaces.
PointGuard (interface · required) — Carries focused cross-app context while leaving specialist execution and canonical records with their owning surfaces.

Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved.

Authoritative lane instrument assignments

Canonical tools-page assignments

No verified instrument is assigned to this tools lane.

An instrument listed only for another lane does not become a tools-page assignment.

Use boundary

Treating confidence, urgency, or a prior handoff as permission.
Manufacturing Antonio's authority or substituting Stan's role for a required approver.
Converting a proposal, terminal instruction, or receipt into an external effect.
Executing destructive remediation or changing credentials without explicit human authorization.
Leaking secrets, credentials, sensitive paths, or protected operational details into a handoff.
Using stale, unverified, or unprovenanced source material.
Creating a receipt that records intention as completion.
Assuming a named Supabase or Cloudflare guide proves provider connection or operational access.
Overlooking recipient identity, acknowledgement, timezone, dependency, rollback, or continuity requirements.
Relying on inaccessible status colors, ambiguous labels, or undocumented failure states.

Sources and evidence

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

agents/index.html#stan
source_record:job:stan:receipt-backed-handoffs
observed_native_contract.records
observed_native_contract.deadlines
observed_native_contract.pointguard
observed_native_contract.web_boundary
app_route:/app/pointguard/
app_route:/app/notebook/approvals/
app_route:/app/notebook/agent-logs/
app_route:/app/notebook/field-guides/
app_route:/app/notebook/projects/
app_route:/app/notebook/search/