RecurseWright is an evolving human–AI engineering system.
It explores what happens when people, AI, tools, methods, and engineering practice change together — while evidence, judgment, continuity, and human autonomy still need to remain visible.
It is not a fixed methodology.
It is developed through engineering work, experiments, artifacts, writing, and repeated re-evaluation.
Engineering on Moving Ground, and Other Pretty Problems with Stability
The first full RecurseWright article.
It begins with a small engineering decision and follows what happens as evidence, tools, boundaries, and the people involved begin to move.
Two interactive artifacts are part of the article rather than illustrations beside it.
What Does It Mean to Be Embarrassed to Use a Calculator?
An earlier trace of the questions that eventually became RecurseWright.
Smaller observations, experiments, and consequences that do not need to wait for a full article.
RecurseWright artifacts are small executable or interactive pieces of an investigation.
They are not demonstrations of a finished framework. They are ways to expose assumptions, make decisions observable, and create new evidence.
Source and versioned artifact implementations live in:
A RecurseWright claim is not protected by authorship.
It survives by evidence.
The same applies to methods, tools, artifacts, and RecurseWright itself.
RecurseWright is being built in public.
The articles, artifacts, practices, tools, and even the current boundaries of the project are expected to evolve.
What should not disappear in that evolution is the human capacity to judge, question, revise, and leave.