Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

job / candidate

Draft preparation — field guides

The distinct field guides record for Draft preparation. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID
job:rebecca:draft-preparation
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

  1. Create a source-labelled draft-preparation job and assign Rebecca as the proposed owner.
  2. Collect the brief, campaign packet, brand voice guidance, channel rules, and supporting file references.
  3. Record source locators, provenance, revisions, and hashes where available; flag missing or stale sources.
  4. Confirm the target channel and account label without treating an account connection as established.
  5. Create a draft record and corresponding draft ledger entry; preserve version history.
  6. Check the draft against brand voice, channel rules, accessibility needs, and evidence for every public claim.
  7. Place the draft in the local approval queue with explicit open questions and a proposed publication window.
  8. Route any customer proof, account choice, paid promotion, or direct-message commitment to human review.
  9. Apply only a local approval state: Needs review, Approved, or Held; preserve the reviewer and receipt.
  10. If approved, prepare a human-held publication handoff; do not self-authorize publication or external sending.
  11. Record publication confirmation only when supplied by an authorized human or verified receipt; otherwise retain Held status.
  12. Log the completed work, authority boundary, revisions, failures, and unresolved follow-up in Agent Logs.

Handoff boundary

  • Self-authorized publication or external sending
  • Use of an unapproved or incorrectly identified account
  • Invented customer proof, testimonials, metrics, or outcomes
  • Public claims that cannot be traced to supplied source material
  • Paid promotion initiated without explicit human authorization
  • Direct-message commitments made without human review
  • Approval applied to a changed draft, channel, account, or publication window
  • Provider, credential, database, customer, or publication effects being mistaken for connected capability
  • Duplicate or conflicting calendar entries
  • Missing alt text, inaccessible media, unclear links, or non-keyboard-operable review controls
  • Stale campaign material or source revisions being used without review
  • Sensitive customer or business information copied into an unapproved public draft

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:draft-preparation
  • Observed native contract: project and field-guide collections, deadlines, canonical records, PointGuard context surface, and held web boundary
  • App route: /app/notebook/field-guides/
  • App route: /app/notebook/approvals/
  • App route: /app/notebook/messages/
  • App route: /app/notebook/agent-logs/
  • App route: /app/notebook/agenda/
  • App route: /app/business/messages/
  • App route: /app/pointguard/
  • Observed native contract: project_and_field_guide_collections
  • Observed native contract: deadlines
  • Observed native contract: records
  • Observed native contract: pointguard
  • Observed native contract: web_boundary
  • App route: /app/notebook/projects/
  • App route: /app/notebook/to-dos/
  • App route: /app/business/home/