Publication receipts — forms

The distinct forms 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.

Proposed form sections

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

Receipt scope

Define the proposed publication activity and the receipt being prepared.

receipt title
related job
owner agent
audience
channel or surface name
proposed publication date and time
timezone
receipt status
source record ID

Source and provenance

Keep every claim and attachment traceable to its source.

source locator
source SHA-256 if available
origin
provenance note
record revision
linked source records
visibility classification

Content package

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

draft text
call to action
asset description
asset reference or local path
alt text
caption or transcript
link target held for review
accessibility checks

Approval routing

Record human review and preserve the decision boundary.

reviewer
decision state
review notes
decision timestamp
required changes
approval receipt reference
final-send responsibility

Post-performance record

Capture only observed or supplied results after a human confirms the relevant state.

observation date and time
observation source
reported outcome
measure name
measure value
measurement limitations
follow-up action
result status

Workback and deadlines

Turn preparation into explicit bounded work without hidden automation.

draft due date
asset due date
approval due date
publication decision deadline
post-performance review date
priority
recurrence candidate
completion state
tags

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.

Receipt identity

Identify the proposed publication event and its accountable records.

receipt title
record owner
responsible agent
related project ID
channel or destination label
planned publication date and time
timezone
source locator
visibility state

Content and asset evidence

Bind the receipt to the exact draft and reviewed assets without hidden uploads or unsupported external claims.

draft record ID
draft revision ID
asset record IDs
asset filenames or local references
caption or message revision
link targets
content status
asset review status
source SHA-256 values when available

Approval and authority

Show whether the proposed action is ready, held, or approved locally while preserving human control over final send or publication.

approval record ID
approval status
approver
approval timestamp
approval scope
held reasons
required follow-up
final-send responsibility

Deadline and workback

Make preparation deadlines explicit and detect incomplete prerequisites before the planned time.

publication deadline
draft-lock deadline
asset-freeze deadline
approval deadline
reminder schedule
priority
recurrence candidate
conflict note
completion state

Post-performance receipt

Record observed evidence separately from planned or inferred outcomes.

observation timestamp
observation source locator
observed state
observed response or metric if supplied
evidence attachment reference
source SHA-256
revision note
operator or observer
unresolved discrepancy

Required or proposed record references

No record existence is asserted by this documentation page.

Source record for field-guide:publication-receipts:plan
Publication receipt record
Draft record
Asset reference record
Approval record
Post-performance observation record
Deadline to-do records
Agent log receipt
source-bound publication plan
draft message or post record
asset reference record
approval record
scheduled/deadline to-do
publication receipt record
post-performance note
agent log receipt

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