Source: https://guthlabs.ai/docs/jobs/rebecca-draft-preparation/forms/

job / candidate

# Draft preparation — forms

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

Status: **proposed**Lifecycle: **candidate**

## Record status

**Record ID**: job:rebecca:draft-preparation

**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](<https://guthlabs.ai/guth.html#builder>) — Inspect the package and stage a local project. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

## Proposed form sections

Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth.

### Brief and source context

Define the communication task and bind it to reviewable source material.

- job title

- business page or communication context

- communication objective

- intended audience

- campaign or project link

- source record IDs

- source locators

- source SHA-256 when available

- supporting file references

- known claims and evidence

- claims requiring human confirmation

### Channel and audience rules

Apply the approved operating constraints before drafting.

- target channel

- account identifier or account label

- channel rule reference

- audience description

- format constraints

- character or media limits if known

- tone requirements

- accessibility requirements

- prohibited content

- account approval status

### Draft content

Create a reviewable draft without publication authority.

- draft text

- headline or opening line

- call to action

- link or destination reference

- media references

- alt text or equivalent description

- content warnings if applicable

- hashtags or metadata

- version number

- authoring agent

- draft status

- open questions

### Review and approval

Capture human review, requested changes, and the final local decision.

- reviewer

- review date

- brand voice check

- channel rules check

- claim-evidence check

- customer-proof check

- account check

- accessibility check

- requested revisions

- decision: Needs review, Approved, or Held

- approval scope

- approval expiry or deadline

- approval receipt reference

### Publication handoff and receipt

Prepare a human-held handoff while keeping external publication effects out of this proposal.

- approved draft ID

- intended publication window

- handoff owner

- final recipient or account label

- publication instructions

- publication status

- external publication confirmation

- publication timestamp

- receipt reference

- exceptions or failure reason

### Accessible state contract

- Every field requires a visible and programmatic label.

- Required and optional fields must be stated in text.

- Invalid entries require an actionable message linked to the field.

- Blocked and Held states remain visible without relying on color alone.

## Supporting documentation fields

These fields come from the docs_urls lane and remain separate from the primary operating form.

### Draft brief

Capture the intended communication without implying that an account or publication channel is connected.

- communication objective

- business page or public communication context

- proposed channel

- audience

- campaign or content-calendar reference

- requested publication date and timezone

- call to action

- owner and reviewer

### Source and brand checks

Make the draft traceable to approved material and applicable guidance.

- source records and locators

- source SHA-256 when available

- brand voice guide reference

- channel rules reference

- campaign packet reference

- claims requiring evidence

- customer-proof status

- media or attachment references

### Draft content

Prepare the actual post for review as a revisioned, non-published record.

- draft text

- headline or opening line

- alt text or media description

- links and tracking parameters as plain draft values

- hashtags or labels

- character-count notes

- content warnings or accessibility notes

- revision summary

### Gates and approvals

Record every required human decision and prevent unauthorized effects.

- public-post gate status

- account-connection gate status

- paid-promotion gate status

- direct-message commitment gate status

- reviewer decision

- approval scope

- approval expiry or supersession condition

- hold reason

- receipt requirement

### Schedule and handoff

Turn an approved draft into a bounded handoff without performing publication.

- target handoff time

- review deadline

- publication owner

- handoff channel or record link

- final preflight checklist

- fallback if approval is late

- publication result receipt reference

## Required or proposed record references

No record existence is asserted by this documentation page.

- Source-labelled brief or campaign packet

- Brand voice guide

- Channel rules guide

- Draft record

- Draft ledger entry

- Content calendar item

- Approval record

- Publication receipt, only after human-held publication review

- Linked file references for supporting assets

- Agent log with authority and decision receipts

- Job record owned by Rebecca

- Draft record with canonical ID, source locator, provenance, revision, lifecycle, tags, links, and attachments

- Content calendar item with target channel and deadline

- Approval record with Needs review, Approved, or Held state

- Campaign packet when a campaign context is used

- Publication receipt only after a human-held publication action

- Account-connection record marked held unless separately verified

## 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/`
