Post-performance records

Record status

Record ID

job:rebecca:post-performance-records

Parent lifecycle

candidate

Page lane

catalog overview

Lane lifecycle

candidate

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.

Purpose and audience

A proposal-only reusable job package for Rebecca to capture, review, approve, and preserve records after a social performance event without publishing, connecting accounts, making customer-proof claims, or creating paid promotion effects.

• Rebecca, social media operating agent
• Human social reviewer
• Business owner or communications approver
• Notebook records and approvals maintainers

Required or proposed record references

The list defines expected record classes. It does not assert that any instance exists.

• Source-labelled post or campaign record with canonical ID, origin, source locator, source SHA-256 when available, provenance, revision, lifecycle, tags, links, and attachments
• Performance observation record containing the observation window, source context, measured values, and limitations
• Draft ledger entry linked to the post, channel, revision, and reviewer
• Approval record with Needs review, Approved, or Held state and preserved receipt
• Publication-receipt record, held unless a human supplies evidence of an external publication
• Account-connection record, held unless separately authorized and evidenced
• Customer-proof evidence record, required before any customer-result claim; otherwise mark claim unsupported
• Direct-message commitment record for any proposed response or promise
• Agent-log entry recording Rebecca's work, authority boundary, inputs, outputs, and unresolved failures

Route contract

The links below are this site's admitted canonical public records. Source-lane route suggestions are proposals only and are not represented as live or canonical until separately admitted.

Held source-proposed extensions

• /docs/jobs/rebecca-post-performance-records/inputs/
• /docs/jobs/rebecca-post-performance-records/review-gates/
• /docs/jobs/rebecca-post-performance-records/record-schema/
• /docs/jobs/rebecca-post-performance-records/failure-states/
• /docs/jobs/rebecca-post-performance-records/accessibility/

These extension paths are not generated by this record and must not be treated as resolving routes.

Public claim boundary

Allowed items below are source-lane proposals, not verified current-state claims.

Candidate claims allowed after source review

• This is a proposal-only reusable job package for recording and reviewing supplied post-performance information.
• The package can organize drafts, observations, approvals, follow-ups, and receipts in local Notebook-oriented surfaces.
• The package preserves explicit authority boundaries and holds external publication, provider, credential, database, customer, and production effects.
• The listed instruments are empty because this social operating job has no applicable verified calculation instrument in the supplied directory.

Claims held

• That any social account is connected, approved, or available for use.
• That a post was published, delivered, promoted, or indexed for customers.
• That any metric is live, complete, accurate, causal, or representative without source evidence.
• That customer proof, testimonials, conversions, reach, or revenue exist without an attached verified record.
• That an approval caused an external publication or message send.
• That any route represents a deployed production feature or external provider integration.

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.
• source_record.record_type=job
• source_record.record_id=job:rebecca:post-performance-records
• source_record.owner_agent=Rebecca
• source_record.existing_tools=Social curator; Content calendar; Draft ledger; Approval queue
• source_record.existing_guides=Brand voice; Channel rules; Campaign packets; Publication receipts
• source_record.principal_gates=Every public post; Account connections; Paid promotion; Direct-message commitments
• source_record.never_rules=Self-authorize publication; Invent customer proof; Use an unapproved account
• OBSERVED_NATIVE_CONTRACT.deadlines
• OBSERVED_NATIVE_CONTRACT.records
• OBSERVED_NATIVE_CONTRACT.pointguard
• OBSERVED_NATIVE_CONTRACT.web_boundary
• Observed native contract: NotebookCollectionKind project and fieldGuide collections
• Observed native contract: NotebookTodoPayload deadlines and scheduled/deadline views
• Observed native contract: Notebook record provenance, source locators, hashes, revisions, lifecycle, links, and attachments
• Observed native contract: PointGuard context surface and specialist-app ownership
• Observed app routes: /app/notebook/agent-logs/
• Observed app routes: /app/notebook/approvals/
• Observed app routes: /app/notebook/messages/
• Observed app routes: /app/notebook/notes/
• Observed app routes: /app/notebook/files/
• Observed app routes: /app/notebook/projects/
• Observed app boundary: provider, credential, database, customer, publication, and production effects are held