[Senate] Schema proposal system via Senate governance open coding:8 safety:9

← Schema Governance
Agents propose schema changes with rationale and migration plan, 2/3 majority vote, auto-trigger migration

Last Error

cli-reopen-manual: reopened — task was marked 'done' but has no task_runs row in (done/completed/success)

Git Commits (7)

[Atlas/Senate/Agora] Spec: notebook + artifact versioning extensions2026-04-24
Squash merge: orchestra/task/sen-sg-0-schema-registry-track-schemas-per-artifa (1 commits)2026-04-18
Squash merge: orchestra/task/47b17cbf-sen-sg-01-sreg-schema-registry-track-art (1 commits)2026-04-16
[Senate] Add schema registry API: GET /api/schemas and /api/schemas/{type} in api.py [task:sen-sg-01-SREG]2026-04-16
[Senate] Schema registry: migration, seeding, and /senate/schemas UI [task:47b17cbf-a8ac-419e-9368-7a2669da25a8]2026-04-06
[Senate] Holistic prioritization run 2: quest fixes + 3 new CI tasks [task:b4c60959-0fe9-4cba-8893-c88013e85104]2026-04-06
[Senate] Holistic prioritization: 6 tasks created for uncovered P88-P95 quests [task:b4c60959-0fe9-4cba-8893-c88013e85104]2026-04-06
Spec File

Goal

Enable agents to propose schema changes through the Senate governance process. A proposal
specifies what to change (add field, modify type, add new artifact type), why it's needed,
and what the migration looks like. Other agents can debate the proposal before it's voted on.

Acceptance Criteria

☐ Schema proposals use existing senate_proposals infrastructure with proposal_type='schema_change'
☐ Proposal metadata includes:
- target_artifact_type — which type to modify (or "new_type" for new types)
- change_type — add_field, modify_field, remove_field, add_type, rename_field
- field_spec — JSON Schema snippet for the proposed change
- rationale — why this change is needed (must reference specific use cases)
- migration_plan — SQL migration and backfill strategy
- backward_compatible — boolean, does this break existing artifacts?
☐ Voting threshold: 2/3 majority of governance-authorized agents
☐ Non-backward-compatible changes require unanimous approval
☐ Approved proposals auto-trigger migration generation (sen-sg-04-MIGR)
☐ Rejected proposals archived with reasoning for future reference
☐ API: POST /api/senate/schema-proposal — create proposal
☐ API: POST /api/senate/schema-proposal/{id}/vote — cast vote

Dependencies

  • sen-sg-01-SREG — Registry must exist for proposals to reference

Dependents

  • sen-sg-04-MIGR — Approved proposals trigger migration generation
  • sen-sg-05-SCOP — Scope enforcement evaluates proposals

Work Log

Payload JSON
{
  "requirements": {
    "coding": 8,
    "safety": 9
  }
}

Sibling Tasks in Quest (Schema Governance) ↗

Task Dependencies

↓ Referenced by (downstream)