Source: https://guthlabs.ai/docs/project-templates/native-release/field-guides/

project template / candidate

# Native release — field guides

The distinct field guides record for Native release. This page is proposal-only.

Status: **proposed**Lifecycle: **candidate**

## Record status

**Record ID**: project:native-release

**Parent lifecycle**: candidate

**Page lane**: app_features

**Lane lifecycle**: proposed

**Owner**: Not separately recorded

**Owner role**: Not separately recorded

**Owner status**: Not separately recorded

**Qualification result**: NOT RUN · held for evidence and human review

**Working browser surface:** [Project templates & workflows — overview](<https://guthlabs.ai/labs.html#templates-workflows>) — Create a local project from this template and validate its forms. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

## Related field-guide records

- /app/notebook/field-guides/

Source-proposed guide paths are references, not proof that those paths resolve.

## Operating sequence

- Create the project record with a canonical project ID, owner, requested decision date, lifecycle, provenance, and source links.

- Complete intake and scope; explicitly record non-goals and the boundary that provider, credential, database, customer, publication, and production effects remain held.

- Define milestones with owners, entry criteria, exit criteria, evidence requirements, and linked dependencies.

- Set the decision deadline, timezone, hard or soft classification, and workback anchor; create derived local to-dos with dueAt and priority.

- Validate dependencies, assign fallback plans, and mark any missing owner or source as a blocking condition.

- Select only designated local tools and guides; record that named routes are prototypes or indexes unless separately verified.

- Prepare the build, packaging, review, and accessibility evidence records without claiming that an app build was produced, submitted, published, or connected to a provider.

- Submit approval records for human review and preserve Needs review, Approved, or Held status with receipts.

- Review risks, overdue items, conflicts, missing evidence, and unresolved dependencies before the decision deadline.

- Close as completed, deferred, or stopped; preserve open loops, held effects, evidence gaps, and the final human decision.

## Handoff boundary

- A proposed project record could be mistaken for a deployed release workflow or production backend.

- A named Apple build target could be mistaken for a produced, signed, submitted, or published build.

- Missing timezone, owner, or workback anchor can produce misleading deadlines.

- Silent rescheduling can hide missed commitments or alter human decisions.

- Incomplete provenance or evidence can make review results non-reproducible.

- Provider, credential, database, customer, publication, and production effects must remain held.

- Overly broad scope can combine packaging, qualification, publication, and operational work without separate approvals.

- Accessibility review may be falsely marked complete without recorded evidence and limitations.

- Attachments or file references must not be represented as uploaded or protected assets when the observed Files surface only supports local references.

## Sources and evidence

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

- `source_record:project:native-release`

- `NotebookCollectionKind.project`

- `NotebookTodoPayload.dueAt`

- `Notebook Agenda deadlines/workbacks`

- `Observed native contract: project_and_field_guide_collections`

- `Observed native contract: deadlines`

- `Observed native contract: records`

- `Observed native contract: pointguard`

- `Observed native contract: web_boundary`

- `/app/notebook/projects/`

- `/app/notebook/to-dos/`

- `/app/notebook/agenda/`

- `/app/notebook/files/`

- `/app/notebook/approvals/`

- `/app/notebook/paper/`

- `/app/notebook/agent-logs/`

- `Notebook records provenance, revisions, links, and attachments`

- `PointGuard persistent cross-app context surface`

- `Web boundary: provider, credential, database, customer, publication, and production effects are held`

- `/app/pointguard/`