Source: https://guthlabs.ai/docs/project-templates/app-feature-build/field-guides/

project template / candidate

# App feature build — field guides

The distinct field guides record for App feature build. This page is proposal-only.

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

## Record status

**Record ID**: project:app-feature-build

**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 canonical ID, lifecycle, provenance, and source references.

- Complete intake and attach source-bound requirements; mark unknowns explicitly rather than filling them by inference.

- Define scope, exclusions, authority boundaries, visibility, and held provider or production effects.

- Assign owners and create milestones with deliverables, exit criteria, evidence requirements, and due dates.

- Generate the workback from the target date, including review, accessibility, approval, evidence-freeze, and buffer windows.

- Register dependencies and blockers with owners, verification methods, fallbacks, and escalation paths.

- Declare proposed tools, guides, records, and app surfaces; verify that each is appropriate to its execution and canonical ownership boundary.

- Produce implementation or design evidence as source-labelled records or file references; preserve revisions and receipts.

- Run acceptance checks, accessibility review, risk review, and human approval; record rejected, conditional, or held decisions.

- Update milestone, deadline, dependency, evidence, and risk states after each review; never mark completion from an unverified external effect.

- Close only when delivered outcomes, open items, evidence, approvals, handoff, and follow-up ownership are recorded.

## Handoff boundary

- Confusing indexed or prototype routes with deployed functionality.

- Treating local approval or completion state as external publication, provider connection, database authority, customer indexing, or qualification.

- Creating deadlines without timezone, owner, review buffer, or conflict handling.

- Allowing hidden automation to change schedules, send messages, upload files, or write to external providers.

- Losing provenance, source locators, source hashes, revisions, or visibility boundaries when copying evidence.

- Closing a project despite unresolved blockers, missing evidence, rejected approvals, inaccessible forms, or high-severity risks.

- Overloading one owner with intake, implementation, review, approval, and closure responsibilities without an explicit backup.

- Using unsupported assumptions to fill absent source requirements.

- Exposing private project records through public documentation or search surfaces.

- Failing to provide accessible labels, error summaries, keyboard operation, focus handling, or non-color status indicators.

## Sources and evidence

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

- `source_record:project:app-feature-build`

- `NotebookCollectionKind.project`

- `NotebookTodoPayload.dueAt`

- `Notebook Agenda deadlines/workbacks`

- `Observed native contract: records preserve canonical IDs, provenance, revisions, lifecycle, tags, links, attachments, and record revisions`

- `Observed native contract: PointGuard is a persistent cross-app context surface and specialist apps remain execution and canonical-record owners`

- `App route: /app/notebook/projects/`

- `App route: /app/notebook/to-dos/`

- `App route: /app/notebook/agenda/`

- `App route: /app/notebook/files/`

- `App route: /app/notebook/approvals/`

- `App route: /app/notebook/notes/`

- `App route: /app/notebook/field-guides/`

- `App route: /app/pointguard/`

- `project:app-feature-build`

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

- `PointGuard persistent cross-app context surface`

- `APP_ROUTES:/app/notebook/projects/`

- `APP_ROUTES:/app/notebook/to-dos/`

- `APP_ROUTES:/app/notebook/agenda/`

- `APP_ROUTES:/app/notebook/approvals/`

- `APP_ROUTES:/app/pointguard/`

- `APP_ROUTES:/app/notebook/agent-logs/`