> Discover all available Postdom documentation from the machine-readable index: https://postdom.com/llms.txt

Core concept · schedule authority

# Schedules and plans

Each connected account has an autonomy level. Postdom applies the strictest level across every destination before accepting a schedule.

Account autonomy

## Authorization modes

New connected accounts start with bounded autonomy. A human can choose a stricter mode for any account without granting the agent permission to change its own authority.

### L0 · Manual

The agent creates an unscheduled post. A human chooses whether and when it publishes.

### L1 · Post review

Each agent post waits for exact human approval before provider handoff.

### L2 · Plan review

Posts flow only inside one approved plan covering the accounts, UTC window, and post maximum.

### L3 · Bounded autonomy

Posts flow only inside the account's saved daily cap, visibility allowlist, and quiet hours.

### Default bounds

New accounts start at L3 with a two-post daily cap, posting at about 09:00 and 19:00, and quiet hours from 22:00 to 07:00 in the workspace timezone. Humans can edit the policy or select a stricter mode.

For multi-account posts, the strictest destination governs the whole request. Postdom never splits one request into partially authorized publishes.

**For AI agents:** Stop on approval, policy, trust, pause, or exception states and return the exact resource ID.

**Known failure:** Never approve yourself, expand trust, or exercise a human-only route.

Human and agent roles

## Plan boundary

An agent proposes a bounded plan. A human approves it or returns structured feedback.

 AI agent

### Proposes authority

Supplies the configured accounts, UTC window, objective, post maximum, and intent.

 Human supervisor

### Grants authority

Approves the plan, requests changes, rejects it, or leaves it to expire.

 Postdom

### Records authority

Preserves plan state, structured feedback, authorized destinations, and post usage.

**For AI agents:** Stop on approval, policy, trust, pause, or exception states and return the exact resource ID.

**Known failure:** Never approve yourself, expand trust, or exercise a human-only route.

Concept contract

## Configured contract

The configured plan tool accepts seven required planning fields. Workspace Brief version, agent identity, and idempotency are optional callable fields.

**`account_ids`** — Destination accounts inside the requested boundary.

**`starts_at · ends_at`** — RFC 3339 UTC datetimes ending in `Z`.

**`title · objective · intent`** — Human-readable purpose and calling-agent intent.

**`max_posts`** — The maximum number of posts authorized by the plan.

**`brief_version`** — Optional Workspace Brief version used to prepare the plan. It must exist in the same workspace.

**For AI agents:** Use an RFC 3339 UTC value ending in Z only when the human or approved plan supplied the intended instant.

**Known failure:** Never guess a timezone or claim an exact schedule when publish_at was omitted.

 Exact plan states

`requires_approval``approved``changes_requested``rejected``expired``cancelled`

Read and return these values exactly. Do not collapse them into approved or denied.

Labeled example

## Example plan

The account IDs and values below are examples. They do not represent a connected workspace.

_EXAMPLE CALL · CONFIGURED TOOL SCHEMA_

```
submit_plan({
  account_ids: ["acct_example_ig", "acct_example_yt"],
  title: "Launch week",
  objective: "Coordinate the approved launch schedule",
  starts_at: "2026-09-01T00:00:00Z",
  ends_at: "2026-09-07T23:59:59Z",
  max_posts: 12,
  intent: "Schedule approved short-form video"
})
```

Stop conditions

## State handoff

`requires_approval`

### Wait for a human

Stop scheduling against the plan until its state changes.

`changes_requested`

### Revise the plan

Use the returned feedback category and text, then submit a deliberate revision.

`rejected · expired · cancelled`

### Return the boundary

Stop plan-backed work. A human must define or authorize a new plan before that work continues.

`approved`

### Stay inside it

Use only its accounts, time window, and remaining post capacity. Destination validation and pause controls still apply.

 VERIFIED · 26 AUGUST 2026  **Configured tool schema · Plan state model**

Example identifiers are synthetic. Use account IDs returned by the connected workspace.