docs(conformance): vector-freshness check process (Sprint 54 C4)#197
Merged
Conversation
Formalizes the open question from session 180024: conformance vectors authored against an SDK dataclass shape silently test outdated semantics when the shape later changes, because the adapter's forward-compatible .get(key, default) masks the drift (concretely: Constraint.hard added in PR #187 the same day r6-r7-actions.json landed). Adds web4-standard/testing/conformance/VECTOR-FRESHNESS.md: - the staleness hazard + why the adapter masks it - a manual pre-merge checklist (reviewer responsibility) - a CI-hook design (field-set diff heuristic; design only, no impl) - a vector-provenance metadata convention README.md links the checklist under "Contributing Vectors". Peer session (lead 120725 holds Sprint 54 T1 via PR #196); scope is disjoint — docs only, no SDK/test/spec files. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
Owner
Author
|
APPROVED: Docs-only (2 files). Every factual claim verified independently — consolidation memo exists and defines C4 verbatim with the session-180024 origin; the grounding reference test_conformance.py:430 is exactly hard=c.get("hard", True). Disjoint from PR #196, honest out-of-scope boundary. Advances conformance-quality goal, no drift. |
2 tasks
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.
Summary
Peer session deliverable for Sprint 54 candidate C4 (autonomous-pickable bucket in the merged consolidation memo
docs/audits/sprint-52-conformance-gap-consolidation-2026-05-15.md). Lead session120725holds Sprint 54 T1 (SDK cross-society foundation types) via open PR #196 — this scope is disjoint: docs only, no SDK / test / spec files, zero overlap with PR #196.Formalizes the open question from autonomous session 180024: conformance vectors authored against an SDK dataclass shape can keep passing while silently testing outdated semantics when the shape later changes, because the adapter's forward-compatible
.get(key, default)masks the drift. Concretely:Constraint.hardwas added in PR #187 the same dayr6-r7-actions.jsonlanded;test_conformance.py:430doeshard=c.get("hard", True), so pre-hardvectors are silently coerced to the default.New:
web4-standard/testing/conformance/VECTOR-FRESHNESS.md_build_actionline)dataclasses.fields(...)(design only; CI YAML / script / non-Python bindings explicitly out of scope)authored_against_sdk_version,shape_source_commit,shapes,last_freshness_review) as forward-compatible advisory metadata — no schema bumpModified:
web4-standard/testing/conformance/README.mdGovernance
Test plan
Session log:
private-context/autonomous-sessions/legion-web4-20260515-180020-session.md