Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

field guide / candidate

Qualification records — forms

The distinct forms record for Qualification records. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID
field-guide:qualification-records
Parent lifecycle
candidate
Page lane
plan
Lane lifecycle
proposed
Owner
Tilly
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.

Proposed form sections

Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth.

Scope and ownership

Define the qualification task without implying production authority or completed qualification.

  • task type
  • source record ID
  • related job
  • owner agent
  • reviewer
  • scope boundary
  • requested completion date
  • visibility state

Source and provenance

Capture the source material and its traceability before analysis.

  • source locator
  • source SHA-256
  • origin
  • source title
  • source revision
  • capture date
  • provenance note
  • linked file reference

Evidence assessment

Record observations, inputs, calculations, limitations, and unresolved conflicts.

  • evidence item ID
  • evidence description
  • evidence class
  • supporting locator
  • observed value or text
  • method
  • instrument slug if applicable
  • limitations
  • reconciliation status

Review and disposition

Separate draft findings from human-reviewed decisions.

  • reviewer
  • review date
  • decision state
  • accepted findings
  • held findings
  • required corrections
  • receipt link
  • next review deadline

Accessible state contract

  • Every field requires a visible and programmatic label.
  • Required and optional fields must be stated in text.
  • Invalid entries require an actionable message linked to the field.
  • Blocked and Held states remain visible without relying on color alone.

Supporting documentation fields

These fields come from the tools lane and remain separate from the primary operating form.

Review scope

Define what is being reviewed and who owns the record.

  • record title
  • review purpose
  • owner agent
  • related job
  • reviewer
  • review start date
  • target completion date
  • visibility

Evidence intake

Capture traceable source material without hidden upload or unsupported claims.

  • source locator
  • source type
  • source SHA-256 if available
  • source date
  • provenance note
  • local file reference
  • evidence summary
  • known gaps

Instrument use

Record only an allowed verified instrument and its bounded use.

  • instrument slug
  • input values
  • units
  • assumptions
  • instrument status
  • result summary
  • result limitations
  • reviewer check

Reconciliation and claims

Compare evidence, identify conflicts, and separate supported claims from held claims.

  • claim text
  • supporting evidence IDs
  • conflicting evidence IDs
  • reconciliation decision
  • confidence or uncertainty note
  • public-claim status
  • required follow-up

Review and receipt

Preserve human review, decision state, and authority boundaries.

  • decision: Needs review, Approved, or Held
  • decision owner
  • decision date
  • receipt or revision ID
  • reason for hold
  • next action

Required or proposed record references

No record existence is asserted by this documentation page.

  • Source-labelled qualification note
  • Qualification evidence record
  • Instrument reference record, if an instrument is used
  • Evidence reconciliation record
  • Review or approval record
  • Deadline todo with owner and dueAt
  • Revision and provenance receipt
  • source-labelled notes
  • file references
  • to-dos with due dates and review state
  • approval records
  • agent receipts and authority logs
  • instrument result records
  • claim-to-evidence links

Sources and evidence

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

  • source_record:field-guide:qualification-records
  • agents/index.html#tilly
  • field-guide:qualification-records
  • OBSERVED_NATIVE_CONTRACT.records
  • OBSERVED_NATIVE_CONTRACT.deadlines
  • OBSERVED_NATIVE_CONTRACT.pointguard
  • APP_ROUTES:/app/notebook/field-guides/
  • APP_ROUTES:/app/notebook/notes/
  • APP_ROUTES:/app/notebook/files/
  • APP_ROUTES:/app/notebook/to-dos/
  • APP_ROUTES:/app/notebook/approvals/
  • APP_ROUTES:/app/notebook/search/
  • APP_ROUTES:/app/notebook/agent-logs/
  • ALLOWED_INSTRUMENTS:checksum-verifier
  • ALLOWED_INSTRUMENTS:date-duration-calculator
  • Observed native contract: Notebook collections, deadlines, records, PointGuard, and held web boundary
  • App routes: /app/notebook/field-guides/
  • App routes: /app/notebook/approvals/
  • App routes: /app/notebook/agent-logs/
  • App routes: /app/notebook/files/
  • App routes: /app/notebook/messages/
  • App routes: /app/notebook/notes/
  • App routes: /app/notebook/search/
  • App routes: /app/notebook/to-dos/
  • App routes: /app/notebook/agenda/
  • App routes: /app/pointguard/