Automate spec-first .t27 mutations with hash seals and PHI LOOP guardrails.
npx skills add https://github.com/gHashTag/t27 --skill tri
Please help me install this Agent Skill. Skill: tri Source: https://github.com/gHashTag/t27/tree/main/.claude/skills/tri Command: npx skills add https://github.com/gHashTag/t27 --skill tri
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.
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.
High-intent search queries and answers about installing and using this skill.
Spec-first development structures code mutations around editable specifications, and hash seals enforce it by creating immutable verifiable checkpoints. This workflow prevents untraceable edits to generated backends, ensuring every mutation is verifiable and recoverable.
To automate conformance testing within a spec mutation workflow, you execute a PHI LOOP iteration that applies mutations, generates backends, and runs automated toxic verdict checks. This enforces TDD-inside-spec and validates sacred physics tolerances.
Yes, you need git and jq along with bc and uuidgen to run spec mutation guardrails. These dependencies support the constitutional PHI LOOP workflow, enabling hash sealing, spec verification, and session registration.
Yes, you can use NotebookLM for persistent semantic memory in automated testing. The workflow queries existing notebooks before starting work to prevent duplication and automatically uploads session wrap-ups to per-issue notebooks.
Swarm health monitoring triggers automatic spec replay to self-heal anomalies detected across Queen Trinity domains. When runtime or compiler health fails, recovery procedures like claim reclamation and spec replay restore operational integrity.
The best way to prevent accidental edits to generated backends is enforcing a structured mutation cycle with mandatory guardrails like NO-MUTATION-WITHOUT-CELL. This replaces ad-hoc editing with a structured, verifiable, and recoverable workflow.
Thiago-Cruz-engInitialize a Git repository with an initial commit in the current project directory.
gHashTagExtract session summaries from .trinity files and upload them to NotebookLM.
nanorepublicaValidate code against centralized global tech stack standards.
drxaibiOrchestrate continuous autonomous agent loops with quality gates and recovery controls.