docs: lead with the harness problem, not the agent shape - #146
Merged
Conversation
The old tagline described what Reigner is (a single agent over a compiled
corpus) and skipped what breaks without it. The actual problem statement was
buried in PRINCIPLES.md, the one doc nobody reads first: keeping one agent
coherent and cheap as its context grows over a long run.
Retagline all five surfaces on "A harness for question-answering agents over
your own documents — bounded context, bounded cost, every claim cited", and
open the README and docs index with the failure mode before the description.
"toolkit"/"toolbox" was doing positioning work it can't do — it says you have
many things, not what any of them do.
Also reframes the coding-agent disclaimer as a distinction inside the category
("a harness for retrieval agents rather than coding agents") now that harness
is the lead noun, and names Claude Code and Codex CLI so the exclusion is
concrete. GitHub About updated to match.
The Project Structure and Build sections still described a repo that held only planning documents: a "planned" source tree, no build system, no pyproject.toml, and pytest as an "expected future test command". All of that has been true for a while. Replaces them with the real layout (adding reigner/server/, which the list never had) and the actual uv commands, matched against .github/workflows/ci.yml so the two can't drift silently. Also drops the last "toolkit" from the positioning sentence.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The old tagline — "A single agent that answers from your compiled corpus — every claim cited" — described what Reigner is and skipped what breaks without it. The actual problem statement was buried in
PRINCIPLES.md, the one doc nobody reads first: keeping one agent coherent and cheap as its context grows over a long run.What changed
New tagline on all five surfaces:
README.mddocs/index.mdmkdocs.ymlsite_descriptionpyproject.tomldescriptionSPEC.mdThe README and docs index now open with the failure mode before the description. "toolkit"/"toolbox" is gone from the positioning copy — it's a container word that says you have many things, not what any of them do.
Notes
gh repo edit(not part of this diff).AGENTS.mdstill says "toolkit" and also still claims the repo "currently contains the v0 planning documents" — stale for unrelated reasons, left for a separate pass.