Skip to content

[positioning] Name the ICP + pre-empt the overhead objection (small README edits) #72

@SUaDtL

Description

@SUaDtL

Source: positioning review (ICP naming upheld; the rest refined to small edits, NOT a hero rewrite — the first-pass "lead with governance" advice was rejected as stale: README.md:7 already names the audit trail and /ca:audit is already in the top-8 table).

Concrete, surgical edits:

  1. Name the ICP — add a one-line "Who it's for" near the top: e.g. "for teams and power users who let agents write real code and need to prove what happened — and who'd rather a tool BLOCK than apologize." The README currently addresses a generic "you"; README.md:37 filters on temperament, not audience.
  2. Surface the overhead answer — pull the load-bearing sentence from README.md:322 ("the failure mode of an eager AI assistant is plausible-but-wrong work that ships"), currently buried in a collapsed <details>, up into "What it is" after the "It will not" bullets. Add one sentence that ceremony scales to change size (the small lane and /ca:chore exist but a skimmer only sees heavyweight gates).
  3. Reframe sprint autonomy — rewrite the lead-in at README.md:148 from "One deliberate exception: autonomy" to dream-first: "Autonomy with a paper trail: go to bed, wake to a reviewed PR and a log of every call it made," keeping the guardrails sentence after it. (No new section — the featured table at :223 already leads with the payoff.)

Effort: S. Note: a website is deliberately deferred — the repo README is the right shareable surface until there's usage to point to.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationmarket-evalFrom the 2026-06 multi-agent market-readiness evaluation

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions