Social planning — forms

The distinct forms record for Social planning. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: job:rebecca:social-planning
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 — 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.

Social brief

Define the communication request and intended outcome without assuming publication authority.

request title
requester
business page or communication context
objective
audience
channel
campaign or standalone post
desired call to action
requested publish date and time
priority
owner
approver

Source and proof

Bind copy and media to reviewed source material and prevent invented customer proof.

source record IDs
source URLs or locators
source SHA-256 when available
claim inventory
proof status for each claim
customer permission status
media references
brand-voice reference
channel-rules reference
unsupported-claim notes

Draft ledger

Capture versioned content for review.

post text
headline or hook
channel-specific variant
media asset reference
alt text
link target
hashtags or tags
call to action
character or format check
revision number
draft status
drafted by
draft timestamp

Principal gates

Record explicit human review for public or externally consequential work.

public-post review status
account-connection status
paid-promotion status
direct-message commitment status
approver
approval decision
decision timestamp
held reason
required changes
receipt reference

Schedule and workback

Create bounded preparation deadlines while keeping external scheduling and publication human-held.

publish target
timezone
brief due date
source review due date
draft due date
review due date
approval due date
asset readiness due date
final handoff due date
conflict notes
calendar record reference

Handoff and receipt

Prepare a complete package for human execution and preserve the resulting evidence.

final approved copy reference
approved media reference
account identity confirmation
handoff recipient
send or publish instruction
publication state
publication receipt reference
external URL if human supplied
failure state
follow-up owner

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.

Post brief

Define the communication before drafting.

working title
business objective
audience
channel
approved account target
campaign or project reference
desired publish window
priority
call to action
required accessibility notes

Sources and claims

Keep public claims traceable and prevent invented proof.

source record IDs
source locators
claim text
claim support or evidence note
customer-proof status
media or attachment references
unsupported-claim warning acknowledgement

Draft package

Prepare a reviewable post and its delivery context.

post copy
alt text or equivalent media description
link destination if applicable
hashtags or labels
variant notes
character or format checks
revision note

Review and approval

Record human review and resolve gates before handoff.

reviewer
review checklist
brand-voice result
channel-rules result
account-authorization result
paid-promotion flag
direct-message commitment flag
decision: Needs review, Approved, or Held
decision rationale

Publication handoff

Make the final state explicit without claiming external effect.

handoff recipient
approved account confirmation
scheduled window
final approved revision ID
publication status: held or handed off
receipt reference when available
post-publication follow-up owner

Required or proposed record references

No record existence is asserted by this documentation page.

job:rebecca:social-planning
social-curator record
content-calendar record
draft-ledger record
approval-queue record
campaign-packet record when a campaign is involved
brand-voice guide reference
channel-rules guide reference
publication-receipt record for any human-confirmed publication
account-connection review record
paid-promotion review record when promotion is proposed
direct-message commitment review record when a commitment is proposed
source-labelled asset references for media and claims
deadline and revision records
Draft record with canonical ID, owner, source references, channel, account target, copy, media references, status, and revision history
Content-calendar item with planned publish window, priority, dependencies, and deadline state
Approval record with reviewer, decision, timestamp, rationale, and receipt link
Campaign packet or source-backed brief when a post belongs to a campaign
Publication receipt or explicit held state; no external publication is implied by this proposal

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/