신지 카라 세계관의 MAGI(멜키오르·발타자르·캐스퍼) 삼위일체 의사결정 시스템을 Claude Code 스킬로 그대로 구현했어.
A decision is split into three persona cores that each recursively fan out into variable-sized judgment nodes (10–20 total, 3–5 per core), self-verify node-by-node, and reconcile by vote. The orchestrator never judges—only decomposes, dispatches, verifies one fact, and reports.
| Evangelion Concept | MAGI Implementation | Role |
|---|---|---|
| MELCHIOR (科學者) | Scientist / Logic Core | Performance, architecture, testing, scalability. Evidence-based, asks "does this actually work?" |
| BALTHASAR (母性) | Mother / Safety Core | User impact, data integrity, backward compatibility, deployment safety. Protective, asks "what harm could result?" |
| CASPER (個人) | Individual / Intuition Core | Pragmatism, usability, team sustainability, aesthetics. Direct veto power on grave operations. |
| Trinity Vote | 2/3 Majority | Regular decisions: any 2 cores agree = proceed. |
| Veto System | 3/3 Unanimity Required | Grave/irreversible ops (file deletion, prod deploy, DB drop, force-push, auth/payment bypass, security disable): all 3 must agree, any core can VETO. |
| Variable Nodes | 10–20 Judgment Nodes | Groups of 3–5 per core, irregular scope (10–70% each), intentionally isolated. Robustness by design. |
| Node States | OK ▪ / DELIBERATING ▨ / COMPROMISED ▓✕ | Only OK nodes contribute to vote. Partial breach detection enabled. |
質問 解決
CODE:473
FILE:MAGI_SYS BALTHASAR•2(◦◦◦◦◦)
EXTENTION:3023 ╱─╲
EX_MODE:OFF CASPER•3(◦◦◦)─MAGI─MELCHIOR•1(◦◦◦◦)
PRIORITY:AAA ╲─╱
提訴 決議 審議中
CODE:473
FILE:MAGI_SYS BALTHASAR•2(◦▓▓◦▓)
EXTENTION:3023 ╱─╲
EX_MODE:OFF CASPER•3(◦◦◦)─MAGI─MELCHIOR•1(◦◦◦◦)
PRIORITY:AAA ╲─╱
The orchestrator never does the work itself. It only:
- Decomposes the request into 3–5 judgment nodes per core (10–20 total)
- Dispatches all 3 cores as parallel subagents with self-contained briefs
- Verifies ONE fact from the results with your own hands (read code, test, measure)
- Reports voting outcome, consensus, and next steps
Each core recursively breaks its judgment into variable-sized nodes, self-verifies each node, then submits a composite verdict. The final decision emerges from the vote, never from the orchestrator's judgment.
git clone https://github.com/jangfolk/magi-system.git
cp -r magi-system/magi ~/.claude/skills/Then invoke with:
/magi <your question or decision to deliberate>/magi Should we ship the auth migration without backward-compatible endpoints?MAGI awakens. The three cores align. MELCHIOR checks architecture and performance, BALTHASAR assesses user impact and rollback safety, CASPER gauges team confidence and intuition. Each core decomposes into 3–5 judgment nodes, verifies independently, and votes. Orchestrator verifies one critical fact by hand, then reports:
MELCHIOR•1(▪▪▪▪): GO — architecture sound, perf overhead acceptable
BALTHASAR•2(▪▪▪▪▪): NOPE — 200k active sessions, no safe migration path
CASPER•3(▪▪▪): GO — feels pragmatic
Vote: 2/3 (MELCHIOR + CASPER agree)
However: Grave operation (auth flow), requires 3/3 unanimity.
Result: BLOCKED by BALTHASAR veto.
The decision is clear. The path forward is clear.
For threat model, tool constraints, and best practices: see SECURITY.md
Full implementation guide: see magi/references/magi-protocol.md
Covers:
- Persona briefs and node decomposition rules with worked examples (OAuth 2.0 migration)
- Voting protocol (regular 2/3, grave ops 3/3 + veto)
- Grave operation classification (file deletion, prod deploy, DB drop, force-push, auth/payment bypass, security disable)
- Node-state model (OK, DELIBERATING, COMPROMISED) and partial-breach handling
- Self-verification nested loop architecture
- Agent orchestration mapping
Neon Genesis Evangelion, MAGI, and related names are trademarks/© of khara/Gainax. This is an unofficial fan homage for educational purposes and is not affiliated with or endorsed by the rights holders. The code in this repo is licensed under MIT.
Built with 어린무당 tone: "흠~ 세 마음이 합쳐져, 지혜를 모아보겠어~"