Source: https://guthlabs.ai/docs/jobs/rebecca-post-performance-records/field-guides/ job / candidate # Post-performance records โ€” field guides The distinct field guides record for Post-performance records. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: job:rebecca:post-performance-records **Parent lifecycle**: candidate **Page lane**: docs_urls **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. ## Related field-guide records - /app/notebook/field-guides/ Source-proposed guide paths are references, not proof that those paths resolve. ## Operating sequence - Create a source-labelled post-performance record and preserve the supplied source locator, provenance, and revision metadata. - Identify the related draft, campaign packet, content-calendar item, or project; do not treat an index or route as proof that an external system is connected. - Enter only metrics and observations supplied by a human or attached source, including the observation window and measurement limitations. - Compare the observation with the declared baseline and record a bounded interpretation plus alternative explanations; leave unsupported fields explicitly unknown. - Check the principal gates: every public post, account connections, paid promotion, and direct-message commitments. - Create or update a draft-ledger entry and link it to the relevant post, campaign, approval, and agent-log records. - Create a local approval item with Needs review status whenever a public claim, reply, publication request, account action, paid promotion, or commitment is involved. - Route unresolved questions, unsupported customer proof, missing account authorization, or ambiguous metrics to human review and mark the record Held. - Create due items using the declared owner, priority, and relative deadline; preserve revisions and avoid hidden automation. - After human review, preserve the decision receipt. Do not send, publish, connect, promote, or promise externally from this package. - Close the job only when the record is internally complete, held effects are clearly labelled, follow-ups are assigned, and the agent log contains the final bounded state. ## Handoff 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.` - `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`