Source: https://guthlabs.ai/docs/field-guides/primary-source-packets/steps/ field guide / candidate # Primary-source packets โ€” steps The distinct steps record for Primary-source packets. This page is proposal-only. Status: **proposed**Lifecycle: **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. ## Ordered procedure - 1. Open the proposed guide from Notebook Field Guides and establish a PointGuard room for the current packet. Confirm that this is planning work and that the named surfaces are prototype or indexed interfaces rather than proof of connected production behavior. - 2. Create the packet project record in Notebook Projects. Set the owner to Socrates, identify a human reviewer, define the inquiry question, intended use, audience, visibility, and target review date. Checkpoint: no packet proceeds without a bounded question, owner, and reviewer. - 3. Inventory only supplied primary-source material and supplied artifacts. Create one source note and one source-labelled file reference per item where applicable. Record origin, locator, source SHA-256 when supplied, revision, and provenance. Failure branch: if a source locator, artifact identity, or provenance value is missing, mark the item Held and request the missing evidence; do not fill the gap from inference. - 4. Inspect each source note in Notebook Notes and each file reference in Notebook Files. Confirm that the source label is visible, the record ID is stable, and the file reference does not imply hidden upload or protected storage. Checkpoint: every excerpt must map to exactly one source record and locator. - 5. Extract bounded evidence. Record quotations or paraphrases separately, preserve surrounding context, and label uncertainty whenever the source is incomplete, ambiguous, contested, or unavailable for verification. Failure branch: if an excerpt cannot be located or its wording is uncertain, exclude it from supported claims and create an uncertainty record instead. - 6. Build the comparison record in Notebook Projects or Notes. For each comparison question, list source-supported agreements, differences, scope limits, and missing evidence. Do not convert disagreement into a resolution without an explicit source basis. Checkpoint: every material statement has a source record and locator or is labelled interpretation, question, or uncertainty. - 7. Draft the guided inquiry, lesson pathway, or study record. Link each activity to evidence records, include prompts that distinguish observation from interpretation, and provide an accessibility accommodation such as plain-language restatement, keyboard-operable review, or a non-visual description of the evidence structure. - 8. Create bounded to-dos for unresolved locators, reviewer questions, accessibility checks, and revision work. Use due dates, priorities, tags, completion state, and recurrence only when explicitly intended. Work back from the target review date: evidence lock before pathway drafting, draft review before final review, and final review before any proposed release decision. - 9. Submit the packet to Notebook Approvals with the state Needs review. Preserve the proposed decision, reviewer identity, source context, and receipt. Failure branch: if the reviewer cannot verify a claim, source locator, or accessibility requirement, set the packet to Held, create a corrective todo, and retain the prior revision rather than overwriting it. - 10. Record the review outcome and revision. Approved means only that the designated human reviewer approved the local proposal for its stated use; it does not mean publication, customer indexing, provider connection, database authority, or production qualification. Held items remain excluded from supported claims until evidence is added. - 11. Inspect Notebook Agent Logs for the packet's authority boundary, current work, and receipts. Confirm that Socrates performed only the bounded preparation described here and that any external send, publication, upload, or provider write remains human-held. - 12. Mark the field guide instance complete only when all completion criteria pass; otherwise keep it proposed or held with a documented failure reason. ## Deadline and chronology rules - Set a target review date before source extraction begins. - Work backward from review: unresolved-source deadline, evidence-lock deadline, pathway-draft deadline, accessibility-review deadline, and final human-review deadline. - Every unresolved locator, ambiguity, or correction receives a due date and owner. - If a deadline passes, keep the packet in Needs review or Held; do not treat lateness as completion. - Do not schedule external publication, provider writes, customer communication, or production actions from this guide. ## Failure branches during execution - 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-packets` - `agents/index.html#socrates` - `observed_native_contract.project_and_field_guide_collections` - `observed_native_contract.deadlines` - `observed_native_contract.records` - `observed_native_contract.pointguard` - `app_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/`