Approval queue

Record status

Record ID

tool:approval-queue

Parent lifecycle

candidate

Page lane

contract

Lane lifecycle

proposed

Owner

Rebecca

Owner role

Social media operating agent

Owner status

Not separately recorded

Qualification result

NOT RUN · held for evidence and human review

Working browser surface: Tools — overview — Inspect the tool contract, usage, boundaries, and proposed qualification checks. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

Bounded contract

Proposal-only workflow for routing social-media work through explicit approval gates before any public posting, account connection, paid promotion, or direct-message commitment. It organizes drafts, assets, approvals, and publication records but does not publish, connect accounts, authorize spending, or create customer proof.

Owners

• Rebecca
• Social media operating agent

Inputs

• Social planning requests
• Draft posts
• Campaign packets
• Assets and asset status
• Target account and channel
• Approval decisions
• Publication receipts
• Performance records

Outputs

• Approval status by item
• Pending-gate list
• Required reviewer or owner
• Rejected or returned items with stated reason when recorded
• Publication-readiness handoff
• Post-publication record handoff

Required or proposed record references

The list defines expected records; it does not assert that any record instance exists.

• Draft content
• Associated campaign packet
• Asset coordination status
• Approval decision and approver
• Target account
• Channel rules check
• Publication receipt
• Post-performance record

Route contract

The links below are this site's admitted canonical public records. Source-lane route suggestions are proposals only and are not represented as live or canonical until separately admitted.

Held source-proposed extensions

• /docs/approval-queue/scope: Define the queue as a routing and recordkeeping workflow, including what each gate means and what the queue cannot authorize.
• /docs/approval-queue/records: Specify the minimum draft, approval, account, asset, receipt, and performance records for auditability.
• /docs/approval-queue/failure-states: Explain pending, rejected, incomplete, unapproved-account, and missing-receipt states and the required handoffs.
• /docs/approval-queue/operating-guide: Describe how social planning, draft preparation, asset coordination, approval routing, and performance records move through the queue.
• /docs/approval-queue/overview
• /docs/approval-queue/approval-gates
• /docs/approval-queue/records-and-receipts
• /docs/approval-queue/never-rules
• /docs/approval-queue/overview — scope, owner, lifecycle, and explicit statement that implementation and authority are unproven.
• /docs/approval-queue/workflows — deterministic routing for public posts, account connections, paid promotion, and direct-message commitments.
• /docs/approval-queue/records — required records, evidence fields, retention boundaries, and audit-log requirements.
• /docs/approval-queue/qualification — pass/fail qualification tests for routing, authorization, never-rules, and receipt handling.
• /docs/approval-queue/accessibility — keyboard, focus, labels, status announcements, contrast, reduced motion, and non-visual review requirements.
• /docs/approval-queue/privacy — minimum data collection, sensitive-content handling, access control, retention, export, and deletion questions.
• /docs/approval-queue/abuse — controls for unauthorized publication, account misuse, spam, impersonation, coercive approvals, and malicious payloads.
• /docs/approval-queue/source-and-authority — source traceability to agents/index.html#rebecca and separation of ownership from proven authority.
• /docs/approval-queue/failure-modes — blocked, ambiguous, stale, conflicting, missing, or unverifiable approval states.
• /docs/approval-queue/runbook — proposal-only operator checklist for intake, routing, evidence capture, escalation, and post-performance recording.

These extension paths are not generated by this record and must not be treated as resolving routes.

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

• source_record:tool:approval-queue
• agents/index.html#rebecca