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

project template / candidate

App feature build

A source-bound project record for taking one product capability through intake, scope, ownership, milestones, deadline workback, dependency review, evidence capture, approvals, risk handling, and closure. All implementation and external effects remain proposal-only until separately verified.

Status: candidateLifecycle: candidate

Record status

Record ID
project:app-feature-build
Parent lifecycle
candidate
Page lane
catalog overview
Lane lifecycle
candidate
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.

Purpose and audience

A source-bound project record for taking one product capability through intake, scope, ownership, milestones, deadline workback, dependency review, evidence capture, approvals, risk handling, and closure. All implementation and external effects remain proposal-only until separately verified.

  • product owner
  • feature owner
  • designer
  • engineer
  • reviewer
  • accessibility reviewer
  • approver

Required or proposed record references

The list defines expected record classes. It does not assert that any instance exists.

  • project record
  • source-bound requirement notes
  • milestone to-dos
  • deadline and workback items
  • dependency records
  • evidence records or file references
  • approval record
  • risk records
  • closure note

Route contract

The links below are this site's admitted canonical public records. Source-lane route suggestions are proposals only and are not represented as live or canonical until separately admitted.

01overview/docs/project-templates/app-feature-build/02forms/docs/project-templates/app-feature-build/forms/03deadlines/docs/project-templates/app-feature-build/deadlines/04tools/docs/project-templates/app-feature-build/tools/05field guides/docs/project-templates/app-feature-build/field-guides/06qualification/docs/project-templates/app-feature-build/qualification/

Held source-proposed extensions

  • /docs/projects/app-feature-build/requirements
  • /docs/projects/app-feature-build/workback
  • /docs/projects/app-feature-build/review-boundaries

These extension paths are not generated by this record and must not be treated as resolving routes.

Public claim boundary

Allowed items below are source-lane proposals, not verified current-state claims.

Candidate claims allowed after source review

  • This is a proposed project-record and form design for a source-bound app-feature workflow.
  • The design includes intake, scope, milestones, deadlines, dependencies, owners, workbacks, evidence, approvals, risks, and closure.
  • The observed native contract includes local or indexed Notebook surfaces for projects, to-dos, agenda, files, approvals, notes, and field guides.
  • External provider, credential, database, customer, publication, and production effects are held.

Claims held

  • The feature is deployed or production-ready.
  • A project backend, database, provider connection, credential flow, customer index, or publication pipeline is connected.
  • Any project, milestone, approval, evidence item, or deadline has been created or persisted in production.
  • A named app route proves a connected web feature.
  • A project is qualified, approved externally, or complete beyond its recorded local review state.

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/
  • Notebook records provenance and revision contract
  • Current GuthHub app routes and held web boundary