Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

project template / candidate

Field guide build — field guides

The distinct field guides record for Field guide build. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID
project:field-guide-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 — 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

  1. Create the proposal project record with canonical ID, origin, source references, provenance, revision, lifecycle, tags, links, and visibility.
  2. Complete intake and identify the source records and source locators that bound the work.
  3. Define scope, prerequisites, exclusions, human-review points, and external-effect holds.
  4. Assign project, guide, evidence, risk, approval, and closure owners, including backups and escalation paths.
  5. Create milestones and derive a workback from the final deadline with review buffers and explicit approval gates.
  6. Register dependencies and assign verification dates, fallback plans, and blocking severity.
  7. Declare the native Notebook surfaces and any applicable guide or record relationships; record all prototype or indexed limitations.
  8. Draft the field guide from source-bound procedures and link each material claim to evidence.
  9. Run procedural tests using representative local records or references; record failures, expected results, actual results, and rework.
  10. Submit the guide and evidence package for approval; preserve Needs review, Approved, or Held status and decision receipts.
  11. Resolve required rework or document accepted limitations; do not treat an approval as publication or external execution.
  12. Close only when acceptance tests pass, required evidence is linked, open items are dispositioned, and a maintenance owner and review date exist.

Handoff boundary

  • Confusing an indexed or prototype route with a connected production workflow.
  • Treating source-labelled references or local records as authoritative external data.
  • Missing source provenance, locator, revision, or SHA-256 information and later losing traceability.
  • Setting milestone dates without approval buffers and discovering late review conflicts.
  • Marking work complete when evidence is absent, stale, contradictory, or not reviewed.
  • Allowing dependencies or risks to remain unresolved while the project appears on schedule.
  • Hidden provider writes, external sends, publication, credential use, upload, or protected-storage effects.
  • Overly dense forms that omit labels, error text, keyboard access, or non-color status cues.
  • Exposing private project notes, evidence, attachments, or customer-related context through public documentation routes.
  • Using a held instrument or inventing a tool slug instead of selecting only verified instruments.

Sources and evidence

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

  • source_record:project:field-guide-build
  • project:field-guide-build
  • NotebookCollectionKind.project
  • NotebookTodoPayload.dueAt
  • Notebook records preserve canonical IDs, origin, source locators, source SHA-256, provenance, revision, lifecycle, tags, links, attachments, and record revisions.
  • Notebook Agenda deadlines/workbacks
  • /app/notebook/projects/
  • /app/notebook/field-guides/
  • /app/notebook/to-dos/
  • /app/notebook/agenda/
  • /app/notebook/files/
  • /app/notebook/approvals/
  • Notebook records canonical IDs, provenance, source locators, source SHA-256, revisions, lifecycle, tags, links, and attachments
  • PointGuard persistent cross-app context surface
  • APP_ROUTES:/app/notebook/projects/
  • APP_ROUTES:/app/notebook/field-guides/
  • APP_ROUTES:/app/notebook/to-dos/
  • APP_ROUTES:/app/notebook/agenda/
  • APP_ROUTES:/app/notebook/approvals/
  • APP_ROUTES:/app/pointguard/
  • ALLOWED_INSTRUMENTS:date-duration-calculator
  • ALLOWED_INSTRUMENTS:countdown-days-until-timer