Packet identity
Define the packet and its bounded purpose.
- packet title
- packet record ID
- owner agent
- related job
- intended audience
- purpose statement
- visibility state
- lifecycle state
Page actions
field guide / candidate
Instrument packets — forms
The distinct forms record for Instrument packets. This page is proposal-only.
Status: proposedLifecycle: candidate
Record status
- Record ID
- field-guide:instrument-packets
- 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.
Source and provenance
Bind every claim and instrument selection to supplied evidence.
- source record ID
- source locator
- source SHA-256
- origin
- capture or review date
- provenance note
- revision number
- source excerpt or locator note
Instrument selection
Select only an exact verified instrument slug and document why it is relevant.
- exact instrument slug
- instrument name
- directory status
- area
- selection rationale
- status caveat
- alternative instrument considered
- instrument qualification state
Evidence reconciliation
Separate observed facts, proposed behavior, unresolved conflicts, and unsupported claims.
- evidence item ID
- claim text
- claim class
- supporting source locator
- supporting record
- confidence or review state
- conflict note
- required follow-up
Independent review
Capture a human review without treating a native surface as proof of connected behavior.
- reviewer
- review date
- review scope
- accessibility checks
- provenance checks
- slug exactness check
- failure findings
- decision
- review receipt
Workback and closure
Track bounded next actions and explicit due dates.
- next action
- owner
- dueAt
- priority
- recurrenceCandidate
- completion state
- tags
- revision note
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.
Packet identity
Define the packet and its ownership before evidence is assembled.
- packet title
- instrument name
- instrument slug
- packet owner
- owner agent
- intended review use
- packet lifecycle
- canonical record ID
Instrument boundary
Record exactly what the supplied directory establishes and what remains unverified.
- exact allowed slug
- catalog name
- catalog area
- catalog status
- permitted use statement
- prohibited-use statement
- qualification status: proposed or held
- known errata or limitations
- source locator
Evidence and provenance
Attach source-labelled evidence with traceable custody and revision data.
- evidence description
- source URL or locator
- source type
- source SHA-256 if available
- captured date
- linked file reference
- claim supported
- claim not supported
- record revision
Independent review
Provide a bounded review workflow with explicit decisions and unresolved questions.
- reviewer
- review date
- review questions
- reproduction inputs
- reproduction output
- discrepancies
- accessibility observations
- decision: needs review, approved locally, or held
- review notes
Claims and release boundary
Separate permitted descriptive claims from unsupported production or qualification claims.
- claim text
- claim class
- supporting evidence IDs
- public claim allowed
- public claim held
- required caveat
- final reviewer
- approval receipt ID
Workback and deadlines
Turn packet completion into dated, reviewable work rather than hidden automation.
- target review date
- evidence cutoff
- draft deadline
- independent review deadline
- reconciliation deadline
- approval deadline
- owner for each milestone
- priority
- recurrence candidate
- completion state
Required or proposed record references
No record existence is asserted by this documentation page.
- source record for the instrument packet
- instrument record with exact allowed slug
- source locator and source SHA-256
- provenance and revision record
- evidence receipt
- review decision record
- linked job or field-guide membership record
- deadline or follow-up to-do where review remains open
- source-labelled instrument record
- evidence note
- file reference or source locator
- review to-do
- approval receipt
- revision history
Sources and evidence
These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.
source_record:field-guide:instrument-packetsagents/index.html#tillyfield-guide:instrument-packetsOBSERVED_NATIVE_CONTRACTALLOWED_INSTRUMENTSObserved native contract: records preserve canonical IDs, source locators, source SHA-256, provenance, revision, lifecycle, tags, links, attachments, and record revisions.Observed native contract: PointGuard is a persistent cross-app context surface while specialist apps remain execution and canonical-record owners.Observed native contract: current GuthHub app routes are local prototypes or indexes and provider, credential, database, customer, publication, and production effects are held.Allowed instrument directory entries: checksum-verifier; sha-256-hash-function-demo; date-duration-calculator.