Universalist

Use when current work must decide or reconsider an owned code boundary: introducing, removing, migrating, bypassing, or materially changing its semantic owner, admitted domain, representation, composition, compatibility, effects, failure semantics, or proof; or when repeated implementations distribute one law across owners. Skip routine implementation, validation, review closure, rebasing, Ship, and Land against an accepted architecture unless new evidence fires an invalidator. In Actuating, nominate only when architecture reconsideration is live. Explicit invocation always runs. Team mode requires explicit request.

tkersey Updated 70 repo stars

File contents

tkersey/dotfiles commit 0460381d69

Frequently asked questions

npx get-skill add tkersey/universalist