Engine Trigger Router

Timeline

1. 1

   Start

   The meta-problem named

   Every ForgeKit tool is excellent — but only if Claude remembers to use it

2. 2

   20m

   triggers.md written

   Trigger Map + gate definitions for Schema, AI Route, API Route, Calendar, Dependency, Armory

3. 3

   40m

   Session contract + audit added

   Schema updated, ignition.md wired, hard fails added to build-session

4. 4

   60m

   Diff inference built

   8 INFERRED_RULES, dual diff range (HEAD + HEAD~1..HEAD), exclusion list, file-grouped warnings

5. 5

   80m

   Gate Miss Rate added

   build-trends tracks declared vs missed gates, scores engine health, writes to engine-health.md

6. 6

   90m

   Red-team proof

   Hard fail on missing contract confirmed; Calendar + Schema Gate caught from diff on forgehome files

7. 7

   95m

   Golden template + BOM trap

   _TEMPLATE.json created, PowerShell BOM trap added to ignition.md

What shipped

• .claude/rules/triggers.md — Trigger Router: maps 18 risky actions to required gates; gate checklists for Dependency, Schema, API Route, AI Route, Calendar Sync, Armory

• session_contract block — must be filled before code; build-session hard-fails if missing

• session_audit block — must be filled at Harvest; hard-fails if missing; cross-checks contract gates vs audit gates

• Diff-inferred trigger validation in build-session.mjs — git diff HEAD + HEAD~1..HEAD, 8 INFERRED_RULES, exclusion list for generated files, file-grouped warning output

• Gate Miss Rate metric in build-trends.mjs — declared vs missed gates, engine health scoring, written to engine-health.md

• forgekit-website/sessions/_TEMPLATE.json — golden session JSON with all blocks pre-scaffolded

• ignition.md §3 ORIENTATION — session_contract required before first file; trigger router line added

• ignition.md §8 HARVEST — session_audit write step added; PowerShell BOM trap added to KNOWN TRAPS

• Red-team proof: hard fail on missing contract confirmed, Schema + Calendar gates inferred from actual repo diff