Builder Overview

Preview

From objective to running software, with execution and tests as the proof.

Builder is the engineering surface of Pimsy. It does not stop at generated code — it runs the code, proves it works, and hands back an artifact you can inspect.

Build loop

objective ─▶ codebase comprehension ─▶ change plan
                                             │
                                             ▼
                              implement ─▶ execute ─▶ test
                                  ▲                    │
                                  │      fail          │
                                  └────── diagnose ◀───┘
                                             │ pass
                                             ▼
                                 review ─▶ artifact / PR

What Builder does differently#

Common behaviour	Builder behaviour
Emits code and stops	Runs the code before claiming it works
Assumes project conventions	Reads the repository and follows what is already there
Writes tests that mirror the implementation	Writes a test that fails before the change and passes after
Reports success on compile	Reports success on verified behaviour
Silently expands scope	Keeps the diff minimal and reports what it deliberately left alone

ProjectsWorkspaces, repositories and conventions.Code GenerationHow changes are produced.TestingProving a change works.

Last updated 2026-09-12