TS Evidence Graph: Make Every SKILL Instruction 100% Enforced

Description and use

Using @ttsc/evidence, every function must explicitly acknowledge each rule from the skill file; missing any annotation causes a compile error, ensuring 100% rule enforcement by coding agents.

Problem

Coding agents often ignore written rules, leading to non‑compliant code that still passes tests and builds.

Outcome

All functions now explicitly acknowledge each engineering rule; builds fail if any rule is omitted, guaranteeing that agents cannot bypass constraints.

Workflow

• 1. Write engineering principles in a skill file (e.g., SKILL.md).
• 2. Add @evidence annotations to each function, referencing the relevant rule.
• 3. Run the ttsc compiler (a drop‑in replacement for tsc).
• 4. The compiler checks that every @evidence annotation is present; missing ones trigger errors.
• 5. Fix the code to include all required annotations and recompile until all errors are resolved.

Evidence

Six frontier models, 60 runs, zero actually followed.

Source

Every rule turns into a statement each function has to write, and that is how all of them end up followed.

Source