Study records — field guides

Record status

Record ID

job:socrates:study-records

Parent lifecycle

candidate

Page lane

docs_urls

Lane lifecycle

proposed

Owner

Socrates

Owner role

University guide and tutor entity

Owner status

PROPOSED

Qualification result

NOT RUN · held for evidence and human review

Working browser surface: Agent jobs — builder overview — Inspect the package and stage a local project. 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 a study-record proposal and assign a canonical ID.
2. State the question, audience, objective, and high-stakes status.
3. Collect only supplied or explicitly cited source material; preserve locators and provenance.
4. Record claims separately from interpretation and mark disputed or unresolved evidence.
5. Compare sources using an inspectable note or synthesis record.
6. Compose a bounded learning path with prerequisites, practice, recall, and review points.
7. Create deadlines and workbacks for reading, practice, source checking, and human review.
8. Route high-stakes instruction, student identity data, external enrollment, and published curriculum claims to human review.
9. Hold the record when evidence is missing, disputed evidence is hidden, or tutoring is being treated as authority.
10. Preserve revisions, links, attachments, and review receipts before any later implementation decision.

Handoff boundary

• Invented or unverifiable primary sources could mislead learners.
• Disputed evidence could be hidden by an overconfident synthesis.
• Tutoring could be mistaken for institutional, academic, legal, medical, or other authoritative instruction.
• Student identity data could be collected or exposed without an approved boundary.
• External enrollment or publication could occur without human authorization.
• Prototype routes could be mistaken for connected production features.
• Accessibility needs could be lost when study paths are generated from unstructured notes.
• Missing provenance, revisions, or source hashes could make a study record difficult to inspect or reproduce.

Sources and evidence

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

• agents/index.html#socrates
• source_record:job:socrates:study-records
• observed_native_contract.project_and_field_guide_collections
• observed_native_contract.deadlines
• observed_native_contract.records
• observed_native_contract.pointguard
• app_routes:/app/notebook/field-guides/
• app_routes:/app/notebook/agent-logs/
• app_routes:/app/notebook/projects/
• app_routes:/app/notebook/approvals/
• app_routes:/app/pointguard/
• Observed native contract: records preserve canonical IDs, provenance, source locators, source SHA-256, revisions, lifecycle, tags, links, and attachments.
• Observed native contract: PointGuard is a persistent cross-app context surface while specialist apps remain execution and canonical-record owners.
• Observed app route: /app/notebook/notes/
• Observed app route: /app/notebook/files/
• Observed app route: /app/notebook/approvals/
• Observed app route: /app/notebook/field-guides/
• Observed app route: /app/notebook/agent-logs/
• Observed app route: /app/notebook/search/
• Observed app route: /app/pointguard/
• Allowed verified instrument: statistics-suite-descriptive-stats
• Allowed verified instrument: correlation-covariance-calculator