kor-team

name	kor-team
description	Orchestrates significant coding work through kor-pi's fusion-native scout, planner, gated builder, dual reviewers, and documenter. Use for multi-file features, risky refactors, audits, architectural decisions, or work needing cross-provider validation.

kor-pi Fusion Team

Use extension-owned kor commands when work needs multi-model judgment. Raw host chat is not fused. A kor role is a contract/topology executed by both active profile lanes; it is never one model identity.

Profiles

• sota: Fable 5 ARCHITECT + GPT-5.6 Sol BUILDER
• workhorse: Grok 4.5 ARCHITECT + GPT-5.6 Terra BUILDER

Use /kor-profile to inspect and /kor-profile sota|workhorse to switch all future kor runs. A profile switch changes compute everywhere, not team roles or safety.

Deterministic delivery

Use /coordinate <task> for significant implementation:

1. Complementary scout briefs (breadth vs depth); an anonymized reducer fuses evidence.
2. Generator-critic planner (author → red-team → revise); workspace plan written under .kor/ (use --plan-only / --from-plan for human checkpoints).
3. ARCHITECT designs an immutable acceptance gate before mutation; baseline must be RED.
4. One BUILDER-lane writer implements with seeded corrections/learnings; unchanged gate runs.
5. Cross-family claim verification after gate-green; REFUTED claims re-enter the correction loop.
6. Correctness and security each run two independent reviews on a parent-computed changeset; parent code computes authoritative non-downgrading envelopes before reducer prose.
7. Any required fix returns to the one writer under one bounded correction budget; unchanged gate and both reviews rerun.
8. Both lanes assess documentation; a fresh reducer plans it; one documentation writer applies it only after gate/reviews pass.
9. Final unchanged gate, repository validation, provenance, calls ledger, summary.json, and durable report.md establish completion.

PASS and PASS WITH NOTES require non-empty evidence, non-empty residual risk, and no unresolved fix. Worker failure retries exactly once and then fails closed. Malformed or empty evidence, a BLOCKER/HIGH, reducer failure, gate failure, budget/correction exhaustion, or cancellation cannot become fused success.

Other compositions

• /parallel --agents scout,planner <task> runs read-only logical fusion cells under physical concurrency limits. Writer topologies are rejected.
• /debate --agents planner,security-reviewer --rounds 2 <topic> fuses every position/round with linear handoffs, then runs a fresh pair-plus-reducer judge preserving dissent.
• /opinion <task> returns two independent lane artifacts without reduction; partial output is never labeled successful fusion.
• /fusion <task> returns neutral dual-lane workers plus an anonymized attributed reducer.
• /auto-validate <task> runs fused planning, gated one-writer action, and claim verification.
• /coordinate --plan-only / --from-plan <file> checkpoint or resume planning without re-scouting.
• /kor-replay <run-dir> re-renders a finished mission report from artifacts.
• /scout, /plan, /build, /review, /security, /document execute trusted role topologies as extension handlers.
• /team is deterministic help/composition, not a host-improvised prompt protocol.

The typed subagent tool returns fused logical results in single/parallel/chain modes and exposes no lane/model/topology bypass. Package/global scope is default. Project config/resources require Pi project trust and explicit approval; they may select a profile and reduce capabilities but cannot redefine models, families, topology, or fusion.

Mission Deck is default-on in Pi's TUI and shows model-first lane cards, activity trails, fusion receipts, stage timeline, gate, both-lane envelopes, per-family cost, and cancellation state. Use /kor-ui full|compact|off to change presentation without changing execution; Tab focuses an active cell, Ctrl+K opens the focus overlay, and Escape cancels the complete run. Use /kor-routes for the frozen pair/topologies and /kor-doctor for schema, trust, family, provider, model, and thinking-ceiling checks. Treat /tmp/kor-pi-* artifacts as sensitive.