Supabase field guide

Record status

Record ID

field-guide:supabase-field-guide

Parent lifecycle

candidate

Page lane

catalog overview

Lane lifecycle

candidate

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.

Purpose and audience

Proposal-only, source-bound procedure for evaluating and documenting Supabase-related architecture, security, operations, and handoffs without treating the observed app routes as connected provider infrastructure.

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

Required or proposed record references

The list defines expected record classes. It does not assert that any instance exists.

• 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

Route contract

The links below are this site's admitted canonical public records. Source-lane route suggestions are proposals only and are not represented as live or canonical until separately admitted.

Held source-proposed extensions

• /docs/field-guides/supabase-field-guide/overview/

These extension paths are not generated by this record and must not be treated as resolving routes.

Public claim boundary

Allowed items below are source-lane proposals, not verified current-state claims.

Candidate claims allowed after source review

• A proposal-only Supabase field guide exists as a source-bound Notebook record.
• The observed GuthHub routes provide local prototype or indexed surfaces for notes, files, to-dos, approvals, projects, field guides, logs, and context navigation.
• The guide defines review ownership, evidence requirements, deadline handling, failure states, and handoff criteria.
• The supplied source record identifies Stan as owner and links the stated related jobs.

Claims held

• Supabase is connected to Guth or any provider is connected.
• A Supabase database, credential, schema, customer index, deployment, publication, or production environment exists.
• Any route performs provider writes, database reads, customer indexing, authentication, or operational automation.
• The guide has qualified, deployed, approved, or completed a production implementation.
• Any security, reliability, or compliance property has been verified in production.

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/