Supabase field guide — forms

The distinct forms 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: plan
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.

Proposed form sections

Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth.

Scope and authority

Define what is being evaluated and preserve the boundary between a proposal and verified production state.

objective
requesting_agent
owner_agent
related_job
in_scope_surfaces
out_of_scope_effects
authority_boundary
target_review_date

Source and provenance

Capture the supplied source record and any evidence without inventing provider or deployment facts.

source_record_id
source_refs
source_locator
source_sha256
evidence_description
evidence_timestamp
provenance_note
revision

Architecture review

Document proposed data, application, and ownership boundaries for later human review.

proposed_components
canonical_record_owner
context_surface_role
data_flow_description
visibility_partition
dependency_assumptions
unverified_questions

Security and operations checks

Create reviewable checks for security engineering, SRE, incident command, and fleet operations.

credential_handling_check
access_boundary_check
failure_mode_check
incident_owner
rollback_or_hold_action
monitoring_evidence_required
operational_unknowns

Receipt-backed handoff

Produce a bounded handoff that identifies evidence, open questions, and approval state.

handoff_recipient
evidence_links
open_risks
decision_requested
approval_state
next_owner
review_deadline

Accessible state contract

Every field requires a visible and programmatic label.
Required and optional fields must be stated in text.
Invalid entries require an actionable message linked to the field.
Blocked and Held states remain visible without relying on color alone.

Supporting documentation fields

These fields come from the tools lane and remain separate from the primary operating form.

Scope and ownership

Define the bounded evaluation and accountable owner without asserting an active Supabase connection.

guide title
guide owner agent
related job IDs
evaluation objective
in-scope surfaces
out-of-scope effects
record owner

Evidence register

Capture source-labelled evidence and preserve provenance for each conclusion.

evidence record ID
source locator
source SHA-256
evidence type
observed state
revision
provenance note
linked attachment or file reference

Security review

Review proposed security controls and unresolved risks without treating estimates or local checks as certification.

identity and access assumptions
secret-handling boundary
data classification
least-privilege questions
logging and receipt requirements
failure state
security reviewer
review deadline

Architecture and operations

Document proposed ownership, dependencies, recovery questions, and operational workbacks.

canonical-record owner
specialist execution owner
dependency list
backup and recovery questions
migration or rollback concern
incident trigger
runbook link
workback due dates

Approval and handoff

Make review status and transfer conditions explicit.

approval status
approver
held claims
accepted claims
handoff recipient
receipt ID
next action
handoff deadline

Required or proposed record references

No record existence is asserted by this documentation page.

field-guide:supabase-field-guide:plan
source-bound evidence notes with source locators and SHA-256 where available
architecture review record
security review record
operations and incident review record
receipt-backed handoff record
approval record marked Needs review, Approved, or Held
source-labelled field-guide record
linked job records for Security engineering, Architecture and implementation, SRE and incident command, Fleet operations, and Receipt-backed handoffs
source notes and file references
deadline and workback to-dos
approval receipt
Agent Log entry

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:plan
Observed native contract: project_and_field_guide_collections
Observed native contract: deadlines
Observed native contract: records
Observed native contract: pointguard
Observed app routes supplied in the source context
field-guide:supabase-field-guide
App route: /app/notebook/field-guides/
App route: /app/notebook/approvals/
App route: /app/notebook/agent-logs/