Page actions
project template / candidate
Customer implementation — tools
The distinct tools record for Customer implementation. This page is proposal-only.
Status: proposedLifecycle: candidate
Record status
- Record ID
- project:customer-implementation
- 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 · required) — Canonical project grouping and lifecycle surface.
- Notebook To-dos (interface · required) — Stores milestones, dueAt values, priorities, completion state, tags, and revisions.
- Notebook Agenda (interface · required) — Displays source-bound deadlines, conflicts, and draft schedule changes while provider writes remain held.
- Notebook Files (interface · required) — Keeps source-labelled file references beside project records without hidden upload.
- Notebook Approvals (interface · required) — Provides local review states and receipts for proposed decisions.
- PointGuard (interface · required) — Projects current project context, next work, blockers, linked records, and held effects across app surfaces.
- Agent Logs (interface · optional) — Makes bounded assistance, authority, receipts, and current state inspectable.
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
An instrument listed only for another lane does not become a tools-page assignment.
Use boundary
- Tenant leakage through copied links, stale filters, global search, PointGuard context, or shared local storage.
- A project title or customer display name being mistaken for verified customer identity.
- Workback dates being treated as commitments despite uncertain duration or missing dependencies.
- Date and timezone conversion causing an incorrect deadline.
- Local prototype state being mistaken for a connected provider, database, or production configuration.
- Draft messages or schedule changes being accidentally represented as sent or externally applied.
- Sensitive customer information being entered into unsupported fields or file references.
- Stale revisions causing one local edit to overwrite another without warning.
- Accessibility failures from color-only status, keyboard traps, inaccessible drag reordering, or unannounced dynamic projections.
Sources and evidence
These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.
source_record:project:customer-implementationproject:customer-implementationNotebookCollectionKind.projectNotebookTodoPayload.dueAtNotebook Agenda deadlines/workbacksObserved native contract: records preserve canonical IDs, provenance, revisions, lifecycle, tags, links, attachments, and record revisionsObserved native contract: PointGuard is a persistent cross-app context surface and specialist apps remain execution and canonical-record ownersObserved native contract: provider, credential, database, customer, publication, and production effects are held/app/notebook/projects//app/notebook/to-dos//app/notebook/agenda//app/notebook/approvals//app/pointguard/