Claude Opus 5andbdeshi
25d7045133
The cap was arbitrary and the wrong lever: what matters is that a question's answer changes the code, not how many such questions a request happens to carry. A request with six real forks now gets six, batched into one turn — splitting them to look brisk costs the human more than asking once. The instruction to ask is unchanged and still gated by "each with a default so silence answers". The rest is numbers the harness had no business holding. Three kinds, swept across every harness doc, and none of them wanted machinery. Restated values were the real fault: HARNESS.md carried the ceiling figures, which docs/README.md's single-source table says live in scripts/budgets.env and nowhere else. Prose repeating a value is a copy waiting to go stale, which is exactly the rule I was quoting at everything else. The ADRs keep old and new, as an append-only log should; the harness names the concept and points. Illustrative figures — how long verify.sh prints, surface.md against the source, how much the binary grew — drift every commit and carry no decision, so they now say "a line per gate", "an order of magnitude smaller", "roughly a third". Counts that restate their own list are the same fault in miniature: "the three gates people skip", "six commands", "three pieces of it are mechanical", "two sibling folders", "three cases, no fourth". Each is a number that goes wrong the day the list beneath it changes, and none of them was doing any work. Left alone deliberately: values with no other home — the ~50% overrun, the 72-character subject, 40 lines of stdlib over a dependency, toolchain versions. Those are the source, not a copy of one. No gate for this. It would have to guess which four-digit number is a budget rather than a year, an ADR, an HTTP status or a Go version, and a gate that fires on correct prose is a defect.
khosra
A flat-file personal publishing engine in Go. Point the binary at a directory of Markdown and it becomes an owned, networked home for fiction, webcomics, art, and essays, in English and Bengali. The site's content lives in its own repository, not this one (ADR-0011).
Build and run
Needs Go 1.26+ and git; nothing else.
make build # or: go build -o khosra ./cmd/khosra
make run SITE=/path/to/site # or: ./khosra -site /path/to/site
make test
make verify # everything the project enforces — green before every commit
make help lists targets. make is a convenience wrapper; go build, go test and
./scripts/verify.sh work on their own and are what the gate uses.
A site root is a directory holding content/, and optionally static/ and templates/. It lives in its
own repository, not this one — the binary is pointed at it.
If you are a human: start at HARNESS.md — what the scaffolding is, how to use it, and what to decide.
If you are an agent: start at CLAUDE.md — the constitution and the read order. It is loaded for you automatically; this file is not a prerequisite and nothing here is a rule.