Page actions
job / candidate
Asset coordination — tools
The distinct tools record for Asset coordination. This page is proposal-only.
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.
Authoritative package lane tools and interfaces
Canonical tools-page assignments
- Social curator (skill · required) — Organizes proposed social assets and communications while keeping publication authority outside the agent.
- Content calendar (record · required) — Tracks requested windows, deadlines, scheduling conflicts, and rescheduling decisions.
- Draft ledger (record · required) — Preserves copy revisions, channel variants, source context, and unresolved claims.
- Approval queue (record · required) — Provides a review state and receipt trail for every proposed public post.
- Notebook Files (interface · required) — Keeps source-labelled local file references beside coordination records without hidden upload.
- Notebook To-dos (interface · required) — Tracks review, evidence, correction, and receipt deadlines with human-review signals.
- Notebook Messages (interface · required) — Prepares internal or business communication while final external send remains human-held.
- Notebook Approvals (interface · required) — Supports explicit Needs review, Approved, and Held decisions with preserved receipts.
- PointGuard (interface · required) — Provides persistent cross-app context while specialist apps remain execution and canonical-record owners.
Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved.
Authoritative lane instrument assignments
Canonical tools-page assignments
No verified instrument is assigned to this tools lane.
An instrument listed only for another lane does not become a tools-page assignment.
Use 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#rebeccasource_record:job:rebecca:asset-coordinationjob:rebecca:asset-coordinationObserved 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.