1 Operator People Generic Consistency
Forgejo Actions edited this page 2026-09-25 16:38:07 +00:00

People Generic Consistency Diagnostics

Super Admin operator status exposes a read-only peopleGenericConsistency block at:

GET /api/admin/operator-status

Use it during the People-to-generic class-instance migration to decide whether legacy owner-local People state and generic People state are aligned enough for further migration work.

Status Values

  • consistent: generic People state is internally consistent and covers accepted legacy People assignments.
  • drift_detected: at least one legacy/generic parity check failed. Do not treat generic People state as the only authority until the drift is understood.

Counters

  • activePersonRecordCount: active owner-local person_records rows.
  • activeClassInstanceCount: active generic people/person class_instances rows.
  • missingClassInstanceCount: active legacy People records without a matching active generic People instance.
  • extraActiveClassInstanceCount: active generic People instances without a matching active legacy row or accepted generic occurrence.
  • eligibleAssignmentCount: accepted, non-superseded legacy People assignments eligible for generic coverage.
  • acceptedOccurrenceCount: accepted generic people/person occurrences.
  • missingAcceptedOccurrenceCount: accepted legacy assignments missing accepted generic occurrences.
  • staleAcceptedOccurrenceCount: accepted generic occurrences not backed by an active generic instance or accepted legacy compatibility assignment.
  • removedOccurrenceCount: removed generic People occurrences retained for provenance.
  • archivedClassInstanceCount: archived generic People instances retained for lifecycle/provenance.

How To Use It

  • Treat this as a migration diagnostic, not an automatic repair tool.
  • If drift_detected, inspect recent People migration/backfill, worker-result, owner-curation, and media-maintenance activity before adding more generic-only behavior.
  • This diagnostic covers owner-local People parity only. Collaborative People table retirement additionally needs parity checks for generic collaborative class instances, shares, roles, contributions, forks, revocations, representative metadata, and orphaned source mappings.
  • Destructive legacy People schema removal is blocked unless ADR 0039's retirement prerequisites are met.