Source: https://guthlabs.ai/docs/field-guides/supabase-field-guide/related-jobs/

field guide / candidate

# Supabase field guide — related jobs

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

Status: **proposed**Lifecycle: **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](<https://guthlabs.ai/docs/field-guides/>) — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

## Related Agent job handoffs

[source-listed handoff**Security engineering**Source-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/supabase-field-guide/Open the separately admitted canonical job record; this guide does not import its package claims.](<https://guthlabs.ai/docs/jobs/stan-security-engineering/>)[source-listed handoff**Architecture and implementation**Source-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/supabase-field-guide/Open the separately admitted canonical job record; this guide does not import its package claims.](<https://guthlabs.ai/docs/jobs/stan-architecture-and-implementation/>)[source-listed handoff**SRE and incident command**Source-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/supabase-field-guide/Open the separately admitted canonical job record; this guide does not import its package claims.](<https://guthlabs.ai/docs/jobs/stan-sre-and-incident-command/>)[source-listed handoff**Fleet operations**Source-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/supabase-field-guide/Open the separately admitted canonical job record; this guide does not import its package claims.](<https://guthlabs.ai/docs/jobs/stan-fleet-operations/>)[source-listed handoff**Receipt-backed handoffs**Source-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/supabase-field-guide/Open the separately admitted canonical job record; this guide does not import its package claims.](<https://guthlabs.ai/docs/jobs/stan-receipt-backed-handoffs/>)

## Handoff record requirements

The guide may supply evidence, checkpoints, and failure context to a job. The receiving job retains ownership and must record its own decision, approval, and receipt.

- 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

## Ownership boundary

The guide supports these jobs without importing their package descriptions, becoming the job owner, or gaining independent authority.

- A named Supabase surface may be mistaken for a connected provider feature.

- Prototype or indexed routes may be mistaken for production behavior.

- Unverified credentials, database authority, customer data, publication, or deployment may be inferred from architecture language.

- PointGuard may be incorrectly treated as the canonical execution or record owner.

- Missing provenance, source hashes, or receipts may make later review non-reproducible.

- Relative deadlines may be misread as committed calendar dates if no target date is supplied.

- Security, incident, or operational conclusions may be overstated when the supplied source record contains no implementation evidence.

- Local drafts, approvals, or schedule entries may be mistaken for external side effects.

## 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/`