Words agents can act on.

A saved social account record inside one Postdom workspace. Agent calls use its account ID when selecting a publishing destination or measurement scope.

The human-selected L0–L3 authority mode on a connected account. It determines whether publishing is manual, reviewed per post, approved by plan, or allowed inside saved bounds.

The evidence status attached to a modeled metric field: available, delayed(2-3d), estimable, never, or unverified. It must remain attached to the returned value or null.

An availability state saying the modeled evidence baseline exposes the field. The returned value can still be null and must be preserved exactly.

A ranking of one connected account's posts by one supported metric inside a 7-day or 30-day publication window. Null observations are excluded, never ranked as zero.

A social account whose provider authorization has been completed by a human and whose Postdom record can be selected by account ID.

The maximum number of posts an L3 account policy authorizes in that account's local day. A human can edit the cap or choose a stricter authority mode.

An availability state saying a field is expected after a two-to-three-day evidence delay. It is not a guarantee that a value will arrive.

One provider-and-account target selected for a post. A single post can have several destinations, and each destination keeps its own state and outcome.

The exact state of one destination inside a post: queued, sent, published, or failed. It is separate from the post's overall state.

An availability state saying suitable evidence could support a derived value. Postdom does not promise that the value has been estimated or that a computation exists.

A post observation left out of a best-post ranking because the requested metric value is null. The exclusion retains its availability state and reason where supplied.

A destination state entered when the provider or local watchdog records failure for that destination. The returned error code and detail remain part of its answer.

A post state entered when every destination fails or execution fails locally. It can retain recoverable evidence, but remains a recorded failure until reconciliation changes it.

A named Postdom operation exposed to a configured agent through the Model Context Protocol, with a machine-readable input and return schema.

A recoverable post state entered when execution begins more than 15 minutes after the scheduled time. Postdom stops instead of publishing late and returns control to a human.

An availability state saying the platform does not expose the field. The normalized value remains null and includes an explicit reason.

A Postdom field that gives comparable meaning to evidence returned from supported destinations while preserving its source, observation time, and availability state.

The absence of an evidence-backed metric value. Null is not zero and must stay paired with its availability state; only never and unverified guarantee a reason.

A measured numeric value of nothing. Zero is evidence and must never be converted to null or treated as missing.

The timestamp attached to evidence showing when Postdom observed or generated that read. It is not the post's scheduled or published time.

A post state used when published and failed destination outcomes coexist. Every destination answer remains visible; partial is not a vague sent status.

A human control that blocks execution for one account or blocks agent write activity across the workspace. Only a human can resume paused activity.

A set of normalized metric observations for a post at a recorded observation time, with source and availability metadata preserved for every modeled field.

A stored proposal for selected accounts, a UTC time window, an objective, and a maximum number of posts. At L2 it becomes an authorization boundary only after human approval.

The recorded result of evaluating a publish request against an approved plan's accounts, window, state, and remaining capacity.

Descriptive evidence for one approved plan's completed work. An agent can read it before proposing later work, but Postdom does not turn it into a recommendation.

The UTC start and end timestamps bounding when an approved plan can authorize eligible posts. It is not the schedule itself.

The durable Postdom record for one submitted video, caption, intent, schedule, authorization evidence, and one or more destination outcomes.

The exact overall state of a durable post record. It describes authorization and execution across all selected destinations and must not be renamed by an agent.

A destination state entered when the provider confirms publication for that destination. It retains the provider identifiers and publication evidence returned to Postdom.

A post state entered only when every selected destination is recorded as published. It is distinct from one destination publishing successfully.

The optional RFC 3339 UTC timestamp on publish_video that asks Postdom to schedule the post for an exact future time.

A saved local-time window in an L3 account policy during which new work is not authorized. The account timezone determines how the window is evaluated.

A modeled destination state reserved in storage before provider handoff. No configured production path currently creates it, so agents must not expect it from the provider result.

A buyer-facing name for one durable post record moving from accepted work through destination outcomes and measurement. The public wire contract exposes a post, not a separate run resource.

The future publishing work Postdom holds against exact UTC targets. It is a product concept represented by durable posts, not a separate public API resource.

A destination state saying the provider accepted the destination request. Sent is not published; the agent must keep reading for authoritative destination evidence.

The selected destination account with the lowest autonomy level in a multi-account request. Its level governs the whole request; Postdom does not split authorization.

A recorded completion state: published, partial, or failed. It ends normal polling, although recoverable local evidence can later reconcile partial or failed outcomes.

An availability state saying recorded evidence has not verified whether the field is exposed. The normalized value is null and includes an explicit reason.

The set of publishing visibility values a human permits in an L3 account policy. Work outside the saved allowlist is not authorized.

A comparison between the latest two completed account-local weeks. It describes movement in returned evidence; it does not establish causality or recommend the next action.

The human-owned Postdom boundary containing members, keys, connected accounts, policy, the Workspace Brief, plans, posts, and returned evidence.

Versioned workspace guidance for brand voice, captions, hashtags, timing context, and never-dos. A connected agent reads the current version before planning or writing.

A scoped credential an owner, admin or member creates for a configured agent connection. Postdom shows its exact MCP configuration once; the key stays out of chat and source control.