Native release — tools

The distinct tools record for Native release. This page is proposal-only.

Status: proposedLifecycle: candidate

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.

Authoritative app_features lane tools and interfaces

Canonical tools-page assignments

Notebook Projects (interface · optional) — Owns the local project grouping, lifecycle, links, and evidence context.
Notebook To-dos (interface · optional) — Owns milestone completion, due dates, priorities, tags, and review signals.
Notebook Agenda (interface · optional) — Shows source-bound deadline and workback views while external calendar writes remain held.
Notebook Files (interface · optional) — Stores local, source-labelled file references without implying hidden upload or protected storage.
Notebook Approvals (interface · optional) — Captures proposed release decisions and preserves local receipts.
PointGuard (interface · optional) — Provides persistent cross-app context while Notebook remains the canonical owner of project records.

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 prepared build reference may be mistaken for a verified or signed Apple build.
A local approval may be mistaken for App Store qualification, submission, publication, or release.
Stale or incomplete evidence may create false confidence in readiness.
Deadline changes can silently invalidate dependent work unless a preview and confirmation are required.
File references may expose sensitive paths or metadata; show only permitted metadata and keep upload/protected storage held.
Provider, credential, database, customer, notification, payment, publication, and production effects must remain held.
Accessibility status can be overstated if it is only self-attested; distinguish unchecked, self-reviewed, and evidenced states.
Duplicate project or milestone records can split ownership; surface canonical IDs and revision conflicts.

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 records provenance, revisions, links, and attachments
Notebook Agenda deadlines/workbacks
PointGuard persistent cross-app context surface
Web boundary: provider, credential, database, customer, publication, and production effects are held
/app/notebook/projects/
/app/notebook/to-dos/
/app/notebook/agenda/
/app/notebook/files/
/app/notebook/approvals/
/app/pointguard/