Customer implementation — field guides

The distinct field guides 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.

Related field-guide records

/app/notebook/field-guides/

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

Operating sequence

Create the project record with canonical ID, origin, provenance, lifecycle, visibility, and tenant/effect isolation statements.
Complete intake and identify customer context, owners, target outcome, dates, and source records.
Draft scope, explicitly marking excluded capabilities and all provider, credential, database, customer, publication, and production effects as held unless separately verified.
Create milestones and derive deadline todos and workback dates from the target completion date.
Record dependencies, owners, review authority, fallback plans, and escalation paths.
Select only proposed tools, guides, and records whose authority boundaries are understood; do not treat named routes as connected web features.
Prepare configuration and communication drafts in local or held surfaces.
Collect source-labelled evidence, file references, revisions, and receipts for each completed milestone.
Run deterministic acceptance tests and record failures, missing evidence, and rework tasks.
Submit scope, configuration, acceptance, and closure decisions through human review.
Complete closure only when required evidence, approvals, handoff ownership, open items, and held effects are recorded.

Handoff boundary

Confusing a named native surface with a connected or production web feature.
Cross-tenant record leakage through shared context, links, attachments, search, or PointGuard rooms.
Unreviewed provider, credential, database, customer, publication, communication, or production effects.
Silent deadline changes that erase accountability or invalidate the workback.
Missing provenance, source locators, revisions, or evidence receipts.
Closing a project with unresolved blocking dependencies or unsupported completion claims.
Overbroad scope that turns configuration into unauthorized implementation.
Accessibility failures in multi-step forms, validation, focus order, contrast, keyboard operation, or status communication.
Treating Agent activity as authoritative without inspecting authority, receipts, and human approval.
Publishing doorway or keyword-spam documentation instead of distinct, useful source-backed content.

Sources and evidence

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

source_record:project:customer-implementation
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/approvals/
/app/notebook/files/
/app/notebook/field-guides/
/app/notebook/agent-logs/
/app/pointguard/
project:customer-implementation
Observed native contract: records preserve canonical IDs, provenance, revisions, lifecycle, tags, links, attachments, and record revisions
Observed native contract: PointGuard is a persistent cross-app context surface and specialist apps remain execution and canonical-record owners
Observed native contract: provider, credential, database, customer, publication, and production effects are held