Ester Clean Code - v0.2.1 is out (with v0.2.0 as the hardening baseline).
This is not a chatbot release.
It's a clean-code publication for a long-lived, local-first entity built for accountable action under real constraints (identity, privileges, budgets, fail-closed behavior).
What's new
v0.2.0 (baseline): public hardening baseline (no "silent defaults" for secrets; reduced token/trace leakage; policy-driven boundaries).
v0.2.1 (latest): hygiene-only cleanup (generated artifacts removed; ignore rules tightened to prevent reintroduction).
Why this exists
Long-lived systems don't fail from drama.
They fail from boring physics: fans fail, disks fill, clocks drift, keys leak, dependencies decay.
So this release is built around hygiene + fail-closed defaults, not "trust me" automation.
Bridge set
Explicit bridge: c = a + b isn't philosophy - it's wiring: a is the accountable human anchor, b is procedures/models - bounded by auditable privileges and a tamper-evident witness trail.
Hidden bridges:
- Ashby: control collapses when regulator variety < environment variety.
- Cover & Thomas: ambiguity lowers signal; governance needs names with operational meaning.
Naming note: AGI here = Advanced Global Intelligence, not "Artificial General Intelligence".
If you care about reality-bound safety (L4) + auditability, take a look - link in the first comment.