Content calendar

Record status

Record ID

tool:content-calendar

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 contract for organizing social planning, draft preparation, asset coordination, approval routing, and post-performance records. It may structure work and surface gates, but it does not publish, connect accounts, authorize paid promotion, make direct-message commitments, or create customer proof.

Owners

• Rebecca
• Social media operating agent

Inputs

• Social planning requests
• Draft post content
• Brand voice guidance
• Channel rules
• Campaign packets
• Asset coordination details
• Approval status and approver identity
• Publication receipts
• Post-performance observations
• Account and promotion gate status

Outputs

• Calendar entries
• Draft preparation records
• Asset coordination checklist
• Approval routing records
• Publication-readiness status
• Post-performance record placeholders
• Unresolved gate and dependency notices

Required or proposed record references

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

• Content item identifier
• Planned channel and timing
• Draft or draft status
• Associated assets and asset status
• Applicable brand voice and channel rules
• Campaign packet reference when applicable
• Approval request and decision record
• Publication receipt when a post is published by an authorized process
• Post-performance record
• Account connection status
• Paid promotion status
• Direct-message commitment status

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/content-calendar/contract: Defines the bounded purpose, inputs, outputs, records, workflow, and authority boundary.
• /docs/content-calendar/gates: Explains public-post, account-connection, paid-promotion, and direct-message commitment gates.
• /docs/content-calendar/records: Specifies calendar, approval, asset, publication-receipt, and post-performance records.
• /docs/content-calendar/failure-states: Describes hold conditions for missing approval, unapproved accounts, unsupported proof, missing assets, and unresolved commitments.
• /docs/content-calendar/overview — scope, source record, proposal status, and unproven capabilities.
• /docs/content-calendar/workflow — deterministic planning, drafting, asset, approval, gate, and receipt states.
• /docs/content-calendar/records — required fields and evidence-preserving record formats.
• /docs/content-calendar/gates — public-post, account-connection, paid-promotion, and direct-message controls.
• /docs/content-calendar/accessibility — keyboard, focus, labels, semantics, contrast, motion, and assistive-technology checks.
• /docs/content-calendar/privacy-abuse — data minimization, secret handling, spam, impersonation, and unsafe-commitment controls.
• /docs/content-calendar/source-authority — provenance, owner authority, claims boundaries, and escalation rules.
• /docs/content-calendar/qualification-tests — deterministic acceptance, regression, accessibility, privacy, abuse, source, and authority tests.

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:content-calendar
• agents/index.html#rebecca