Source: https://guthlabs.ai/docs/field-guides/publication-receipts/steps/ field guide / candidate # Publication receipts โ€” steps The distinct steps record for Publication receipts. This page is proposal-only. Status: **proposed**Lifecycle: **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. ## Ordered procedure - Open the proposed guide from Notebook Field Guides and confirm the owner is Rebecca and the related jobs are Social planning, Draft preparation, Asset coordination, Approval routing, and Post-performance records. - Create or link a project grouping in Notebook Projects for the receipt package; preserve canonical IDs, origin, source locators, provenance, revisions, lifecycle, tags, and links for each record. - Create the receipt scope record in Notebook Notes with a unique title, source record ID, intended audience, proposed surface, and proposed timing. Mark the publication state as proposed or held; do not label it published. - Collect source-labelled references in Notebook Files. Add local file references, type, size, and links to the receipt; do not imply upload, protected storage, or external asset availability. - Prepare the draft in Notebook Paper or Notes. Record the exact draft text, intended call to action, source context, accessibility text, and revision identifier. - Create explicit workback to-dos for draft, asset, approval, decision, and post-performance review. Assign dueAt, priority, tags, and completion state; use Agenda only for local inspection or draft scheduling. - Coordinate assets through Notebook Capture or Files. Review each proposed asset, its local custody state, dimensions or type if known, alt text, and any missing or held attachment. Do not claim Vault copy or publication. - Route the package through Notebook Approvals. Set the decision to Needs review, Approved, or Held, preserve reviewer notes and a receipt, and keep final send human-held. - If approved locally, record approval as a proposal receipt only. Do not send messages, write to an external provider, publish, index customers, or treat an app route as evidence of a connected web feature. - If a human later supplies a publication confirmation, create a separate post-performance observation record containing the supplied source, timestamp, locator, and limitations. Otherwise retain the receipt as prepared, approved locally, or held. - Record post-performance observations only from an identified source. Separate reported measures from interpretation and preserve the observation revision and provenance. - Review Agent Logs for the work performed, authority boundaries, decisions, unresolved gaps, and receipts. Mark the guide complete only when all acceptance tests pass or an explicit held state is recorded. ## Deadline and chronology rules - Every workback item must have an explicit dueAt or be marked unscheduled with a reason. - Set the approval deadline before the proposed publication decision deadline. - Set the post-performance review date only after a publication confirmation source exists; otherwise keep it held. - Overdue items remain open and receive a review tag; do not silently reschedule or mark complete. - A recurrence candidate is only a planning field and must not create hidden automation. - If timing, timezone, source, or reviewer is missing, hold the affected decision rather than guessing. ## Failure branches during execution - A named agent or route may be mistaken for an external provider, connected web feature, or execution authority. - An Approved local decision may be misread as publication authorization; final send remains human-held. - Unlabelled screenshots, files, or metrics can become unsupported publication or performance claims. - Missing timezone, source locator, revision, or reviewer can make a receipt non-reproducible. - Local file references may be mistaken for uploaded or protected assets. - Post-performance numbers may be copied without a source, observation time, denominator, or limitation. - Overdue work may be mistaken for failure or silently advanced; preserve explicit held and overdue states. - Medical, financial, legal, or other regulated claims in copy require appropriate human review; this guide does not qualify them. ## 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.`