Supabase field guide — examples

The distinct examples 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.

Hypothetical scenarios

A reviewer opens the Supabase field guide guide for bounded local rehearsals. Every fixture uses invented placeholders, performs no provider or external action, and remains held until source evidence and human review are recorded.

1. Guided inquiry fixture

A reviewer records a bounded question, links only supplied source references, and marks every unanswered point Needs review.

Fixture ID: supabase-field-guide-example-001
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

2. Source comparison fixture

A reviewer compares two hypothetical source locators, preserves disagreement, and holds any conclusion until provenance is supplied.

Fixture ID: supabase-field-guide-example-002
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

3. Uncertainty and pathway fixture

A reviewer constructs a local procedure or study pathway with checkpoints while labelling uncertainty and leaving external effects Held.

Fixture ID: supabase-field-guide-example-003
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

4. Potentially allowed claim fixture

A hypothetical claim may advance only when its exact evidence locator, scope, reviewer, and decision rationale are recorded; this fixture asserts no fact.

Fixture ID: supabase-field-guide-example-004
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

5. Held claim fixture

A hypothetical unsupported claim remains Held with missing evidence and human-review rationale visible; it is not published or indexed.

Fixture ID: supabase-field-guide-example-005
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

Filled example fields

Scope and authority fixture

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

objective: Example value to be supplied and reviewed
requesting_agent: Named human or Agent owner required
owner_agent: Named human or Agent owner required
related_job: Example value to be supplied and reviewed
in_scope_surfaces: Example value to be supplied and reviewed
out_of_scope_effects: Example value to be supplied and reviewed

Source and provenance fixture

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

source_record_id: fixture-source-001 (hypothetical; no external claim)
source_refs: fixture-source-001 (hypothetical; no external claim)
source_locator: fixture-source-001 (hypothetical; no external claim)
source_sha256: fixture-source-001 (hypothetical; no external claim)
evidence_description: fixture-source-001 (hypothetical; no external claim)
evidence_timestamp: Not supplied in this hypothetical fixture

Architecture review fixture

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

proposed_components: Example value to be supplied and reviewed
canonical_record_owner: Named human or Agent owner required
context_surface_role: Example value to be supplied and reviewed
data_flow_description: Example value to be supplied and reviewed
visibility_partition: Example value to be supplied and reviewed
dependency_assumptions: Example value to be supplied and reviewed

Review questions

The guide record is lifecycle proposed and contains Stan as owner.
All five related jobs are linked without inventing their IDs or status.
Every evidence item has a source locator, provenance note, revision, and, where supplied, source SHA-256.
The form distinguishes observed local prototype or index state from held provider, credential, database, customer, publication, and production effects.
Each workback action has an owner, due date, status, and failure or escalation path.
Instrument outputs are attached as evidence with explicit limitations and are not described as deployment, connectivity, uptime, SLA, or compliance proof.
Approval state is one of Needs review, Approved, or Held and preserves a local receipt.
The handoff records recipient, accepted scope, held claims, next action, and receipt ID.

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/