tri

What problem does it solve?

This skill solves the problem of chaotic, untraceable, and unsafe code mutations in the t27 spec-first development environment. Without enforced guardrails, developers accidentally edit generated backends, skip testing, or violate sacred physics constants, leading to toxic verdicts and broken silicon generation. This skill replaces ad-hoc editing with a structured, verifiable, and recoverable workflow.

Core Features & Use Cases

• Constitutional PHI LOOP Workflow: Enforces the five-step mutation cycle (Small Step, Hash Seal, Verify, Fixate, Register) with mandatory guardrails like NO-COMMIT-WITHOUT-ISSUE and NO-MUTATION-WITHOUT-CELL.
• Swarm Health & Self-Healing: Continuously monitors Queen Trinity health across six domains (SacredPhysics, Numeric, Graph, Compiler, Runtime, QueenLotus), automatically detecting anomalies and triggering recovery procedures like claim reclamation and spec replay.
• NotebookLM Session Memory: Queries existing notebooks before starting work to prevent duplication and automatically uploads session wrap-ups to per-issue notebooks, creating a persistent semantic memory for the swarm.

Quick Start

Use the tri skill to execute a complete PHI LOOP iteration for a .t27 spec mutation, including hash sealing, backend generation, conformance testing, toxic verdict checking, and automatic NotebookLM session wrap-up.