Decide that entropy review is a different product - #349
Merged
Conversation
Release v0.3.0
Release v0.4.0
Release v0.4.1
Release 0.5.0
Release 0.5.1
A review scored this project's direct effect on AI code entropy at 7.1 and asked whether it should detect what an agent actually does to a codebase: comments that restate the code, an abstraction used once, a function's responsibility widened, a compatibility branch protecting a caller that should have moved. The list is accurate and this repository does nothing about it. The question was never whether those failures matter -- it was whether they belong here, and the answer had been neither promised nor refused. That is the state that lets a claim drift in later, when somebody writes a launch post. Those checks read a diff. Everything here reads a record store. They share a motivation and no mechanism: judging whether an abstraction is premature needs taste about code, and saying "this was ruled out in March and the reason still holds" needs provenance, lifecycle and a trust boundary. Building the first inside the second gives one name to two data models. ADR-0013 already made this argument about a dashboard, an embedding layer and an organisation graph, and it recorded the measurements that matter here too: three registered runs found no significant effect from injecting more context. The value is control, not volume -- which records may be obeyed and which are stale. Entropy review bets on the hypothesis this project's own data declines to support. So it is out of scope, and the README keeps the distinction it already draws: this does not slow the rate an agent produces entropy, it stops that entropy being inherited by the next agent as settled design. The second sentence is what the lifecycle and the path scope do. The first is one this repository cannot support, and a future review scoring it low is describing the product correctly rather than finding a gap. Record-Id: r-entropyscope Limit: an unclaimed capability is indistinguishable from an unbuilt one, so a scope question left silent gets resolved later in whichever direction sells better Ruled-out: Shipping it as an optional skill in this repository | optional does not separate it -- the skill carries this product's name and plugin, and its failures read as this tool's failures Ruled-out: Deferring it to a later milestone | a deferral is a promise with no date, and this question has now been raised in two reviews Ruled-out: Leaving the README silent on it | silence is what produced the question twice Certainty: firm Blast: local Undo: easy Verified: readme, manifest and compatibility-matrix suites pass with the ADR added; the README and docs/COMPATIBILITY.md both already decline to claim entropy suppression, which is the state this decision holds Unverified: nothing executable changed
CommitLore — record lintTrailers: clean — 6 commits in Limits (1)
Ruled out (3)
Trailer violations fail this check. Active constraints are informational — they are what the repository already decided, not a verdict on this PR. |
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.
Closes #342.
The question was never whether verbose comments, single-use abstractions, widened responsibilities and accumulating compatibility branches matter. They do, they are common in agent-written code, and this repository does nothing about them.
The question was whether they belong here — and the answer had been neither promised nor refused, which is the state that lets a claim drift in later.
What decides it
Shared motivation, no shared mechanism. Judging whether an abstraction is premature needs taste about code; saying "this was ruled out in March and the reason still holds" needs provenance, lifecycle and a trust boundary. One name over two data models.
ADR-0013 made this argument about a dashboard, an embedding layer and an org graph, and its measurements apply here: M1 (p = 0.7480), M1-b (p = 0.0522), M2 (p = 0.2247) found no significant effect from injecting more context. The value is control, not volume. Entropy review bets on the hypothesis this project's own data declines to support.
The decision
Out of scope. Not deferred. No skill, no command, no roadmap entry implies it.
The README keeps the distinction it already draws, and it is worth stating in the negative because the two are easy to conflate:
A future review scoring direct entropy suppression low is describing the product accurately, not finding a gap.
Consequences worth naming
commitlore-entropy-reviewas its own repository composes at the agent, not in this codebase. That is a different decision.docs/COMPATIBILITY.mdcurrently decline to say it; that is the state to hold.Alternatives ruled out
Optional skill inside this repository — optional does not separate it. The skill carries this product's name and ships in its plugin; its failures read as this tool's failures. The separation that matters is the name.
Defer to a later milestone — a deferral is a promise with no date, and this has now been raised in two reviews.
Leave the README silent — silence is what produced the question, twice.