Newsroom Operations

Operate the Core-owned editorial ledger through a restricted, typed boundary for private drafts, safe structured content, scheduled or immediate publication, archival, immutable revisions, and public authenticity evidence.

BUSINESS CASES

Where this module fits

editorial workflow
governed publication
scheduled release
correction and archival
revision and authenticity verification

PRIMARY CONSUMERS

Who integrates it

editors
communications teams
publishing agents
compliance reviewers
Explorer integrators

PREREQUISITES

What must exist first

an authenticated owner context
admin:news:read for collection access
admin:news:write and an Idempotency-Key for mutations
approved editorial content and publication policy
the latest article version before any lifecycle action
an editorial_date for SCHEDULE

RECOMMENDED WORKFLOW

Compose the module safely.

01
list minimized article summaries with an exact lifecycle filter or search term
02
create a private draft with a stable slug and structured safe content blocks
03
review the returned revision and content commitment
04
apply a version-bound SAVE_DRAFT, SCHEDULE, PUBLISH, or ARCHIVE action with an attributed reason
05
re-read the article and verify its retained revision and proof chain
06
use the public Newsroom and Explorer reads only after the ledger reports publication

AGENT INTEGRATION

Machine-use boundaries

Creation always produces a private DRAFT; supplying editorial_date does not publish or schedule it.
Send only the documented structured body blocks. HTML, scripts, secrets, arbitrary objects, and unknown fields are rejected.
Treat expected_version as an optimistic concurrency boundary. On 409, re-read the article, review the intervening revision, and create a new intent rather than overwriting it.
Reuse the same Idempotency-Key only for a byte-equivalent retry of one logical mutation. A different request under the same key is a conflict.
author_name is a public byline, not authority. The authenticated profile is the actor recorded by the ledger.
Draft, scheduled, archived, or review state is not public publication. Do not announce or syndicate an article until the returned lifecycle is PUBLISHED.
Retain article_uuid, version, revision, content_commitment, previous_commitment, action reason, and proof identifiers for every release or correction.
Never interpret publication as website deployment authority, trading authority, or permission to mutate Explorer evidence.

Register only production-listed routes as executable tools, and re-fetch the deployed OpenAPI before generating or sending a request. Source-ready routes awaiting deployment are preparation references; planned contracts are non-executable.

MODULE CONTRACTS

Every mapped endpoint

Each operation states whether its request shape is authoritative in OpenAPI, reviewed as a planning profile, or intentionally left as an outline pending an owner schema.

GETList articles/api/v2/admin/news/articlesList restricted draft, scheduled, and published newsroom records.›POSTCreate article/api/v2/admin/news/articlesCreate a newsroom article draft.›PATCHUpdate article/api/v2/admin/news/articles/{article_uuid}Update, schedule, publish, or archive an authorized article.›