corpus: duplicate invariant entries for operator doctrine with conflicting quotes

[ahuimanu]

Observed

When attempting to recompose AGENTS.md renditions with gz content compose AGENTS.md --consumer claude, the command fails with invariant-floor violations. Multiple corpus entries for the same operator directive cannot coexist as invariant-tier entries with different quote styles.

Exit code 1 output:

Error: Invariant-floor violation: entry 'corpus-prime-directive-ownership-2026-06-13T12:34:39.169495+00:00' text not found verbatim in rendered text. Invariant-tier entries MUST appear unchanged at every setpoint.

Expected

Corpus append-only mechanism should prevent conflicting duplicate entries, OR old entries should be marked withdrawn, OR composition should handle superseded entries gracefully.

Canonical contradiction

Corpus entries marked tier: invariant must ALL appear verbatim in every rendition (ADR-0.0.37 rendition-floor-coherence rule). The corpus currently contains TWO invariant-tier entries for the same "Correction vs enhancement" directive with different quote styles, which makes the invariant rule unsatisfiable — only ONE version can appear in the rendition.

Class of failure

Duplicate corpus entries with different formatting for operator-verbatim canonical directives. The corpus append-only semantics do not prevent creating superseded/conflicting entries with the same textual content but different formatting. When both are marked invariant-tier, recomposition becomes impossible.

Evidence: Conflicting corpus entries

Entry 1 (older, 2026-06-13, with double quotes):

• ID: corpus-prime-directive-ownership-2026-06-13T12:34:39.169495+00:00
• Tier: invariant
• Text: Correction vs enhancement (operator doctrine, verbatim): "discovering that more is needed to fulfill the intent of a feature is not an enhancement, it is a correction."...

Entry 2 (newer, 2026-06-19, with single quotes):

• ID: corpus-operator-doctrine-verbatim-canon-2026-06-19T22:54:45.960384+00:00
• Tier: invariant
• Text: Correction vs enhancement (operator doctrine, verbatim): 'discovering that more is needed to fulfill the intent of a feature is not an enhancement, it is a correction.'...

The newer entry is the canonical version (single quotes), the older should be withdrawn or marked as superseded.

Scope hint (advisory, for routing)

• Diff size: Likely small (corpus entry metadata fix)
• Surfaces touched: .gzkit/corpus/AGENTS.md.jsonl, src/gzkit/ composition logic
• In-flight vs. new feature: in-flight (blocking git-sync after corpus enrichment session 2026-06-19/20)

Related

• GHI ADR-0.0.37: canon->AGENTS.md derivation spine is facade (02/03/21/22 repudiated) #623: ADR-0.0.37 repudiation (broader corpus/rendition verification)
• ADR-0.0.37: canon->rendition derivation spine

[ahuimanu]

Status: still open — gate de-fanged, root defect not fixed

The corpus-duplicate defect this GHI tracks (8 invariant-tier entries re-appended by the 2026-06-19 consolidation under new section IDs, including the quote-style conflict that makes the floor unsatisfiable) is not fixed. An attempt to fix it by manually deleting from the append-only corpus + recomposing renditions was reverted — that path operated the un-designed ADR-0.0.37 corpus→rendition ceremony, which has had no design session (operator ruling).

What landed (commit 2d27a99)

The duplicate defect was blocking git-sync via the rendition_floor_coherence pre-push gate, which fail-closed (exit 3) while its sibling rendition_freshness — enforcing the same repudiated ADR-0.0.37 machinery — was already staged to warn (_FRESHNESS_FAIL_CLOSED=False, OBPI-0.0.41 warn→fail). That posture inconsistency was the immediate blocker.

fix(governance): stage rendition-floor-coherence to warn brings floor-coherence into the same staged-warn posture (_FLOOR_FAIL_CLOSED=False + fail_closed param), with the QC-binding negative control updated to assert fail_closed=True (coupled surface). Drift is now an advisory WARNING; gz check stays green. The flag flips to fail-closed only when the corpus→rendition ceremony is designed and renditions are re-seeded.

Remaining work (keeps this GHI open)

1. The corpus-duplicate entries are still present (reverted to HEAD).
2. The corpus→rendition CMS (ADR-0.0.37) needs a real design session before any corpus mutation or rendition re-seeding ceremony — see GHI ADR-0.0.37: canon->AGENTS.md derivation spine is facade (02/03/21/22 repudiated) #623 (facade repudiation).
3. _FLOOR_FAIL_CLOSED / _FRESHNESS_FAIL_CLOSED flip together only after that ceremony exists.