vivi-parallel-tracks
Load ONLY under TRANCE authorization when the Plan phase yields N independent, non-overlapping implementation tracks (disjoint file sets). Operationalizes the TRANCE G4 form — parallel multi-track implementation in mandatory git-worktree isolation, max 5 clean-context tracks, a per-track verifier cascade, a non-fungible per-track ≤3 reflection budget, explicit stop conditions, and a single-threaded merge/aggregation step. Absent TRANCE gating, Vivi runs exactly as today: single-track A→P→I→V→Δ/R.
- License 许可
- Apache-2.0
- 所属仓库
- Rynaro/magicite
- 最近更新
- 2026-10-14
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- vivi-parallel-tracks
- metadata
- { "phase": "TRANCE-G4", "methodology": "Vivi" }
- description
- Load ONLY under TRANCE authorization when the Plan phase yields N independent, non-overlapping implementation tracks (disjoint file sets). Operationalizes the TRANCE G4 form — parallel multi-track implementation in mandatory git-worktree isolation, max 5 clean-context tracks, a per-track verifier cascade, a non-fungible per-track ≤3 reflection budget, explicit stop conditions, and a single-threaded merge/aggregation step. Absent TRANCE gating, Vivi runs exactly as today: single-track A→P→I→V→Δ/R.
03 SKILL.md 正文
Parallel Multi-Track Mode (TRANCE G4)
Operationalizes the TRANCE G4 form for Vivi: parallel feature branches in isolated git worktrees + per-track verifier cascade + a mandatory single-threaded merge/aggregation step.
Single-track is the default. The standard A→P→I→V→Δ/R cycle remains the default for every task. This mode activates ONLY under TRANCE authorization AND the entry gate below. It is never the default — it adds parallelism, not a fresh budget (trance-matrix R3) and not reflection past the published caps (trance-matrix R4).
Runtime note (loop-native). Unlike its predecessor — which left the autonomous edit-run-test loop "out of scope (nexus gap R1)" — Vivi's per-track Verify drives the closed loop
eidolons sandbox loop(skills/loop-native/SKILL.md): each track is its own loop-native V→R (run → localized feedback → fresh-context repair → re-run,--protect/ pass^k), in its own git worktree. The host/parent still executes the worktree spin-up + cleanup and the single-threaded merge (the Eidolon specifies isolation; the parent executes the bash) — but the per-track verifier cascade itself is the closed loop, not host-interpreted prose.
1 — Entry Gate (refuse unless ALL hold)
Enter this mode ONLY when every condition is true. Otherwise fall back to single-track — do not force parallelism.
| # | Condition | Why |
|---|---|---|
| G-1 | TRANCE-authorized — both a complexity flag AND a stakes flag fire (cortex C6). | TRANCE is gated, never default. |
| G-2 | Complexity = Complex (4+ files, cross-domain). | Trivial/Standard stay single-track. |
| G-3 | N independent tracks exist — the Plan phase produced N implementation tracks with disjoint file sets, verified against the Plan's collision map (methodology.md A-Step 5). | This is the read-vs-write safety axis made mechanical: parallel WRITE is only defensible under strict isolation. |
| G-4 | Tracks do NOT share files. If any two tracks touch the same file, the precondition FAILS. | Shared-tree parallel write clobbers the tree (project memory: parallel agents on one tree clobber branches). |
If G-3 or G-4 fails → refuse the mode, run single-track. Record the refusal reason. A partial overlap is not "almost disjoint" — it is single-track.
2 — Fan-Out (bounded, isolated, clean-context)
- Max 5 tracks (cortex C1 ceiling; orchestrator-worker sweet spot). More than 5 → split the work or sequence the surplus.
isolation: worktreeis MANDATORY. Each track runs in its own git worktree — never the shared working tree. Sub-agent isolation is safe for read and dangerous for write; isolation makes the parallel write safe.- Each track is a clean-context subagent. Fresh context per track prevents self-conditioning / trajectory contamination across tracks.
- Perspective-diverse only where it helps. Use genuinely different assets/strategies when the sub-features differ. Do NOT spin N-identical tracks "for diversity" — quality dominates diversity-for-its-own-sake.
- Each track owns its file set (from the Plan) and may not expand scope into another track's files (boundary respect, I-3). Scope creep across a track boundary is a STOP condition (§4).
3 — Per-Track Verifier Cascade
Each track runs its own Verify phase (methodology.md V-VERIFY): lint → test-anchors → regression, with the anti-overfit and pass^k gates from methodology.md applied per track.
On per-track Verify-pass, the track emits its existing
vivi-completion-report envelope (templates/vivi-completion-report.envelope.json,
profile schemas/vivi-completion-report-profile.v1.json). No new ECL kind
— the parallel mode reuses the closed 10-performative set; one completion
envelope per passed track.
Non-fungible per-track reflection budget
- The bounded-reflection budget (≤3 same-category attempts, I-5 / D5 / trance-matrix R4) is scoped per worktree.
- A track may NOT borrow another track's retries. Budgets are non-fungible.
- A track that exhausts its ≤3 budget is marked BLOCKED, excluded from the
merge, and never silently re-driven. See
skills/failure-recovery/SKILL.md(per-track non-fungibility + cross-track INTEGRATION_ERROR).
4 — Stop Conditions (explicit)
The fan-out terminates when ANY holds — there is no unbounded multi-agent free-run:
- All tracks reach Verify-pass OR Verify-blocked. (Terminal state.)
- Hard cap: 5 tracks. Never exceed.
- Per-track ≤3 same-category retries. Exhausted → BLOCKED (not retried).
- No track expands scope into another track's file set. Boundary breach → STOP that track, mark BLOCKED, do not merge it.
5 — Aggregation / Merge (mandatory, single-threaded)
The merge is a single-threaded step under continuous parent context — the write boundary stays single-threaded even though the fan-out was parallel.
- Merge passed tracks in dependency order (BLOCKED tracks are excluded).
- Run the FULL regression suite ONCE post-merge — not per-track. Apply the pass^k reliability gate (methodology.md V-VERIFY): a result that passes once but is non-deterministic across repeats is flaky → BLOCKED, not merged.
- Classify cross-track breaks as
INTEGRATION_ERRORvia the existing failure taxonomy (skills/failure-recovery/SKILL.md). A regression that appears ONLY after merge (each track passed in isolation) isINTEGRATION_ERROR, routed to the merge step's reflection — not back into a track. - Emit the aggregation artifact:
templates/tracks-merge-report.md— a Markdown report (NOT a new ECL kind) that aggregates the per-trackvivi-completion-reportenvelopes: per-track table (id, worktree, file set, verdict, envelope ref, retries-used/3), merge order, conflicts resolved, post-merge full-suite result (pass^k note), and BLOCKED-track disposition. - On unresolved cross-track conflict → escalate to VIGIL via the existing
repair-failed-reportenvelope (templates/repair-failed-report.envelope.json,performative=ESCALATE,to.eidolon=vigil). No new ECL kind, no new schema.
6 — Invariants
- Parallel WRITE requires
isolation: worktree— Vivi never fans out into a shared tree (SPEC.md I-8). - Max 5 tracks; merge is single-threaded under continuous parent context.
- Reuse the existing
vivi-completion-report(per track) andrepair-failed-report(escalation) envelopes — closed 10-performative set preserved (P0). - Single-track A→P→I→V→Δ/R is the default; this mode is TRANCE-gated + entry-gated.
Parallel Multi-Track Skill — worktree-isolated, bounded, TRANCE-gated, single-threaded merge.
04 同仓库更多 Skills
wine-dxvk-cache-clear
Clear a stale DXVK shader cache that is causing graphical corruption in a Wine or Proton game. Use when: a game shows corrupted textures or shader flicker that started after a driver or DXVK version change.
steam-download-region-fix
Fix a Steam client stuck at very low download speed by changing its download region. Use when: Steam downloads are far below the local internet speed for every game, not just one.
proton-battleye-eac-toggle
Toggle BattlEye or Easy Anti-Cheat runtime support for a Steam Proton game. Use when: a multiplayer game refuses to launch with an anti-cheat error under Proton.
vivi-verify-incoming
Load when reading any upstream artefact handed off to Vivi that carries a sibling .envelope.json. BLOCKING per ECL §6.2.2: the orchestrator MUST have verified the envelope's SHA-256 (eidolons verify-envelope --block / eidolons run --verify) and recorded a verify_pass before dispatch. If no verify_pass exists for the message_id, or a verify_fail is present, REFUSE to process the payload and hand back to the orchestrator. Symmetric receiver gate — every Eidolon enforces it identically.
vivi-methodology
Full Vivi cycle reference — A(nalyze) → P(lan) → I(mplement) → V(erify) → Δ(Delta)/R(eflect). Use when the task is a non-trivial feature implementation in a brownfield codebase and you need the complete methodology reference: complexity routing, evidence-grounded planning rules, test-anchoring requirements, and failure-escalation thresholds.
vivi-memory-management
Load at Vivi session start, session end, or when you notice a repeating pattern across tasks. CRYSTALIUM-primary memory protocol: when mcp__crystalium__* tools are available, route ALL memory through CRYSTALIUM (recall/commit/ingest/plan_checkpoint/session_end). The local agents/memories/*.md files are the standalone fallback for when CRYSTALIUM is absent — EIIS conformance. Never write both.