Claude Opus 5andbdeshi
1510a5ff7a
HARNESS.md described how the ceilings got where they are — a paragraph of changelog that grew with each raise. The ADR log is where history belongs, so the section now states what the two ceilings are for, where the values live, and how to read a raise. Any doc that narrates its own edits will do this again. theme-contract.md explained parse order three times: once in the fragments section, once under the stability rule, once under overriding. Once now, with the other two pointing at it. content-model.md carried a marker system — `[arc1]` build now, `[spec]` recorded intent, plus a standing instruction never to build from a `[spec]` section. The better answer than a stricter marker is no marker: the doc now describes only what the parser accepts, and the shapes nobody has asked for moved to ideas/exploration.md, which is storage and out of context by default. There is nothing left to build speculatively from, so nothing needs to say so. 518 lines to 469, and rule 6 plus the leaf/trunk test already cover the rest. A sweep for filler phrasing found almost none — the prose was already tight — so that part is two rhetorical tics rather than the cull expected. Reporting it honestly matters more than manufacturing a diff. No rule, gate, threshold or obligation moved.
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.