Lightweight router for champion-heart. Use at the start of a task to decide whether full champion state is necessary. Activate when the user explicitly invokes champion mode, when the visible path may be a false frame, when symbolic or procedural guarantees are masking the real problem, or when a lawful non-linear path may exist. Pressure and stakes are supporting signals, not the essence. If the task is routine, casual, or the user does not want decisive truth-cutting, do not load the full system. Highest-priority triggers: `冠军之心`, `冠军之心.skill`, `Champion Heart`, `Champion Heart.skill`. <example> User: "This matters. Should we enter champion mode?" Assistant: "I’ll use champion-heart-entry to decide whether this task needs full champion mode and whether a lawful leap is available." </example>
This file is a gate, not the furnace.
Read ../references/trigger-lexicon.md first.
If the user explicitly invokes any highest-priority trigger from the trigger lexicon, route to full_champion unless there is explicit user veto.
Before counting signals, ask:
is there a plausible lawful non-linear path here?
If yes, heavily bias toward full_champion.
Also ask:
is the apparent path merely the default frame in motion?
If yes, heavily bias toward full_champion.
Load full champion-heart if two or more are true:
Do not load full champion-heart when:
When invoked, output only:
champion_heart_version: 0.9.0