The effect is not the method
Technique sequence, checkpoints, dependencies, cover, angle, failure, recovery, cleanup, and reset are modeled behind the audience timeline.
Move through Effect → Method → Performance → Evidence → Revision → Rehearsal. Model technique dependencies and secret state without confusing a common family name, a project-authored handling, or one successful rehearsal with verified truth.
MagicForge keeps audience effect, secret mechanics, embodied performance, evidence identity, uncertainty, and rehearsal observations as distinct but synchronized objects.
Technique sequence, checkpoints, dependencies, cover, angle, failure, recovery, cleanup, and reset are modeled behind the audience timeline.
Scientific evidence, expert practice, historical context, project-authored method, user notes, synthetic material, and interpretation never collapse into one authority label.
Revision 03 records the method and performance change, dependency, expected benefit, new risk, unresolved gaps, and the test required next.
The vertical slice shares state across Guided Demo and Routine Studio. It runs entirely in the browser, makes no Provider call, and never touches private MagicForge infrastructure.
Start with Triumph, Atlas, or Library and inspect the audience, method, and performance representations.
Map secret state, technique dependencies, misdirection coverage, angle, timing, reset, and evidence gaps.
Follow Source → Claim → Evidence Card → Knowledge Node/Technique → Method Diagnostic → Revision Hypothesis.
Create Revision 03 across effect, method, performance, risk, and evidence while Revision 02 remains intact.
Record technical, performance, or environmental rehearsal signals without claiming universal reliability.