Engineering build — tools

The distinct tools record for Engineering build. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: project:engineering-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 project scope, lifecycle, links, evidence, and revisions.
Notebook To-dos (interface · required) — Tracks executable work with due dates, priority, completion state, tags, recurrence candidates, and revisions.
Notebook Agenda (interface · required) — Displays qualification deadlines, milestones, conflicts, and draft workback changes.
Notebook Files (interface · required) — Stores source-labelled local file references while upload and protected storage remain held.
Notebook Approvals (interface · required) — Preserves human decisions and receipts for qualification or proposed external effects.
Notebook Agent Logs (interface · required) — Shows Agent authority, current work, receipts, and boundaries.
PointGuard (interface · required) — Provides a persistent cross-app projection of current project context while Notebook remains the canonical owner.
Engineering build field guide (guide · optional) — Provides a source-backed bounded procedure when one is available; absence must be visible.

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 project workspace may be mistaken for a connected production backend; every surface must label local prototype and proposal-only state.
A deadline workback can create false certainty when task durations, dependencies, or buffers are unknown; expose assumptions and allow explicit exceptions.
Incomplete or stale source evidence can make qualification appear stronger than it is; show provenance, revision, and evidence freshness.
PointGuard context may be mistaken for canonical project data; preserve the Notebook ownership label and source link.
Agent suggestions may be mistaken for completed engineering work; distinguish proposed, in progress, blocked, reviewed, and completed states.
Local persistence may be lost or cleared; provide export as a held local action and disclose that protected backup is unavailable.
External messages, scheduling, deployment, publication, uploads, credentials, provider connections, customer indexing, and production database effects are held.

Sources and evidence

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

source_record:project:engineering-build
project:engineering-build
NotebookCollectionKind.project
NotebookTodoPayload.dueAt
Notebook Agenda deadlines/workbacks
observed native contract: records and provenance
observed native contract: PointGuard persistent cross-app context surface
observed native contract: web boundary holds provider, credential, database, customer, publication, and production effects