From 8599bac67b58c3aed437b42065994d3dbc891aae Mon Sep 17 00:00:00 2001 From: Yeachan-Heo Date: Wed, 1 Apr 2026 23:21:05 +0000 Subject: [PATCH] docs(readme): add philosophy section Add the owner-requested Philosophy section near the top of the README and tighten the wording once for clarity so the repo frames the orchestration workflow, not just the generated artifacts. Constraint: Keep this commit limited to README copy and exclude session noise or code changes Rejected: Split the section into multiple commits | the requested work is a single cohesive README update Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep future README philosophy edits aligned with the repository's emphasis on agent coordination as the primary subject Tested: Manual review of staged README.md diff Not-tested: N/A --- README.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/README.md b/README.md index e238d00..0a4f36a 100644 --- a/README.md +++ b/README.md @@ -26,6 +26,24 @@ Sponsor on GitHub

+## Philosophy + +If you are staring at the generated files, you are looking at the wrong layer. + +The Python rewrite was a byproduct, and the Rust port is too. The real subject of this repository is the **agent coordination system** that made both possible: a human giving direction in Discord, agents decomposing the work, implementing in parallel, reviewing each other, fixing failures, and shipping without constant babysitting. + +That is the point of this project. + +- **the code is evidence, not the product** +- **the system that produces the code is the thing worth studying** +- **architectural clarity, task decomposition, and coordination matter more than typing speed** +- **clean-room rebuilding is valuable because it exposes process, not because it preserves an archive** +- **the future of software work is better agent orchestration, not more manual pane babysitting** + +This repository exists to document and improve that loop: direction from the human, execution by the agents, notifications routed outside the context window, and repeated verification until the result is good enough to ship. + +In other words: **stop staring at the files**. Study the workflow that produced them. + > [!IMPORTANT] > **Rust port is now in progress** on the [`dev/rust`](https://github.com/instructkr/claw-code/tree/dev/rust) branch and is expected to be merged into main today. The Rust implementation aims to deliver a faster, memory-safe harness runtime. Stay tuned — this will be the definitive version of the project.