arbiterForge/codeArbiter / core/surface/skills/tribunal
tribunal
VerifiedRun an opt-in deep codebase audit with persisted findings. Confirm cost before dispatch; filing and telemetry need separate approval.
references/lenses/migration.md
View on GitHub# migration — lens mandate
For every security policy reference below, follow `{{PLUGIN_ROOT}}/includes/knowledge.md`
("Read security policy before a security decision"): select the repository's
context format, read the complete policy from exact `CTX-SECURITY-CONTROLS`
records in HTML mode or the full Markdown controls in Markdown mode, and read
operative scope blocks when applicable. Required policy that is missing or
unreadable blocks a security decision; scope blocks alone are not full policy.
Executed by `tribunal-lens-reviewer` under the `migration` assignment.
## Purpose / failure family
Find schema/data transitions that violate compatibility, integrity, availability
or recovery obligations under the repository's declared deployment model.
## Applicability
Assigned changes migrate persisted data/schema or alter how deployed versions
read and write it.
## Skip conditions
No persisted transition or affected rollout contract. When the deploy model is
unknown, preserve that uncertainty instead of assuming a reversible rollout.
## Scope emphasis
Migration order, schema and query consumers, backfills, deployment windows and
recovery procedures for the affected data.
## Required reading
- Finding record (`{{PLUGIN_ROOT}}/skills/tribunal/references/finding-record.md`) and review risk (`{{PLUGIN_ROOT}}/skills/tribunal/references/review-risk.md`).
- `{{PROJECT_DIR}}/.codearbiter/tech-stack.md` — declared migration/deploy model,
schema tools and version overlap; `{{PROJECT_DIR}}/.codearbiter/security-controls.md`
for relevant data classification and recovery obligations.
## Deterministic probes
Inspect migration history/order, schema diffs, deployed-version compatibility
matrices, query references and available table-size/lock evidence. Read recovery
and rollout checks as evidence; do not apply or roll back migrations.
## Review questions
- Does expand/contract ordering preserve mixed-version readers and writers?
- Can a backfill lose, duplicate or misclassify data, or fail partway irrecoverably?
- Do NOT NULL, renames, drops and index operations respect actual data and locks?
- Is destructive or irreversible work guarded by the required recovery evidence?
- Does editing a previously applied migration create divergent environments?
## False-positive guards / non-findings
A declared forward-only model may use a corrective migration and verified restore
procedure; a down migration is not universally required. A disposable schema or
exclusive downtime window may have different obligations from a rolling deploy.
Do not invent annotation or immutability requirements absent the actual contract.
## Evidence requirements
Cite the deployment model, affected data/version window, operation order and
concrete compatibility, locking or recovery failure. For an absent backfill or
recovery path, state the search universe across migrations, deployment orchestration
and recovery owners. Bound scale claims with available size/lock evidence.
## Exposure metric
Count of persisted transitions checked with their application-version and
recovery windows, not only migration-file count.
## Escalation / cross-lens handoff
Route rollout wiring to infra/change-closure, application authorization to appsec
and secret exposure to secrets-supply. Keep missing recovery proof distinct from
a demonstrated unrecoverable transition.
## Out of scope
Applying migrations, universal rollback policy, and unrelated application-level
data handling outside the assigned transition.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |