Page actions
field guide / candidate
Primary-source packets — prerequisites
The distinct prerequisites record for Primary-source packets. This page is proposal-only.
Status: proposedLifecycle: candidate
Record status
- Record ID
- field-guide:primary-source-packets
- Parent lifecycle
- candidate
- Page lane
- plan
- Lane lifecycle
- proposed
- Owner
- Socrates
- 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.
Entry evidence and required records
Before the procedure starts, an operator must identify the source, owner, scope, and required records below. Missing evidence holds the guide.
- field-guide:primary-source-packets
- source note for each included source
- source-labelled file reference for each supplied artifact
- comparison record
- uncertainty and limitation record
- study or lesson pathway record
- review receipt or approval record
- todo records for unresolved work
Intended operators and ownership
- Socrates
- researchers
- educators
- learners
- reviewers
Being listed as an intended operator does not grant execution or publication authority.
Conditions that hold the guide before entry
- Treating a named native route as proof of a connected web feature.
- Using secondary or unsupplied material as if it were a primary source.
- Losing source locators, SHA-256 values, origin, provenance, or revision history.
- Presenting interpretation, synthesis, or lesson framing as source fact.
- Overstating agreement when sources differ in scope, date, terminology, or context.
- Filling missing evidence through inference instead of marking uncertainty.
- Creating doorway or keyword-spam documentation instead of distinct useful records.
- Confusing local approval with publication, qualification, customer indexing, or production state.
- Scheduling external communication or provider effects that remain held by the web boundary.
- Accessibility failure caused by relying only on visual comparison or color-coded uncertainty.
Sources and evidence
These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.
source_record:field-guide:primary-source-packetsagents/index.html#socratesobserved_native_contract.project_and_field_guide_collectionsobserved_native_contract.deadlinesobserved_native_contract.recordsobserved_native_contract.pointguardapp_route:/app/pointguard/app_route:/app/notebook/field-guides/app_route:/app/notebook/notes/app_route:/app/notebook/files/app_route:/app/notebook/projects/app_route:/app/notebook/to-dos/app_route:/app/notebook/approvals/app_route:/app/notebook/agent-logs/