Customer indexing — field guides

Record status

Record ID

project:customer-indexing

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 and identify the project owner.
2. Record consent, authorized domains, visibility, private-content exclusions, and prohibited paths.
3. Draft inclusion, exclusion, canonicalization, retention, and human-review rules.
4. Create milestones for intake review, scope review, proposed crawl plan, local index review, approval review, and closure.
5. Create deadline to-dos with dueAt, priority, completion state, tags, revisions, and scheduled/deadline views.
6. Build the reverse workback from the proposed completion date, including review buffers and dependency gates.
7. Assign owners, reviewers, evidence custody, approval authority, and human-only decisions.
8. Link only observed Notebook, PointGuard, Files, Agenda, To-dos, Approvals, Projects, Field Guides, Agent Logs, and Search surfaces as proposed support.
9. Attach source-labelled evidence and preserve provenance, revisions, and visibility labels.
10. Run deterministic acceptance tests on scope, privacy exclusions, accessibility, evidence, dates, and held effects.
11. Submit the proposal for human approval before any crawl, index write, message send, publication, provider connection, credential use, database action, or customer exposure.
12. Record closure, unresolved risks, retention actions, and confirmation that external and production effects remain held.

Handoff boundary

• Consent may be absent, stale, ambiguous, or narrower than the proposed URL scope.
• Private, authenticated, customer-only, or sensitive content may be accidentally included.
• A named native route may be mistaken for a connected web feature or canonical backend.
• Provider, credential, database, crawl, customer, publication, or production effects may be performed without approval.
• URL canonicalization, parameters, redirects, duplicates, or content-type rules may expand scope unexpectedly.
• Deadline drift or timezone ambiguity may hide missed review gates.
• Evidence may lack source locators, provenance, visibility labels, or revision history.
• Agent authority may be broader than the approved project scope.
• Search results may expose held or private records across visibility partitions.
• Accessibility defects may prevent keyboard, screen-reader, zoom, or narrow-screen users from completing review.
• Unsupported public claims may be inferred from a local prototype or proposed index.
• Closure may be declared while critical risks or unresolved dependencies remain.

Sources and evidence

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

• source_record:project:customer-indexing
• NotebookCollectionKind.project
• NotebookTodoPayload.dueAt
• Notebook Agenda deadlines/workbacks
• Observed native contract: records preserve canonical IDs, origin, source locators, source SHA-256, provenance, revision, 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
• App route: /app/notebook/projects/
• App route: /app/notebook/to-dos/
• App route: /app/notebook/agenda/
• App route: /app/notebook/approvals/
• App route: /app/notebook/files/
• App route: /app/notebook/field-guides/
• App route: /app/notebook/agent-logs/
• App route: /app/notebook/search/
• App route: /app/pointguard/
• Notebook record provenance and revision contract
• PointGuard persistent cross-app context surface
• Current GuthHub local prototype and index routes
• customer-indexing project source record