Website surface — field guides

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.

Related field-guide records

• /app/notebook/field-guides/

Source-proposed guide paths are references, not proof that those paths resolve.

Operating sequence

1. Create the project intake record and assign a project owner.
2. Define scope, audience, release definition, claim boundary, crawl intent, and accessibility target.
3. Create milestones and deliverables with owners, dependencies, evidence requirements, and acceptance criteria.
4. Set the target release date and generate a workback of review, content, accessibility, crawl, and release deadlines.
5. Record dependencies and handoffs; mark the project blocked when a required prerequisite is missing.
6. Link only the relevant local tools, guides, records, and held-capability notes.
7. Capture source-labelled evidence for claims, content decisions, accessibility checks, crawl decisions, and release readiness.
8. Submit each gate to Notebook Approvals and preserve Needs review, Approved, or Held decisions.
9. Review risks and unresolved issues before any release decision.
10. Close only when required evidence and approvals are complete; preserve deferred work, held claims, and final revisions.

Handoff boundary

• Unsupported or stale public claims may pass planning without evidence.
• A named native route may be mistaken for a connected web, provider, publication, or production feature.
• Deadline changes can hide slippage unless revisions, reasons, and prior dates are preserved.
• Missing dependency owners can leave work silently blocked.
• Approval status may be confused with external publication or deployment.
• Local file references may be mistaken for uploaded or protected assets.
• Accessibility checks may be asserted without recorded method, scope, or evidence.
• Crawl or indexing intent may be mistaken for actual customer indexing.
• Sensitive private work may be exposed if visibility classification and search partitioning are not respected.
• Overly long forms may create abandonment; sections should support save-and-resume, concise validation, and clear progress.

Sources and evidence

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

• source_record:project:website-surface
• 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_ROUTES:/app/notebook/projects/
• APP_ROUTES:/app/notebook/to-dos/
• APP_ROUTES:/app/notebook/agenda/
• APP_ROUTES:/app/notebook/approvals/
• APP_ROUTES:/app/notebook/notes/
• APP_ROUTES:/app/notebook/files/
• APP_ROUTES:/app/notebook/field-guides/
• APP_ROUTES:/app/notebook/search/
• APP_ROUTES:/app/pointguard/
• project:website-surface
• Notebook records provenance and revision contract
• PointGuard persistent cross-app context surface
• APP_ROUTES:/app/notebook/paper/
• ALLOWED_INSTRUMENTS:wcag-contrast-ratio-checker
• ALLOWED_INSTRUMENTS:reading-time-estimator