Asset coordination — field guides

The distinct field guides 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: 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

Create a source-labelled asset coordination record owned by Rebecca and set lifecycle to proposed.
Collect the communication brief, requested channel, audience, deadline, and source references.
Link existing Brand voice, Channel rules, and any Campaign packets before drafting.
Register local asset references in Files or Vault surfaces; do not assume upload, protected storage, or account access.
Create or update the Content calendar and Draft ledger with explicit revision, owner, priority, and due date fields.
Draft channel-specific copy and accessibility text while marking unsupported claims for evidence review.
Run the Brand voice and Channel rules checks and record unresolved issues.
Place the draft in the Approval queue with a human reviewer and a review deadline.
Hold the work when account identity, authorization, source evidence, or approval is missing.
After local approval, prepare a publication handoff; do not publish or send externally.
Record a Publication receipt only from a supplied, source-labelled receipt; otherwise retain publication as held.
Create follow-up to-dos for corrections, rescheduling, expiry, or receipt reconciliation.

Handoff boundary

Self-authorizing publication or treating an Approved local state as an external publication event.
Using an unapproved account or assuming that a named business page is connected.
Inventing customer proof, performance metrics, testimonials, or campaign results.
Sending direct messages or making commitments without human review and explicit authorization.
Treating local prototype routes as connected provider, credential, database, customer, publication, or production surfaces.
Using assets without a recorded source, rights or approval note, or revision lineage.
Publishing stale copy after a source, account, claim, or approval change.
Creating doorway documentation or duplicate keyword pages instead of distinct source-backed guidance.
Exposing private drafts, customer-related context, credentials, or held records through public search or docs.
Failing to provide accessible alt text, clear status labels, keyboard access, or non-color-only error states.

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/