Repository navigation
pragmatic-architecture (new)
A design method for simple solutions that are not fragile, from the choice of model, state ownership and boundaries down to the order of implementation steps. It unfolds Kent Beck's rule: "For each desired change, make the change easy (warning: this may be hard), then make the easy change."
- Two tests, in order. A design that breaks a must under a realistic sequence of events is out. Among the admissible ones, prefer the design in which this change and the next plausible ones cost least.
- A route of eight steps, each ending in an output, from naming the change to rehearsing it. How deep to go is decided by what the change touches, not by the size of the diff.
- The context that decides a design is part of the method: eight groups of facts, a filter question, criteria, cost over the horizon and a stopping condition (
references/context.md). - A property card for each promise at risk: mechanism, assumptions, a counterexample of 3-4 events, the nearest failure the mechanism does not stop, evidence, recovery.
- References on models and boundaries, failure and recovery, the change path, and 22 moves indexed by symptom.
The architecture-consilium skill in pragmatic-orchestration applies the method with several independent architect models.
Not measured yet: the effect of the skill on real design work. One probe on a single task showed no difference with and without the core; the task was too easy to tell.
pragmatic-verification
- Case design: a mode, setting or permission the user can turn on needs a case that turns it off again and one that shows which state is current.
maintaining-macos-health
mac-heavyrewritten: a holder blocks other heavy jobs only while it is busy (its first 45 s, or while its process tree uses at least 50 % CPU or 1024 MB RSS), so something light wrapped by mistake no longer holds the queue.
fetch-url-as-markdown
- The script runs through
uvwith an inline PEP 723 header and a lock file, instead of a system-widepipinstall.