Evidence over confidence
A green command carries more weight than a fluent claim.
Native Hew, grown in public
A software workshop that rewrites itself.
Hewbers turns approved issues into reviewed, tested changes while converting the machinery beneath that loop from Go to Hew.
01 / THE PREMISE
The interesting part is not that an agent can write code. It is whether the system can choose work, preserve intent, reject bad changes, recover, and keep going.
02 / THE LOOP
Every change has to survive the workshop.
Four stations. Durable evidence at every handoff. No prose-only gates.
-
A
Select
Choose one dependency-ready issue and fence ownership before work begins.
BACKLOG → CLAIM -
B
Build
Work in an isolated tree with only the capabilities the stage declares.
CLAIM → PATCH -
C
Prove
Run executable acceptance checks and an independent, SHA-bound review.
PATCH → VERDICT -
D
Land
Merge only the reviewed head, then release the claim and advance the queue.
VERDICT → MAIN
03 / WORKSHOP RULES
Autonomy with hard edges.
Review stays independent
The builder cannot grade its own work into main.
State survives restarts
Claims, attempts, and terminal decisions remain recoverable.
Resolved friction disappears
Fixed findings leave the active list so tomorrow's agents see today's truth.
04 / THE HANDOVER
The destination is native ownership.
Goobers is the bootstrap supervisor. Hewbers is taking over the journal, scheduler, forge lifecycle, review loop, recovery, and finally its own backlog.
- LANDEDDeterministic native core
- IN PROGRESSDurable autonomous runtime
- NEXTLive self-host canary
- PRIMARY GOALSustained self-improvement