Page actions
field guide / candidate
Publication receipts — tools
The distinct tools 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
- tools
- 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.
Authoritative tools lane tools and interfaces
Canonical tools-page assignments
- Notebook (interface · required) — Owns the proposal records, lifecycle, provenance, revisions, links, attachments, deadlines, approvals, and receipts; use it as the canonical local record surface.
- PointGuard (interface · required) — Provides the persistent cross-app context room for keeping the current publication work, related records, and held states together; it is not the execution owner.
- Messages (interface · required) — Prepares and reviews draft communication with recipients, source context, and final-send responsibility; never use it to claim an external send.
- Files (interface · required) — Stores source-labelled local file references and asset metadata beside records; never use it to imply upload or protected external delivery.
- Approvals (interface · required) — Captures local approval state, held reasons, approver, scope, and receipts before any human-held final effect.
- Agenda (interface · required) — Stages source-bound time blocks, deadline review, and conflict checks; external calendar writes remain held.
- Agent Logs (interface · required) — Records Rebecca's work, authority boundaries, failures, receipts, and unresolved discrepancies for auditability.
- Search (interface · required) — Finds local indexed records by type and source labels so the draft, asset, approval, schedule, and receipt chain can be checked together.
- Checksum Verifier (skill · optional) — Verifies supplied checksums for draft or asset references when a source hash is available; must not establish file identity beyond the supplied input or prove publication.
Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved.
Authoritative lane instrument assignments
Canonical tools-page assignments
checksum-verifierrequired · Check a supplied digest against a supplied local file or text representation before recording the resulting checksum in a receipt; do not use it to verify provider delivery, publication, customer access, or a file that was not supplied.date-duration-calculatorrequired · Calculate workback intervals between draft lock, asset freeze, approval, and planned publication deadlines; do not use it as evidence that any deadline was met.countdown-days-until-timeroptional · Show remaining time to a manually supplied deadline during preparation; do not treat the countdown as a scheduler, reminder delivery, or publication confirmation.
An instrument listed only for another lane does not become a tools-page assignment.
Use boundary
- Confusing a scheduled plan with a completed publication.
- Treating a local prototype route as a connected provider or web feature.
- Overwriting a draft or asset revision after approval without invalidating approval.
- Using an asset reference as evidence of upload, delivery, or customer access.
- Recording inferred reach, engagement, indexing, or qualification as observed performance.
- Losing timezone context and misordering workback deadlines.
- Treating checksum equality as proof of authorship, safety, publication, or provider custody.
- Allowing an Agent to send, publish, approve for a human, or alter external systems.
- Creating doorway documentation pages that repeat keywords without distinct operational content.
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-receiptsfield-guide:publication-receiptsagents/index.html#rebeccaobserved_native_contract.project_and_field_guide_collectionsobserved_native_contract.deadlinesobserved_native_contract.recordsobserved_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-verifierALLOWED_INSTRUMENTS:date-duration-calculatorALLOWED_INSTRUMENTS:countdown-days-until-timer