Instrument qualification — field guides

Record status

Record ID

project:instrument-qualification

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 record with a stable canonical ID, provenance, revision, tags, and proposed lifecycle.
2. Complete intake and select one or more exact instrument slugs from the allowed verified-instrument directory.
3. Record scope, exclusions, authority boundaries, and held production or provider effects.
4. Assign project, instrument, test, accessibility, documentation, approval, and closure owners.
5. Create milestones and dependencies with explicit exit criteria.
6. Create deadline and workback to-dos using dueAt, priority, completion state, tags, and revisions.
7. Link the project to the relevant local Notebook records, files, notes, guides, and specialist-app surfaces; do not imply that a named route is connected.
8. Execute bounded test cases and preserve source-labelled evidence and reproducibility notes.
9. Review accessibility, validation, error handling, performance observations, and failure states.
10. Log risks, blockers, exceptions, and remediation decisions.
11. Submit scope, evidence, exceptions, and final outcome through local Approvals.
12. Close only after required evidence, approvals, documentation, and dependency checks pass; otherwise mark Held or Not qualified with a reason.

Handoff boundary

• A selected instrument slug may be mistyped or may not correspond to a locally available instrument record; retain the selection as unresolved rather than inventing a record.
• Prototype routes may appear functional without connected web, provider, credential, database, customer, publication, or production effects.
• Evidence may be irreproducible if inputs, expected results, environment, timestamps, or revisions are omitted.
• A deadline may be treated as an external calendar write even though Agenda is only a source-bound prototype/index surface.
• Agents may be granted authority beyond the recorded boundary; require human review and preserve Agent receipts.
• Sensitive files may be referenced without protected upload or storage; keep local references and access state explicit.
• Accessibility regressions may be missed if testing covers only successful paths and not validation, blocked, held, and error states.
• A project may be closed on verbal approval without a durable approval record.
• Instrument limitations, errata, or educational-only boundaries may be omitted from public-facing claims.
• Date changes may erase the original workback unless revisions and change reasons are retained.

Sources and evidence

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

• source_record:project:instrument-qualification
• project:instrument-qualification
• NotebookCollectionKind.project
• NotebookTodoPayload.dueAt
• Notebook Agenda deadlines/workbacks
• Observed native contract: records, PointGuard, 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/
• Notebook records canonical IDs, origin, source locators, source SHA-256, provenance, revisions, lifecycle, tags, links, and attachments
• PointGuard persistent cross-app context surface
• /app/pointguard/