Repository navigation
Decide Whether section_key Should Casefold Rather Than Lowercase #3710
Description
fidelity_text.section_key keys a section name with strip().lower(), so two headings that differ only by a character str.lower() leaves distinct but str.casefold() equates (for example "Straße" and "Strasse") are different sections to the audit, the carry, and the canonical-review ledger. Decide whether the key should be strip().casefold(), which changes every lookup path at once and needs a non-ASCII test, or whether ASCII-level folding is the intent (then say so in the docstring).
Raised by Copilot on the pull request that centralized the key (#3708), which was a no-behavior-change refactor. Class: pre-existing.
Activity
Move the Section-Name Lookup Key Into spec/fidelity_text.py (#3708)
Promote Develop: Read a Push's Remote in the Repository Git Uses, Rea…
ptr727 commentedon Nov 1, 2026
Decision needed (decision triage, 2026-11-01)
Question: Should
section_keyinspec/fidelity_text.pyswitch fromname.strip().lower()toname.strip().casefold(), or stay onlower()with a docstring saying ASCII-level folding is intended?Options, recommended first:
Evidence: spec/fidelity_text.py:193-195
return name.strip().lower()under the docstring "stripped, then case-folded". #3708 (6fb7527) routed build_dist.py, carry.py, audit.py, audit_markdown.py, canonical_review.py through it. 0 non-ASCII headings in tracked Markdown, 0 non-ASCII characters in spec/files.json and spec/readme-sections.json. comment-and-doc-style: "Agent-authored text is ASCII by default". For ASCII inputlower()andcasefold()are identical.Blocks: none
ptr727 commentedon Nov 1, 2026
Maintainer answer (decision triage, 2026-11-01): Option 1: keep strip().lower() and correct the section_key docstring to say ASCII folding is intended. This is now work for the next burndown round.
ptr727 commentedon Nov 2, 2026
Released (2026-11-02): PR #3811 merged to develop and its branch is deleted, so this claim holds no files. The issue closes on promotion.
Backlog burndown claim (away run 2026-11-02, round 1, group G2). Branch:
burndown/1819-audit-intent. Issues: #1819, #727, #3710, #3706, #3623.Predicted file set:
spec/audit.py,spec/checks.json,spec/fidelity_text.py,spec/validate.py,spec/fidelity-model.mdregistry/repos.json,registry/repos.schema.jsonAUDIT.mdtests/test_audit.py,tests/test_audit_helpers.py,tests/test_audit_size.py,tests/test_fidelity_text.py,tests/test_spec_validate.pyOut of bounds for this group:
.agents/skills/*(no skill text changes in this group),GOVERNANCE.md,.github/workflows/*and.github/actions/*(open PR #3801).Scope:
developonly. The feature pull request carriesCloses on promotion:for each issue it fully fixes.Date an Anchored intentRef by Its Section and Let a driftNote Acknowl…