IN PRACTICE / OUR OWN DEVELOPMENT
The factory builds
the factory.
TUHFFF is used in its own development. Samuel directs the architecture and the work through conversation; assistants shape requests into tickets, and the forge coordinates implementation and review.
ONE COMPLETED IMPROVEMENT
Make an operating problem visible.
During development, resource pressure made some run failures difficult to understand. A follow-up request asked for visible process usage, a warning near the limit, and a clearer failure explanation.
This is a paraphrased account of a real change in TUHFFF’s private development history, checked on 15 November 2026.
- 01 / REQUEST
Describe the missing capability.
The ticket named the outcome: make resource pressure observable and make failures easier for an operator to interpret.
- 02 / TRIAGE
Turn the request into acceptance criteria.
Triage identified the metric, warnings, failure explanation, tests, and documentation needed, then assigned the work to engineering.
- 03 / IMPLEMENTATION
Produce a change with evidence.
An initial run failed. A later attempt produced the implementation, focused tests, and operating documentation. Its summary also recorded checks that had not been performed.
- 04 / REVIEW & MERGE
Bring the improvement into the product.
The change received an approving review and merged. TUHFFF gained process-pressure telemetry, warnings, and clearer explanations for certain run failures.
WHAT THIS EXAMPLE ESTABLISHES
A traceable path to a useful change.
A request moved through triage, implementation, tests, documentation, and review into the product’s codebase. Human direction and imperfect attempts remain part of the record.
The recorded checks covered focused paths. They did not establish every deployment case or sustained operation at scale. The example is evidence of a completed development change.
THE WORK CONTINUES
Building better ways
to work together.
Current experiments explore how agents reflect on incidents, identify missing dependencies, explain waiting work, and propose reusable operating lessons.
These are active development questions. We evaluate them through their recorded outcomes and carry accepted improvements through the same review process.
Read the current evidence and status ↗START HERE
Bring your own
useful first problem.
A demonstration can show how the process relates to your repository, priorities, and acceptance criteria.
Discuss a demonstration