Page actions
field guide / candidate
Qualification records — related jobs
The distinct related jobs record for Qualification records. This page is proposal-only.
Record status
- Record ID
- field-guide:qualification-records
- Parent lifecycle
- candidate
- Page lane
- plan
- Lane lifecycle
- proposed
- Owner
- Tilly
- Owner role
- Not separately recorded
- Owner status
- Not separately recorded
- Qualification result
- NOT RUN · held for evidence and human review
Working browser surface: Field guides — documentation — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.
Related Agent job handoffs
Handoff record requirements
The guide may supply evidence, checkpoints, and failure context to a job. The receiving job retains ownership and must record its own decision, approval, and receipt.
- Source-labelled qualification note
- Qualification evidence record
- Instrument reference record, if an instrument is used
- Evidence reconciliation record
- Review or approval record
- Deadline todo with owner and dueAt
- Revision and provenance receipt
- source-labelled notes
- file references
- to-dos with due dates and review state
- approval records
- agent receipts and authority logs
- instrument result records
- claim-to-evidence links
Ownership boundary
The guide supports these jobs without importing their package descriptions, becoming the job owner, or gaining independent authority.
- A named native surface may be only a local prototype or index and does not prove a connected web feature.
- A checksum result can verify supplied data integrity but cannot prove source authority, truth, qualification, or publication status.
- Instrument outputs may be mistaken for evidence; inputs, assumptions, units, and limitations must remain attached.
- Conflicting revisions may be silently overwritten unless every material change preserves revision history.
- Local approval may be misrepresented as external approval or production authorization.
- Private, held, and public contexts may be conflated during search or linking.
- Missing source locators or hashes can lead to unsupported claims.
- Deadline todos can be mistaken for automation or completed external work.
- Accessibility failures can exclude reviewers if focus order, labels, status text, and keyboard operation are not preserved.
Sources and evidence
These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.
source_record:field-guide:qualification-recordsagents/index.html#tillyfield-guide:qualification-recordsOBSERVED_NATIVE_CONTRACT.recordsOBSERVED_NATIVE_CONTRACT.deadlinesOBSERVED_NATIVE_CONTRACT.pointguardAPP_ROUTES:/app/notebook/field-guides/APP_ROUTES:/app/notebook/notes/APP_ROUTES:/app/notebook/files/APP_ROUTES:/app/notebook/to-dos/APP_ROUTES:/app/notebook/approvals/APP_ROUTES:/app/notebook/search/APP_ROUTES:/app/notebook/agent-logs/ALLOWED_INSTRUMENTS:checksum-verifierALLOWED_INSTRUMENTS:date-duration-calculatorObserved native contract: Notebook collections, deadlines, records, PointGuard, and held web boundaryApp routes: /app/notebook/field-guides/App routes: /app/notebook/approvals/App routes: /app/notebook/agent-logs/App routes: /app/notebook/files/App routes: /app/notebook/messages/App routes: /app/notebook/notes/App routes: /app/notebook/search/App routes: /app/notebook/to-dos/App routes: /app/notebook/agenda/App routes: /app/pointguard/