Page actions
job / candidate
Uncertainty marking — qualification
The distinct qualification record for Uncertainty marking. This page is proposal-only.
Record status
- Record ID
- job:socrates:uncertainty-marking
- Parent lifecycle
- candidate
- Page lane
- qualification
- 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.
Qualification status
- Result
- NOT RUN
- Disposition
- HELD
- Reviewer
- Not recorded
- Receipt
- Not recorded
This page defines proposed acceptance criteria for the qualification lane. It does not execute tests, establish compliance, qualify the subject, or authorize an effect.
Lane-specific instrument aids
No verified instrument is assigned to this qualification lane.
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.
- A valid record contains a claim, scope, uncertainty label, source status, ownership, lifecycle, and revision identifier.
- The system rejects or holds a claim with no source reference when the claim is presented as source-backed.
- The system rejects invented primary-source metadata and preserves an explicit Unsupported or Unresolved state instead.
- Two conflicting supplied sources produce a Disputed or Unresolved label plus links to both sources and an explanation of the conflict.
- A claim marked Established-by-supplied-evidence cannot be used outside the recorded scope without a new review.
- Student identity data is optional, minimized, access-restricted, and excluded from public or broadly indexed contexts by default.
- High-stakes instruction, external enrollment, and published curriculum claims cannot reach Approved without a human reviewer receipt.
- Final messages remain drafts or Held; no provider, credential, enrollment, database, customer, or publication effect is asserted.
- Revision history preserves the prior claim, sources, labels, reviewer action, and reason for change.
- Keyboard navigation, visible focus, semantic labels, error text, and non-color-only status indicators are present for every form control.
- Screen-reader output names each uncertainty label, source status, review status, and failure reason.
- Search returns only records permitted by visibility and source partition rules; held private records are not exposed as public results.
- If a source cannot be opened or verified, the interface states that verification is unavailable and offers Hold, replace-source, or reviewer-escalation actions.
Negative and held-state tests
- Tutor output may be mistaken for institutional, academic, medical, legal, or enrollment authority.
- Generated recollection may be mistaken for evidence.
- A confidence score may imply unsupported mathematical precision.
- Disputed evidence may be collapsed into a single answer.
- Missing or inaccessible sources may be silently replaced by invented citations.
- Student identity or sensitive learning information may leak through notes, search, messages, or PointGuard context.
- A native route may be mistaken for a connected provider, publication system, or authoritative database.
- Deadline automation may create unintended external communication or enrollment effects.
- Accessibility failures may hide uncertainty labels, source conflicts, or Held states.
- Duplicate documentation pages could become doorway content or keyword-spam.
Qualification claim boundary
Potentially allowed only after the stated evidence
- The proposal describes a bounded teaching and inquiry profile.
- The package can require source labels, uncertainty markers, revision history, and human review.
- The supplied source identifies Socrates as a proposed University guide and tutor entity.
- Local prototype or indexed surfaces may be named as intended review locations.
Still held
- Socrates is deployed, connected, or authoritative.
- Any provider, database, credential, enrollment, customer index, or publication workflow is connected.
- Claims have been qualified, verified, or approved in production.
- A curriculum, course route, primary-source packet, or citation tool is available as a live service.
- Student data is stored in protected production infrastructure.
- Any app route performs external sends, writes, publication, or enrollment.
- Qualification has completed for any individual claim.
Sources and evidence
These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.
agents/index.html#socratessource_record:job:socrates:uncertainty-markingobserved_native_contract.recordsobserved_native_contract.pointguardobserved_native_contract.web_boundaryapp_route:/app/notebook/notes/app_route:/app/notebook/approvals/app_route:/app/notebook/agent-logs/app_route:/app/notebook/search/app_route:/app/notebook/messages/