Post-performance records — tools

The distinct tools record for Post-performance records. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: job:rebecca:post-performance-records
Parent lifecycle: candidate
Page lane: package
Lane lifecycle: proposed
Owner: Rebecca
Owner role: Social media operating agent
Owner status: PROPOSED
Qualification result: NOT RUN · held for evidence and human review

Working browser surface: Agent jobs — builder overview — Inspect the package and stage a local project. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

Authoritative package lane tools and interfaces

Canonical tools-page assignments

Draft ledger (record · required) — Canonical internal record of post or message draft revisions, channel labels, and review status.
Content calendar (record · required) — Provides the declared campaign or scheduling context without authorizing external scheduling.
Approval queue (record · required) — Holds public-post, claim, account, promotion, and commitment decisions for human review.
Social curator (skill · required) — Supports internal organization and interpretation of supplied social material without self-authorizing publication.
Brand voice (guide · required) — Bounds proposed wording and flags tone or claim issues before review.
Channel rules (guide · required) — Provides channel-specific review constraints for proposed communications.
Campaign packets (guide · required) — Supplies campaign scope, approved messages, and evidence expectations when provided.
Publication receipts (guide · required) — Defines what evidence a human must preserve if publication is later confirmed.

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

No verified instrument is assigned to this tools lane.

An instrument listed only for another lane does not become a tools-page assignment.

Use boundary

Treating local prototype or indexed routes as connected social-provider features.
Self-authorizing publication or sending a final external message.
Using an unapproved account or accepting account identity without human-supplied authorization evidence.
Inventing customer proof, engagement numbers, attribution, testimonials, or performance causation.
Turning an observed metric into a guaranteed outcome or individualized business advice.
Launching paid promotion or recording a budget commitment without separate human approval.
Making direct-message commitments, promises, or customer-service decisions without human review.
Losing source provenance, revisions, attachments, approval receipts, or the distinction between draft and published state.
Creating hidden recurring automation from a recurrence candidate.
Exposing private notes, account details, or held work through public documentation or search.

Sources and evidence

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

agents/index.html#rebecca
source_record:job:rebecca:post-performance-records
Observed native contract: PointGuard persistent context surface; specialist apps remain execution and canonical-record owners.
Observed native contract: Notebook records preserve canonical IDs, provenance, source locators, revisions, lifecycle, tags, links, and attachments.
Observed native contract: NotebookTodoPayload supports due dates, priority, recurrence candidate, completion state, tags, revisions, and deadline views.
Observed native contract: provider, credential, database, customer, publication, and production effects are held.
App routes supplied for Notebook approvals, messages, projects, agent logs, field guides, files, notes, to-dos, and Business messages.