Skip to content

E2 E2: validate governing observation rows before writing - #35

Draft
Cubits11 wants to merge 1 commit into
codex/e2-e4from
codex/e2-e2
Draft

Cubits11 wants to merge 1 commit into
codex/e2-e4from
codex/e2-e2

Conversation

@Cubits11

Copy link
Copy Markdown
Owner

Collector rows previously violated the governing schema and were written without validation. Emit contract types, timestamps and provenance; validate each row against CONTRACT before writing; reject invalid rows with a structured violation list. Preserve unrounded scalar scores and existing event semantics; adapters record rendered input/scorer response hashes without changing scoring. Analyzer remains stdlib-only.

Validation: three baseline core regressions fail; five repaired tests pass. A complete synthetic 1320-item/3960-row collect→validate→analyze replay exits 0 with zero governing violations; E4, all P1–P12 properties, and adapter checks pass. Raw logs: experiments/e2/verification/E2/. Original FT11 reproduces 30 baseline violations; repaired synthetic call conforms and the unattributed original real call hard-refuses with zero writes. The 15-violation single-row reconstruction is explicitly labeled, not claimed as exact host provenance.

Depends on SITE E4 #34 and CONTRACT E1 Cubits11/cc-framework#65. Set E2_CONTRACT_ROOT to the paired CONTRACT revision and use its jsonschema runtime for collection/validation. No real guard run or E2 empirical result is claimed.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant