Publication receipts — examples

The distinct examples record for Publication receipts. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: field-guide:publication-receipts
Parent lifecycle: candidate
Page lane: plan
Lane lifecycle: proposed
Owner: Rebecca
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.

Hypothetical scenarios

A reviewer opens the Publication receipts guide for bounded local rehearsals. Every fixture uses invented placeholders, performs no provider or external action, and remains held until source evidence and human review are recorded.

1. Guided inquiry fixture

A reviewer records a bounded question, links only supplied source references, and marks every unanswered point Needs review.

Fixture ID: publication-receipts-example-001
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

2. Source comparison fixture

A reviewer compares two hypothetical source locators, preserves disagreement, and holds any conclusion until provenance is supplied.

Fixture ID: publication-receipts-example-002
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

3. Uncertainty and pathway fixture

A reviewer constructs a local procedure or study pathway with checkpoints while labelling uncertainty and leaving external effects Held.

Fixture ID: publication-receipts-example-003
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

4. Potentially allowed claim fixture

A hypothetical claim may advance only when its exact evidence locator, scope, reviewer, and decision rationale are recorded; this fixture asserts no fact.

Fixture ID: publication-receipts-example-004
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

5. Held claim fixture

A hypothetical unsupported claim remains Held with missing evidence and human-review rationale visible; it is not published or indexed.

Fixture ID: publication-receipts-example-005
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

Filled example fields

Receipt scope fixture

Define the proposed publication activity and the receipt being prepared.

receipt title: fixture-source-001 (hypothetical; no external claim)
related job: Example value to be supplied and reviewed
owner agent: Named human or Agent owner required
audience: Example value to be supplied and reviewed
channel or surface name: Example value to be supplied and reviewed
proposed publication date and time: Not supplied in this hypothetical fixture

Source and provenance fixture

Keep every claim and attachment traceable to its source.

source locator: fixture-source-001 (hypothetical; no external claim)
source SHA-256 if available: fixture-source-001 (hypothetical; no external claim)
origin: Example value to be supplied and reviewed
provenance note: Example value to be supplied and reviewed
record revision: Example value to be supplied and reviewed
linked source records: fixture-source-001 (hypothetical; no external claim)

Content package fixture

Describe what is being prepared without asserting that it was published.

draft text: Example value to be supplied and reviewed
call to action: Example value to be supplied and reviewed
asset description: Example value to be supplied and reviewed
asset reference or local path: Example value to be supplied and reviewed
alt text: Example value to be supplied and reviewed
caption or transcript: Example value to be supplied and reviewed

Review questions

A new receipt record has canonical ID, owner, related draft, asset references, approval state, deadline timezone, lifecycle, provenance, and source locator fields.
The workback view exposes draft-lock, asset-freeze, approval, and publication deadlines with deterministic ordering.
An incomplete asset, missing approval, stale revision, or missed prerequisite produces a visible Held or Needs review state rather than a success state.
The Messages surface displays final-send responsibility and does not display an external-send confirmation without supplied evidence.
The Files surface distinguishes a local file reference from upload or delivery.
The approval record preserves approver, scope, timestamp, decision, and held reason.
A receipt with no supplied observation source cannot be marked as observed or published.
Checksum verification stores the input context and result without claiming provider or publication verification.

Sources and evidence

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

source_record:field-guide:publication-receipts
agents/index.html#rebecca
field-guide:publication-receipts:plan
Observed native contract: records preserve canonical IDs, provenance, source locators, revisions, lifecycle, tags, links, attachments, and record revisions.
Observed native contract: PointGuard is a persistent cross-app context surface; 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.
field-guide:publication-receipts
observed_native_contract.project_and_field_guide_collections
observed_native_contract.deadlines
observed_native_contract.records
observed_native_contract.pointguard
/app/notebook/field-guides/
/app/notebook/approvals/
/app/notebook/messages/
/app/notebook/files/
/app/notebook/agenda/
/app/notebook/agent-logs/
/app/pointguard/
ALLOWED_INSTRUMENTS:checksum-verifier
ALLOWED_INSTRUMENTS:date-duration-calculator
ALLOWED_INSTRUMENTS:countdown-days-until-timer