Problem
The current README opens by describing what the harness is (gates, scaffold, controls) but not who it's for. A newcomer landing from a GitHub link has to infer the audience from the feature list, which weakens the pitch for the project's distinguishing angle: production-grade quality when humans and LLM agents share the keyboard.
Proposed solution
Add a two-line opener at the top of README.md, above the existing pitch:
This template is for teams pairing AI agents with human engineers. The harness keeps quality consistent regardless of who's at the keyboard.
No structural changes to the rest of the README required.
Acceptance criteria
Priority rationale
First impression for anyone discovering the repo; cheap to land and disproportionately changes how the harness reads.
Problem
The current README opens by describing what the harness is (gates, scaffold, controls) but not who it's for. A newcomer landing from a GitHub link has to infer the audience from the feature list, which weakens the pitch for the project's distinguishing angle: production-grade quality when humans and LLM agents share the keyboard.
Proposed solution
Add a two-line opener at the top of README.md, above the existing pitch:
No structural changes to the rest of the README required.
Acceptance criteria
Priority rationale
First impression for anyone discovering the repo; cheap to land and disproportionately changes how the harness reads.