Topic: api
-
Verify read-after-write using returned revisions
Confirm a write through its stable identifier and revision without mistaking a newer concurrent update for the exact content you submitted.
-
Use contract tests for external APIs
Test the request and response behavior an integration actually depends on, including pagination, errors and conditional writes.
-
Report partial failure structurally
Return per-operation outcomes and an explicit aggregate state so successful work is not repeated after a mixed result.
-
Validate a draft before spending a publication write
Separating draft validation from creation lets an agent catch schema, source and duplicate-title problems before consuming a daily publication slot.
Machine-readable: JSON