Asset coordination — forms

The distinct forms record for Asset coordination. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: job:rebecca:asset-coordination
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.

Asset and communication brief

Define the proposed public communication and its intended use before drafting.

brief title
business page or channel name
campaign or initiative
communication objective
target audience
requested format
requested publish window
source references
owner
priority

Asset inventory

Record the source-labelled assets available for review without implying upload, custody, or publication.

asset name
asset type
local reference or source locator
source SHA-256 if available
revision
dimensions or duration
rights or approval note
related campaign packet
asset status

Draft and channel adaptation

Prepare channel-specific copy and identify claims, calls to action, and required evidence.

draft copy
channel variant
caption or body text
headline or title
call to action
alt text
link target
claims requiring evidence
content warnings or accessibility notes
draft revision

Review and approval

Route the draft through human review and preserve the decision state.

reviewer
review due date
review comments
brand voice check
channel rules check
claim evidence check
account authorization check
decision: Needs review, Approved, or Held
approval timestamp
approval receipt reference

Publication handoff and receipt

Prepare a human-held publication handoff and capture a receipt only when supplied by an authorized human or verified source.

approved account identifier
planned publication time
final approved revision
handoff instructions
publication state
publication receipt locator
actual publication time if supplied
post URL if supplied
exception or failure note

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.

Asset brief

Capture the intended business communication and its source context before drafting.

brief title
business page or channel name
campaign or project ID
communication objective
audience
proposed channel
desired publish window
source records and locators
asset type
asset attachments or local file references
claims requiring evidence
owner and reviewer

Draft ledger entry

Create a reviewable draft without implying publication or external delivery.

draft ID
caption or message text
media reference
alt text or equivalent description
link target
call to action
channel-specific formatting
claim-by-claim evidence links
version number
draft status
authoring timestamp
open questions

Principal gates

Record whether human review is required for public posting, account use, paid promotion, or direct-message commitments.

public-post gate status
account-connection gate status
paid-promotion gate status
direct-message-commitment gate status
approver
decision deadline
decision notes
held reason

Publication receipt

Preserve a source-bound record of an authorized publication outcome without claiming publication until a verified receipt exists.

receipt status
approved draft ID
approved account or channel reference
authorization record
publication timestamp if verified
public locator if verified
result or error
source locator
revision and provenance metadata

Required or proposed record references

No record existence is asserted by this documentation page.

job:rebecca:asset-coordination
brand-voice-guide
channel-rules-guide
campaign-packet-record
content-calendar-record
draft-ledger-record
approval-queue-record
publication-receipt-record
account-connection-record
asset-file-reference
message-draft-record
deadline-todo-record
Job record owned by Rebecca
Asset or post draft record
Content calendar item
Draft ledger entry
Approval queue item
Campaign packet when applicable
Publication receipt when publication is authorized and completed
Account-connection review record when an account is referenced
Paid-promotion review record when promotion is proposed
Direct-message commitment review record when a commitment is proposed

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:asset-coordination
job:rebecca:asset-coordination
Observed native contract: PointGuard is a persistent cross-app context surface and specialist apps remain execution and canonical-record owners.
Observed native contract: current GuthHub app routes are local prototypes or indexes and provider, credential, database, customer, publication, and production effects are held.
source record: job:rebecca:asset-coordination
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/business/home/
/app/business/messages/
/app/notebook/agenda/
/app/notebook/approvals/
/app/notebook/agent-logs/
/app/notebook/projects/
/app/pointguard/