Skip to content
This repository was archived by the owner on Aug 8, 2026. It is now read-only.

docs: close C28, the equity spec's UC-2 is fixed - #58

Merged
mspinola merged 1 commit into
mainfrom
claude/c28-outcome
Aug 4, 2026
Merged

docs: close C28, the equity spec's UC-2 is fixed#58
mspinola merged 1 commit into
mainfrom
claude/c28-outcome

Conversation

@mspinola

@mspinola mspinola commented Aug 4, 2026

Copy link
Copy Markdown
Owner

Closes out docs/design/amendments-2026-08-03.md §C28 by appending its outcome.

§C28 recorded that the same stop-placement error lived in ../crucible-stack/docs/design/crowdmon_system_description.md UC-2, and deliberately did not fix it, since that is a shared working tree in another repo. It has now been fixed: mspinola/crucible-stack#21, merge 3efc36f, on their main.

Why this needs recording at all

A section that says "not edited" with no outcome is exactly the stale open marker that invites a second, divergent fix. That is the trap the swap-dealer handoff hit earlier today, where a README row read "OPEN, unclaimed" on top of finished analysis. §C28 would have read the same way to a session with no context.

What landed, and two things §C28 got wrong

All three changes §C28 asked for are in #21: defined-risk protection leads (it was already present, offered second as the alternative), widening is demoted to a trade-off with both sides named, and "a stop is a trigger, not a guarantee" is stated outright.

The outcome block also records where §C28 was thinner than it should have been, both from reasoning about a sibling document rather than reading all of it:

  • It missed the §7 preamble, which promised "stops that survive" — the same claim in miniature, one screen above the use case it was pointed at. Also fixed in feat(macro-pca): the futures absorption ratio, and what PC1 actually is #21.
  • It assumed the trade-off had nowhere to point. §C28 said the fix would need "both sides named" and stopped, because it reasoned from this repo where the classification lives in §A.10. The equity spec already had its own: UC-6, "Classifying a drawdown while it is happening", with a signature table separating a positioning unwind (mean-reverts) from a fundamental repricing (does not). feat(macro-pca): the futures absorption ratio, and what PC1 actually is #21 routes the widening decision to UC-6 rather than merely naming two outcomes, which is strictly better than what §C28 proposed.

The practical lesson, recorded in the block: when a claim is wrong, grep the document for the claim rather than fixing only the passage you were sent to.

Testing

Docs only. test_references.py passes; no test added or removed, so the four skip counts are unmoved.

🤖 Generated with Claude Code

crucible-stack #21 (merge 3efc36f) applies the correction C28 reasoned
about but deliberately did not make, since that file is a shared working
tree in another repo.

Recorded so C28 does not read as an open item. A "not edited" section with
no outcome is the stale marker that invites a second, divergent fix, which
is the trap the swap-dealer handoff hit earlier today.

The outcome block also records two things C28 got wrong, both from
reasoning about a sibling document rather than reading it:

It missed the section 7 preamble, which promised "stops that survive", one
screen above the use case it was sent to.

It assumed the widening trade-off had nowhere to point, because it reasoned
from this repo where the classification is A.10. The equity spec already
had UC-6, "Classifying a drawdown while it is happening", so the fix routes
the decision there rather than merely naming two outcomes. That is better
than what C28 proposed.

Docs only, no test added or removed, so the four skip counts do not move.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@mspinola
mspinola merged commit aef4f59 into main Aug 4, 2026
5 checks passed
@mspinola
mspinola deleted the claude/c28-outcome branch August 4, 2026 02:00
mspinola added a commit that referenced this pull request Aug 4, 2026
…counter collision

PR #58 landed C28 while this branch was in flight, which is the same shared-counter
collision the per-day amendment convention exists to reduce and does not eliminate.
Theirs merged first and keeps C28; the band-rule section here is now C29, along with
its reproducer function names and every citation of it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant