Architecture: the general scope and the new-project sequence (for M2.5) #104

Merged
dongar merged 2 commits from arch-general into main 2026-10-06 00:29:49 +00:00
Showing only changes of commit b78fd58c85 - Show all commits
+2 -5
View File
@@ -618,9 +618,8 @@ mean, how it fits, its first step. Labels steer what happens next:
5. **The architecture lands in one or more PRs,** treated as `design`, then the
plan's milestones.
An experiment before the project exists (does a library parse this format?) has
nowhere to run: the agent says so, and suggests making it a project or using an
existing project's build VM.
`general` never gets a build VM: an experiment that needs one (does a library
parse this format?) is a reason to start the project for real.
- **Progress** goes on the record issue: facts posted by the harness, prose by the
agent when there's something to say.
- **Finishing:** the last PR closes the issue on merge ("Closes #N"; earlier ones say
@@ -945,8 +944,6 @@ shared between agents.
- **More than one active work item:** needs per-item serialisation, an inference
scheduler and per-item intents. Build VMs and threads already separate workspaces
and conversations.
- **Somewhere to experiment before a project exists:** a shared scratch build VM
for `general` conversations, with tools but no push credential (L1, D1).
- **Stacked PRs:** starting a milestone before the previous one merges, after
experience with waiting (D4).
- **Build VM collection:** how long idle, and whether it needs the operator's word.