Native release — deadlines

Record status

Record ID

project:native-release

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

• A decision deadline must include date, time, timezone, owner, and hard or soft classification.
• Every milestone must have an owner, planned finish, exit criteria, and at least one linked to-do or an explicit reason none is needed.
• Workback dates are derived planning values only; external calendar or provider writes require human confirmation and remain held.
• A task may not be marked complete when its required evidence, dependency confirmation, or approval is missing.
• Overdue hard deadlines require a visible risk record and reviewer notification task.
• Conflicting deadlines must remain visible until a human resolves them; the system must not silently reschedule them.
• Changes to scope, decision date, owner, or acceptance criteria create a revision and preserve the prior value.
• A target decision date is optional; when absent, show the project as date-unset rather than inventing a deadline.
• A milestone due date must include a valid local date and time or remain explicitly unscheduled.
• Workback generation must be deterministic: preserve manually entered milestones and calculate only named offsets from the target decision date.
• Flag milestones due today, overdue, blocked, or missing an owner without silently changing their state.
• Changing the target decision date must preview affected calculated milestones and require confirmation before applying changes.
• Completed milestones remain visible in history and cannot be treated as evidence of external release.
• Recurring tasks require an explicit human-selected recurrenceCandidate and must not create hidden automation.

Workback sequence

1. Create the Native release project record and assign an owner.
2. Set a target decision date or mark the date as undecided.
3. Add scope, local build references, known limitations, and source-labelled evidence links.
4. Generate or manually add workback milestones in Agenda and To-dos.
5. Review accessibility, functional evidence, metadata readiness, and unresolved risks.
6. Open each proposed decision in Approvals and preserve reviewer identity, rationale, and receipts.
7. Use PointGuard to view current release context without changing specialist record ownership.
8. Mark the project Approved, Needs review, or Held locally; do not send, upload, publish, submit, or change provider state.
9. Record any next action and its dueAt value, then retain the revision history.

Scheduling records

• milestone records
• deadline and workback to-dos
• dependency records
• owner assignments
• Release milestone to-dos with dueAt, priority, completion state, tags, revisions, and deadline view

Sources and evidence

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

• source_record:project:native-release
• 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
• Observed native contract: web_boundary
• /app/notebook/projects/
• /app/notebook/to-dos/
• /app/notebook/agenda/
• /app/notebook/files/
• /app/notebook/approvals/
• /app/notebook/paper/
• /app/notebook/agent-logs/
• Notebook records provenance, revisions, links, and attachments
• PointGuard persistent cross-app context surface
• Web boundary: provider, credential, database, customer, publication, and production effects are held
• /app/pointguard/