Map Coupang Disagree and Commit onto have-backbone-disagree-and-commit - #60
Merged
Conversation
…mmit Flip the pending map on Disagree and Commit to a landed map in the audit pass, and drop 3007 from the expected pending list. The audit checker now fails until facets.json carries the mapping, which the next commit adds. Refs #47. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QkDGguDo4U2fr7BpaFeCVR
SCHEMA.md says row ids are unique within a principle, and a facet ref carries its principle, but the facets.json check keyed every row by bare id. That rejects the first facet whose members share row ids: Coupang 3007 mirrors Amazon 1013's after-the-decision and social-cohesion rows on purpose. Key source refs by principle and id, keep inline generated rows unique by id alone since they are one app table, and pin all three rules with tests. Refs #47. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QkDGguDo4U2fr7BpaFeCVR
The record already lists have backbone as an equivalent, and the challenge-then-commit behavior is Amazon 1013's, down to refusing to compromise for social cohesion, so the whole principle joins the facet the way Arm 2007 and Coupang 3014 joined bias-for-action: all six of its rows become source refs, in record order. Rebuild the manifest so 3007 carries the facet. Closes #47. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QkDGguDo4U2fr7BpaFeCVR
Scoping ref uniqueness by principle stopped catching an inline generated row that shadows a ref id on the same facet, which the bare id check had rejected by accident. The rule is real: porridge's generator reserves human ref ids so its rows never reuse one, and a rule only an app enforces is not a contract. Reject the clash in both orders and pin it. Refs #47. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QkDGguDo4U2fr7BpaFeCVR
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
2 participants
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 #47.
Coupang 3007 lands on
have-backbone-disagree-and-commit, the pending map from the #45 audit. The record carrieshave-backboneas an equivalent, the whole-principle pattern, so all six rows become source refs in record order:disagreeing-with-the-room,after-the-decision,social-cohesion,disagreeing-upward,someone-else-dissents,new-evidence. The facet's principles are now[1013, 3007, 6011]. No terms change; no record text touched.One validator fix rode along, forced by this mapping: 3007's row ids deliberately mirror 1013's (
after-the-decision,social-cohesion), andvalidate.pykeyed facet source refs by bare row id, stricter than the schema. SCHEMA.md says row ids are unique within a principle, and refs carry{principle, id}, so source-ref uniqueness is now scoped to that pair. Inline generated rows stay unique by bare id, since they are one app table. Three new tests pin all of it.Test first: commit one flips the 3007 audit entry to landed and trims the pending expectation, failing with
audit 3007: map is not on have-backbone-disagree-and-commit. The validator fix and the mapping follow, going green.Pending maps remaining: 3011.
🤖 Generated with Claude Code
https://claude.ai/code/session_01QkDGguDo4U2fr7BpaFeCVR
Generated by Claude Code