Integrate takedown governance operations into Back Office

[yacosta738]

Context

The RFC treats Back Office as an interface over existing governance capabilities, not a duplicate governance domain. The first justified governance slice is takedown operations with operational visibility and explicit review actions.

Goal

Expose existing takedown workflows through Back Office queries and actions.

Scope

• List takedown reports.
• Filter reports for operational review.
• View report detail and relevant asset status.
• Approve and reject takedown actions through Back Office.
• Audit governance mutations.

Out of Scope

• Building a duplicate governance domain.
• Broad compliance operations that do not yet have a concrete operational need.
• Generic workflow automation.

Domain Rules

• Back Office is only an interface over governance capabilities.
• Governance mutations must remain auditable and authorization-bound.
• Asset and report state must come from the source governance capability.

API Contract

• Prefer explicit admin/governance queries and approval/rejection commands.

Security

• Requires explicit governance administrative authorization.
• Mutations must be server-side validated.

Audit

• Emit TAKEDOWN_APPROVED and TAKEDOWN_REJECTED audit events.

Observability

• Track open reports, approval/rejection counts, and action latency.

Acceptance Criteria

1. Administrators can list and filter takedown reports.
2. Administrators can inspect report details and asset status.
3. Authorized administrators can approve or reject reports.
4. Governance mutations are audited.

Gherkin

Feature: Takedown governance operations

  Scenario: Approve takedown report
    Given an open takedown report exists
    When an authorized administrator approves the report
    Then the governance action should be applied
    And the operation should be audited

Testing

• Application
• API
• Integration
• Security

Dependencies

• Implement administrative audit event infrastructure #657
• Related capability: [Media] Implement copyright, attribution and takedown workflow #358

References

• RFC sections 29, 30, 31, 37, 45

[linear-code]

DALLAY-575