Approval routing — tools

The distinct tools record for Approval routing. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: job:rebecca:approval-routing
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) — Proposed source-record tool for organizing social communication candidates and drafts.
Content calendar (record · required) — Proposed source-record tool for requested publish windows, sequencing, and workback context.
Draft ledger (record · required) — Proposed source-record tool for draft revisions, ownership, and source traceability.
Approval queue (interface · required) — Proposed source-record tool for routing review decisions and preserving gate states.
Notebook approvals (interface · required) — Observed local surface for Needs review, Approved, and Held proposal decisions.
Notebook agent logs (interface · required) — Observed local surface for authority, current work, and receipts.
PointGuard (interface · required) — Observed persistent cross-app context surface for focused current work; it does not own specialist records.

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-authorized publication
Invented customer proof or unsupported public claims
Use of an unapproved account
Treating a local prototype route as a connected social provider
Confusing draft approval with account connection approval
Paid promotion proceeding without separate review
Direct-message commitments being treated as ordinary posts
Silent deadline or timezone errors
Publication receipts being inferred without evidence
Private or customer information being exposed in public drafts
Duplicate or stale revisions being approved
Accessibility failures in gate status, forms, or approval actions

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:approval-routing
Observed native contract: Notebook collection lifecycle and membership ordering
Observed native contract: Notebook deadlines and to-dos
Observed native contract: canonical record provenance and revisions
Observed native contract: PointGuard context boundary
Observed app routes: /app/notebook/approvals/
Observed app routes: /app/notebook/agent-logs/
Observed app routes: /app/notebook/field-guides/
Observed app routes: /app/notebook/messages/
Observed app routes: /app/notebook/projects/
Observed app routes: /app/notebook/to-dos/
Observed app routes: /app/notebook/agenda/
Observed app routes: /app/pointguard/