Supabase field guide — tools

The distinct tools record for Supabase field guide. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: field-guide:supabase-field-guide
Parent lifecycle: candidate
Page lane: tools
Lane lifecycle: proposed
Owner: Stan
Owner role: Not separately recorded
Owner status: Not separately recorded
Qualification result: NOT RUN · held for evidence and human review

Working browser surface: Field guides — documentation — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

Authoritative tools lane tools and interfaces

Canonical tools-page assignments

Field Guides (interface · required) — Compose and browse the bounded procedure, prerequisites, ordered steps, related jobs, and linked instruments. Must not imply that a named guide is an active Supabase integration or production runbook.
Notes (interface · required) — Capture source-labelled observations, assumptions, and unresolved questions with tags, pins, source, and revision context. Must not be used as authoritative provider or database state.
Files (interface · required) — Keep local references to architecture diagrams, review exports, and evidence beside records without hidden upload. Must not be treated as protected remote storage or proof that a file was uploaded.
To-dos (interface · required) — Create explicit owners, due dates, priorities, review signals, and workback tasks for security, architecture, SRE, fleet, and handoff work. Must not silently schedule external provider actions.
Approvals (interface · required) — Gate proposed conclusions and handoffs with Needs review, Approved, or Held status and preserve receipts. Approval is local proposal governance, not authorization to deploy or connect a provider.
Agent Logs (interface · required) — Record Stan's bounded work, authority, evidence, current state, and handoff receipts. Must not claim agent execution beyond recorded local proposal activity.
PointGuard (interface · optional) — Carry the current guide context across Notebook surfaces for focused review. Must not become a canonical Supabase execution surface or imply cross-app provider access.
Checksum Verifier (skill · optional) — Check a supplied evidence checksum or source SHA-256 for record-integrity review. Must not verify authenticity, deployment, provider identity, database contents, or security compliance.
HTTP Status Code / Header Lookup (skill · optional) — Interpret supplied, locally captured HTTP status or header text during architecture or incident review. Must not make live requests, prove endpoint ownership, or establish a connected Supabase feature.
Uptime / SLA Availability Calculator (skill · optional) — Calculate availability from an explicitly supplied historical interval and downtime dataset for educational planning. Must not infer live uptime, provider SLA coverage, production health, or contractual compliance.

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

checksum-verifieroptional · Validate a supplied checksum alongside Notebook provenance fields; do not use it to establish authenticity or production state.http-status-code-header-lookupoptional · Explain supplied HTTP response metadata in an incident or architecture note; do not use it for live connectivity or provider verification.uptime-sla-availability-calculatoroptional · Compute a transparent availability estimate from supplied observations; do not present it as a live metric or SLA determination.

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

Use boundary

A field-guide title may be mistaken for a connected Supabase integration.
Local prototype or index routes may be mistaken for provider, credential, database, customer, publication, or production capability.
Checksum validation can confirm only that supplied data matches a supplied digest; it cannot establish trust or authenticity.
HTTP interpretation can be stale, incomplete, or detached from the claimed service.
Availability calculations are only as good as the supplied observation window and downtime data.
Security, recovery, migration, and compliance conclusions require qualified human review.
Attachments or file references may contain secrets; do not place credentials or sensitive production data in proposal records.
Unowned or undated workbacks can create false readiness.
Agent logs and approvals are local receipts, not evidence of external execution.

Sources and evidence

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

source_record:field-guide:supabase-field-guide
agents/index.html#stan
field-guide:supabase-field-guide
Observed native contract: project_and_field_guide_collections
Observed native contract: deadlines
Observed native contract: records
Observed native contract: pointguard
App route: /app/notebook/field-guides/
App route: /app/notebook/approvals/
App route: /app/notebook/agent-logs/