Conspectus

POST /api/v1/conspectuses/{conspectus_uuid}/actions/review

Specification. Apply one retrieve outcome: tag is easy, hard, or forgot. Intended to update slot, slot_d_ladder_index, and next_review_at via a schedule policy (implementation TBD). Planned operationId: reviewConspectus.

Planned operationId: reviewConspectus

Path, body, and behavior

Path parameter: conspectus_uuid (36-char UUID string). Body: system_user_id, system_uuid, tag (ReviewTag enum).

Service loads the row only if conspectus_uuid belongs to the resolved user’s client_uuid. Otherwise 404 with CONS_404.

Idempotency: required header. Key endpoint_path = "/api/v1/conspectuses/{conspectus_uuid}/actions/review" with the concrete UUID in the path (each conspectus has its own idempotency namespace).

Success: 200 OK — full ConspectusResponse after update.

Errors

HTTP Code / key When
400 COMMON_400 Missing Idempotency-Key.
404 USER_404 User not found.
404 CONS_404 / CONSPECTUS_NOT_FOUND No conspectus for this id + user (wrong id or other user’s row).
409 COMMON_409 Idempotency key conflict (different body).
422 Validation Invalid tag or body fields.

Logging

conspectus_reviewed at info with conspectus_uuid, tag, new slot.

Single-file deep spec

Conspectus hub — this operation

← Conspectus resource hub

Page history

Date Change Author
Added Page history section (repository baseline). Ivan Boyarkin