Source: https://guthlabs.ai/docs/project-templates/app-feature-build/tools/ project template / candidate # App feature build — tools The distinct tools 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]() — 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. ## Authoritative app_features lane tools and interfaces ### Canonical tools-page assignments - **Notebook Projects** (interface · required) — Canonical local owner for the project record, membership ordering, lifecycle, and linked evidence. - **Notebook To-dos** (interface · required) — Stores milestones and work items with dueAt, priority, completion, tags, revisions, and deadline views. - **Notebook Agenda** (interface · required) — Displays time blocks, deadline conflicts, and drafted schedule changes while provider writes remain held. - **Notebook Approvals** (interface · required) — Records human review decisions as Needs review, Approved, or Held with receipts. - **Notebook Search** (interface · required) — Filters locally indexed project, requirement, note, file-reference, to-do, and approval records while respecting visibility. - **PointGuard** (interface · required) — Provides the persistent cross-app current-work projection without taking canonical ownership from Notebook. - **Agent Logs** (interface · required) — Exposes bounded Agent activity, authority, receipts, and current state. Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved. ## Authoritative lane instrument assignments ### Canonical tools-page assignments No verified instrument is assigned to this tools lane. An instrument listed only for another lane does not become a tools-page assignment. ## Use boundary - A named native surface may be mistaken for a connected web feature; label all behavior as local prototype or proposal. - Source references may be incomplete, stale, or mismatched; preserve provenance and expose unknowns rather than filling gaps. - Automatic date shifting can silently change commitments; require explicit confirmation and revision receipts. - Circular or missing dependencies can create false confidence in the workback. - PointGuard projection may become a duplicate canonical record; keep it read-through or link-based. - Local persistence may contain sensitive project material; show storage scope and provide deliberate clearing controls. - Accessibility regressions may hide validation, deadline, or held-state information from keyboard and assistive-technology users. - Agent suggestions may be mistaken for approvals; display authority, status, and receipt boundaries. - External sends, provider writes, uploads, protected storage, deployment, publication, and customer-facing changes remain held. ## 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` - `project:app-feature-build` - `NotebookCollectionKind.project` - `NotebookTodoPayload.dueAt` - `Notebook records provenance, revisions, links, and attachments` - `Notebook Agenda deadlines/workbacks` - `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/`