Engineering build — field guides

The distinct field guides 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.

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 a canonical ID, origin, source references, lifecycle, and project owner.
Complete intake and identify the requested outcome, audience, constraints, and decision needed.
Draft the scope baseline, including explicit non-goals, assumptions, qualification boundaries, and held external effects.
Break the scope into milestones with deliverables, owners, prerequisites, acceptance criteria, and evidence requirements.
Set the target completion date and generate a workback of deadline to-dos with dueAt, priority, completion state, tags, and revision history.
Register dependencies and review each dependency before its blocking milestone begins.
Confirm owners, decision authority, backups, handoffs, and acknowledgement states.
Link only the tools and guides needed for the bounded work; record unavailable or held surfaces as failure states.
Execute milestone work in the designated specialist surface while keeping canonical records there; use PointGuard only as cross-app context.
Attach source-labelled evidence and record pass, fail, blocked, or not-run outcomes for each acceptance criterion.
Submit scope changes, qualification results, risks, and external-effect proposals for human approval.
Reconcile milestones, deadlines, dependencies, evidence, approvals, and risks before closure.
Complete the closure form, preserve unresolved items and held claims, and create any follow-up to-dos.

Handoff boundary

A proposed route or interface may be mistaken for a connected production capability.
Silent date changes can invalidate the workback; revisions and change reasons must be preserved.
Unowned dependencies can create hidden blockers and missed deadlines.
Incomplete evidence may be mistaken for qualification.
Approval of a local proposal must not be presented as execution of an external action.
Attachments may contain sensitive material; file references must expose type, size, source, and access state without implying protected upload.
Scope drift can consume capacity without a new baseline and approval.
Accessibility failures in dense milestone, risk, or dependency tables can hide blockers from keyboard and assistive-technology users.
Instrument or provider selection without an exact verified directory match must be held rather than invented.

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: project_and_field_guide_collections
Observed native contract: deadlines
Observed native contract: records
Observed native contract: pointguard
/app/notebook/projects/
/app/notebook/to-dos/
/app/notebook/agenda/
/app/notebook/approvals/
/app/notebook/files/
/app/notebook/field-guides/
/app/notebook/agent-logs/
/app/pointguard/
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