Page actions
project template / candidate
Website surface — tools
The distinct tools record for Website surface. This page is proposal-only.
Status: proposedLifecycle: candidate
Record status
- Record ID
- project:website-surface
- 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) — Owns the project grouping, lifecycle, membership ordering, and linked evidence.
- Notebook Paper (interface · required) — Owns local website copy and revision history.
- Notebook Notes (interface · required) — Stores source-labelled research, decisions, and review notes.
- Notebook Files (interface · required) — Stores local file references and metadata without implying upload or protected storage.
- Notebook To-dos (interface · required) — Owns deadlines, priorities, completion state, tags, and human-review signals.
- Notebook Agenda (interface · required) — Displays source-bound time blocks and drafts schedule changes while provider writes remain held.
- Notebook Approvals (interface · required) — Owns human review decisions and preserved receipts.
- Notebook Search (interface · required) — Filters linked local records while respecting private and held visibility.
- PointGuard (interface · required) — Carries the current project context across Notebook surfaces without taking canonical-record ownership.
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
- A proposed route may be mistaken for a deployed URL or connected website.
- Unsupported claims may be copied into public drafts if claim status is not prominent.
- External links may be stale, inaccessible, unsafe, or unverifiable from the local prototype.
- Contrast results may be treated as complete accessibility compliance rather than one gate among several.
- Workback dates can be misleading when estimates, dependencies, holidays, or timezone assumptions are wrong.
- Local persistence may be cleared, corrupted, or unavailable; the interface must not imply durable server authority.
- File references may be mistaken for uploaded or protected assets.
- Approval may be mistaken for publication authorization or a completed release.
- Search could expose private notes, held claims, or review evidence across visibility boundaries.
- Automated or instrument-derived results may be overtrusted without human review.
Sources and evidence
These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.
source_record:project:website-surfaceproject:website-surfaceNotebookCollectionKind.projectNotebookTodoPayload.dueAtNotebook Agenda deadlines/workbacksNotebook records provenance and revision contractPointGuard persistent cross-app context surfaceAPP_ROUTES:/app/notebook/projects/APP_ROUTES:/app/notebook/field-guides/APP_ROUTES:/app/notebook/approvals/APP_ROUTES:/app/notebook/paper/ALLOWED_INSTRUMENTS:wcag-contrast-ratio-checkerALLOWED_INSTRUMENTS:reading-time-estimator