Division settings you ownadd, edit and drag to reorder — every write is persisted and audited
KeyKindValueLast written
No division settings have been recorded yet. This is a real empty store, not a failed read — add the first one below.
Keys are free-form — add whatever this division needs to carry. Kind is enforced server-side: json must parse, number must be numeric, boolean must be exactly true or false.
These rows live in software_division_setting inside software-agent-team.db — a separate sqlite file from the unwritable software.db that blocks the autonomy controls below. Every add, edit and reorder writes a row to the same audit trail the Agent Team uses, recording the previous and next value, who wrote it and when.
The autonomy controls below are still read-only — a different store, and that one cannot be written. The settings table above writes to software_division_setting inside software-agent-team.db and persists. The autonomy modes and master pause bind instead to pipeline_settings via /api/settings and automation_config via /api/automation, which both write through software.db, whose -wal and -shm siblings are directories rather than files; both endpoints return HTTP 500 on the running service. Rather than show a switch that only moves in the browser, every mode button and the master pause strip below is disabled with its reason.
Autonomy by capabilityModes are real policy from the operating contract; the controls are disabled
CapabilityWhat it doesModeApproval
StatusRead and publish service status, health scans and incident counts.Reviewer Jane
IntakeAccept incoming defects and requests and place them on the backlog.Reviewer Jane
QARun the mechanical QA gates against a change and record the result.Reviewer Jane
Code reviewRun independent code review and record an advance / hold recommendation.Reviewer Jane
FactoryDrive the app-factory build stages for a project.Kevin · threshold not set
ApprovalRecord an approve or send-back decision on a package awaiting approval.Kevin · threshold not set
DeployPush a build to production.Kevin · threshold not set
RollbackReturn a service to its previous build.Kevin · threshold not set
OpenCLIExecute shell-level commands on the box through the OpenCLI bridge.Kevin · threshold not set
CredentialsRead or rotate credentials and signing material.Kevin · threshold not set
Higher modes stay locked on money, production and credential capabilities. Kevin has not defined the handoff §12 money / risk thresholds, so Factory, Approval, Deploy, Rollback, OpenCLI and Credentials cannot be raised to Supervised or Autonomous from this surface even once a durable store exists. Deploy, Rollback, OpenCLI and Credentials are additionally declared off in the division matrix and run only through the Kevin-gated atomic deploy path.
Evidence, retries & escalationPer-capability gate rules from the operating contract
These rules are declared, not enforced. No runtime gate in this app currently reads the evidence, retry or escalation columns before an action runs, and the autonomy-audit table in brain.db holds zero rows (Phase-0 SW-8), so there is no record of them ever having been applied.
Master pause
Automation state: unknown — no readable pause flagDisabled — the pause flag lives in automation_config inside software.db, which cannot accept writes on this box, so pressing this could not actually stop anything. To halt Software automation right now, Kevin stops the loop at the server, not from this page.