Primary-source packets — qualification

Record status

Record ID

field-guide:primary-source-packets

Parent lifecycle

candidate

Page lane

docs_urls

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.

Qualification status

Result

NOT RUN

Disposition

HELD

Reviewer

Not recorded

Receipt

Not recorded

This page defines proposed acceptance criteria for the docs_urls lane. It does not execute tests, establish compliance, qualify the subject, or authorize an effect.

Outcome definitions

Verified

All stated evidence and acceptance requirements passed for the exact reviewed revision; this still does not authorize deployment or an external effect.

Failed

One or more deterministic acceptance requirements failed with an inspectable reason.

Needs review

Evidence or interpretation is incomplete, conflicting, or awaits an identified human reviewer.

Held

Authority, required evidence, safe execution conditions, or a principal gate is absent.

The current record remains NOT RUN / HELD. These definitions describe candidate outcomes only.

Proposed deterministic acceptance tests

Route-resolution and distinct-content checks apply only to the admitted canonical routes in this record. Held source-proposed extensions are non-resolving proposals and are excluded.

• Every documentation route has a distinct purpose and includes content not duplicated from the overview.
• The overview identifies the packet’s scope, audience, owner, lifecycle, limitations, and links to the detailed routes.
• Each source entry requires a locator, origin, provenance note, and a clear distinction between observed source content and interpretation.
• Comparison pages show agreement, disagreement, missing evidence, and uncertainty rather than a single unsupported synthesis.
• Forms support keyboard navigation, visible labels, required-field messaging, readable status text, and non-color-only uncertainty states.
• Examples use clearly labelled hypothetical records and do not imply customer data, publication, provider connection, or production qualification.
• Qualification requires human review for unresolved provenance, contested interpretation, sensitive context, accessibility gaps, and missing evidence.
• Related-job pages link only to the supplied jobs: Guided inquiry, Source comparison, Lesson pathways, Study records, and Uncertainty marking.
• App links open only observed native surfaces and preserve the boundary that local prototypes or indexes are not connected production systems.
• Acceptance evidence records canonical IDs, source locators, provenance, revisions, lifecycle, and review receipts where available.

Negative and held-state tests

• A secondary summary may be mistaken for a primary source; label source type and provenance explicitly.
• Conflicting sources may be flattened into a false consensus; preserve disagreement and context.
• Educational interpretation may be mistaken for fact or professional advice; use bounded language and review states.
• Incomplete or inaccessible source material can undermine comparison; mark gaps and provide accessible text alternatives where available.
• Sensitive historical or personal material may require additional contextual review before classroom or group use.
• A named app surface does not prove a connected web feature; keep provider, credential, database, customer, publication, and production effects held.
• Instrument outputs are estimates or calculations only and must not replace source inspection or human qualification.

Qualification claim boundary

Potentially allowed only after the stated evidence

• A proposed field-guide structure can describe how to assemble and compare source-labelled records.
• The guide can document observed local prototype or index routes as possible working surfaces.
• The guide can identify Socrates as the supplied owner agent for the related inquiry and study jobs.
• The guide can specify human-review states, provenance fields, uncertainty markers, workback rules, and acceptance tests.

Still held

• Deployment or publication of the field guide.
• Connection to a provider, credential, database, customer workspace, external calendar, or protected storage service.
• Qualification, approval, accuracy, completeness, or rights clearance of any source packet.
• Automatic source discovery, citation verification, message sending, scheduling, or lesson delivery.
• Customer indexing, public search availability, or production readiness.

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.records
• observed_native_contract.deadlines
• observed_native_contract.pointguard
• /app/notebook/field-guides/
• /app/notebook/notes/
• /app/notebook/files/
• /app/notebook/approvals/
• /app/notebook/search/