Social planning — field guides

Record status

Record ID

job:rebecca:social-planning

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

No separate guide route is admitted for this project or job.

Source-proposed guide paths are references, not proof that those paths resolve.

Operating sequence

1. Create a social brief with channel, audience, objective, requested timing, owner, and approver.
2. Collect and link source-labelled notes, files, campaign packets, and applicable brand-voice and channel-rules references.
3. Separate factual claims, interpretation, and calls to action; mark unsupported or permission-dependent claims as held.
4. Draft channel-specific variants in the draft ledger, including accessible alt text and reviewed media references.
5. Run the principal gates for every public post, account connection, paid promotion, and direct-message commitment.
6. Submit the draft and gate receipts for human review through Approvals; preserve revisions and held reasons.
7. Build a workback schedule from the requested publish target and surface conflicts or missing prerequisites in Today and Agenda.
8. Hand off only the approved package to the human operator; do not publish, connect accounts, pay for promotion, or commit on behalf of the business.
9. If publication is human-confirmed, record the publication receipt and any supplied external locator; otherwise leave publication held.
10. Review failures, rejected drafts, expired approvals, missing proof, and unresolved commitments in Agent Logs and the relevant Notebook surfaces.

Handoff boundary

• Self-authorized publication or scheduling
• Unapproved or ambiguous account use
• Invented testimonials, customer outcomes, or proof
• Paid promotion proceeding without explicit review
• Direct messages creating commitments without human authorization
• Copy or media changing after approval without re-review
• Provider, credential, customer, database, publication, or production effects being inferred from local prototype routes
• Timezone, recurrence, or deadline ambiguity
• Inaccessible forms or status indicators
• Public claims exceeding the supplied source record

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:social-planning
• observed_native_contract.project_and_field_guide_collections
• observed_native_contract.deadlines
• observed_native_contract.records
• observed_native_contract.pointguard
• app_routes:/app/pointguard/
• app_routes:/app/notebook/approvals/
• app_routes:/app/notebook/messages/
• app_routes:/app/notebook/field-guides/
• app_routes:/app/notebook/agent-logs/
• job:rebecca:social-planning
• Observed native contract: records preserve canonical IDs, provenance, revisions, lifecycle, tags, links, attachments, and record revisions
• Observed native contract: NotebookTodoPayload supports due dates, priority, recurrence candidates, completion state, tags, revisions, and deadline views
• Observed native contract: PointGuard is a persistent cross-app context surface while specialist apps remain execution and canonical-record owners
• Observed native contract: provider, credential, database, customer, publication, and production effects are held
• /app/notebook/projects/
• /app/notebook/to-dos/
• /app/notebook/agenda/
• /app/notebook/approvals/
• /app/notebook/agent-logs/
• /app/business/messages/