Page actions

project template / candidate

Engineering build — forms

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

Status: proposedLifecycle: candidate

Record status

Record ID: project:engineering-build
Parent lifecycle: candidate
Page lane: forms
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.

Proposed form sections

Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth.

Intake

Establish why the build is being proposed, who requests it, and what decision or outcome is needed.

project title
requester name and role
date submitted
problem statement
desired outcome
user or internal audience
known constraints
business or technical context
requested decision
urgency rationale
source references
initial status: proposed, needs clarification, or held

Scope and Boundaries

Define the smallest bounded build and explicitly record exclusions and authority limits.

in-scope capabilities
out-of-scope capabilities
inputs and outputs
supported environments
accessibility requirements
privacy or safety considerations
assumptions
non-goals
success measures
qualification boundary
external effects that remain human-held
scope owner
scope baseline version and date

Milestones and Deliverables

Turn scope into reviewable checkpoints with named owners and acceptance evidence.

milestone ID
milestone name
deliverable description
milestone owner
planned start
planned finish
review date
prerequisites
acceptance criteria
evidence required
status: proposed, active, blocked, complete, or held
revision note

Deadlines and Workback

Create source-bound deadlines and calculate a transparent workback from the target date.

target completion date
deadline label
deadline type: internal, review, qualification, or decision
time zone
hard or soft deadline
workback offset
derived task due date
task owner
priority
recurrence candidate
completion state
conflict note
revision history
schedule source

Dependencies

Identify work, records, people, or decisions that must exist before a milestone can proceed.

dependency ID
dependency description
dependency type: task, record, person, decision, file, or external input
blocking milestone
dependency owner
required-by date
status: open, ready, blocked, waived, or held
verification method
fallback or contingency
linked record IDs
last reviewed date

Owners and Responsibilities

Make accountability explicit without assuming identity-provider or production permissions.

role
person or team label
responsibility
decision authority
backup owner
availability note
handoff condition
acknowledgement state
effective date
end date
owner change reason

Tools and Guides

Record designated local surfaces, procedures, and bounded execution aids.

tool or guide name
kind: interface, skill, guide, record, or provider
purpose in this project
linked route or record
owner
required step
authority boundary
verification state
fallback if unavailable
last reviewed date

Evidence and Qualification

Capture reproducible evidence for each acceptance claim and distinguish observed facts from proposals.

evidence ID
claim or requirement tested
test method
preconditions
inputs or fixture reference
expected result
observed result
pass, fail, blocked, or not run
reviewer
timestamp
source locator
attachment or file reference
revision
qualification limitations

Approvals and Decisions

Preserve human review for scope, risk, qualification, and any held external effect.

approval ID
decision requested
decision owner
reviewers
proposal summary
options considered
decision: needs review, approved, or held
conditions
decision date
receipt or note reference
reconsideration trigger
external action explicitly not performed

Risks and Failure States

Make uncertainty, failure handling, and escalation visible before closure.

risk ID
risk statement
category
likelihood
impact
severity
trigger
mitigation
contingency
risk owner
due date
status: open, monitoring, mitigated, accepted, or held
escalation path
residual risk
last review date

Closure

Confirm what was completed, what remains unresolved, and whether the record may be archived or held.

closure date
completion summary
delivered items
accepted items
unfinished items
open risks
deferred scope
evidence completeness
approval completeness
handoff owner
maintenance or review date
lessons learned
closure decision: complete, incomplete, cancelled, or held
final record revision

Accessible state contract

Every field requires a visible and programmatic label.
Required and optional fields must be stated in text.
Invalid entries require an actionable message linked to the field.
Blocked and Held states remain visible without relying on color alone.

Supporting documentation fields

These fields come from the app_features lane and remain separate from the primary operating form.

Identity and ownership

Define the build and its accountable human owner.

title
short description
owner
contributors
canonical project ID
tags
visibility

Bounded scope

Record what will and will not be built.

problem statement
in-scope capabilities
out-of-scope capabilities
assumptions
dependencies
risk notes

Qualification target

Make completion testable before work begins.

acceptance criteria
required evidence
reviewer
qualification deadline
failure response

Deadlines and workback

Generate local milestones and tasks from a qualification deadline.

target date
timezone
milestones
task durations
buffer
priority
recurrence candidate
blocked-by links

Records and evidence

Attach source-labelled material without implying upload or publication.

linked notes
file references
field guide
agent log
approval records
source locator
source SHA-256

Held effects

Expose actions that require human review before any external change.

draft message
provider or destination
proposed change
approval state
receipt note

Required or proposed record references

No record existence is asserted by this documentation page.

project record
intake record
scope baseline
milestone records
deadline and workback to-dos
dependency records
owner assignments
tool and guide links
evidence records
approval records
risk records
closure record
project record with canonical ID, lifecycle, owner, scope, acceptance criteria, source provenance, revisions, links, and attachments
intake note
milestone and task to-dos with dueAt, priority, tags, completion state, and revisions
agenda deadline and workback records
source-labelled file references
qualification evidence and review receipt
approval record for any proposed external effect

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