Engineering build — deadlines

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.

Deadline and workback rules

• Every milestone must have a planned finish date, owner, acceptance criteria, and required evidence or an explicit held status.
• Every deadline must include a date, time zone, owner, priority, and source or rationale.
• Workback tasks are derived from the target completion date and recorded as separate to-dos; changing the target date creates a revision rather than silently rewriting history.
• A hard deadline requires an approval or decision checkpoint before the date; an unresolved blocker changes the milestone to blocked or held.
• Overdue items remain visible in Today and To-dos until completed, rescheduled with a reason, or explicitly held.
• External sends, provider writes, publication, credential use, database changes, customer indexing, and production effects remain human-held and must be represented as approval or risk items.
• Qualification deadline is required before a workback can be generated.
• Store dueAt with timezone and display the absolute date and local relative status.
• Reject or visibly flag milestones and tasks that fall after the qualification deadline unless explicitly marked exception.
• Generate workback tasks backward from the qualification deadline using declared durations and buffer; never invent provider availability.
• Mark overdue, due today, blocked, and missing-owner states with text labels and icons, not color alone.
• Changing the qualification deadline creates a revision and requires explicit confirmation before recalculating dependent tasks.
• Recurring tasks remain recurrence candidates until a human confirms recurrence.
• External calendar writes, notifications, messages, deployments, publication, and provider changes remain Held.

Workback sequence

1. Create the project record and assign a human owner.
2. Write the bounded problem statement, scope exclusions, assumptions, and dependencies.
3. Define acceptance tests and the evidence required for qualification.
4. Set a qualification deadline and generate a workback of milestones and to-dos.
5. Link source-labelled notes, file references, and applicable field guides.
6. Execute tasks locally while preserving task revisions, blockers, and completion state.
7. Review implementation evidence and record failures or exceptions.
8. Submit the qualification proposal to local review; keep unresolved items Needs review or Held.
9. Project a compact current-work summary into PointGuard without transferring canonical ownership.
10. Mark the project lifecycle locally only after the human reviewer records the decision.

Scheduling records

• milestone records
• deadline and workback to-dos
• dependency records
• owner assignments
• project record with canonical ID, lifecycle, owner, scope, acceptance criteria, source provenance, revisions, links, and attachments
• milestone and task to-dos with dueAt, priority, tags, completion state, and revisions
• agenda deadline and workback records

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