Skip to content

Epic: Build Studio and an admin API with management parity #7

Description

@alexeygrigorev

Normative spec: 06 — Studio and admin API

Outcome

Provide /studio/ and /api/v1/admin/ as two safe adapters over the same services, permissions, validation, concurrency controls, idempotency rules, and append-only audit trail.

Boundaries

Django admin is break-glass only. Studio does not need browser-side API self-calls; code-level service and capability parity is required.

Epic completion gate

  • Capability registry covers every management action and CI detects parity drift.
  • Role/object/field permissions, staff sessions, and scoped hashed API principals pass positive and negative tests.
  • OpenAPI covers all routed management operations and long-running operations have resources.
  • High-risk actions, exports, stale writes, retries, and audits behave consistently.

Dependencies

Foundation starts after #1; domain-specific management screens depend on their domain services. Decision-free Studio authorization/audit primitives are extracted into #86; production identity and final high-risk completion remain gated by #20/#28 through #32.

Child issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    P0Must-have or release-blockingadminArea: adminepicParent issue grouping implementation workintegrationArea: integration

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions