Skip to content

feat: qualify isolated supplied-content normalization across nine ingress kinds (DSE-718) - #129

Merged
ernestprovo23 merged 19 commits into
mainfrom
codex/dse718-universal-normalization
Nov 14, 2026
Merged

ernestprovo23 merged 19 commits into
mainfrom
codex/dse718-universal-normalization

Conversation

@ernestprovo23

@ernestprovo23 ernestprovo23 commented Nov 14, 2026 •

Copy link
Copy Markdown
Member

Supplied documents and encoded payloads currently bypass the text-only inspection path. DSE-718 adds one Linux-first normalization/extraction profile across all nine supplied ingress kinds, preserving exact ingress hashes and deriving untrusted evidence with labeled provenance. It does not retrieve external content or grant delivery authority.

The standalone, independently hash-locked parser handles the approved text/web/data, RFC822/MIME, ZIP and conservative text-PDF profiles. A fixed immutable local Docker image runs without network, credentials or host-data mounts and with verified filesystem, capability, process, memory, CPU, time and IPC limits. Unsupported/partial/ambiguous inputs and missing controls refuse; there is no in-process fallback. Office/OCR and non-Linux worker execution remain unsupported.

normalize emits evidence and redacted findings. Opt-in guard/inspect --normalizer-image sha256:... share raw/normalized inspection and atomic refusal. Universal mode rejects shadow/recording flags and cannot reuse legacy fail-open branches. Existing default commands retain their earlier contracts.

The interview settled current formats, Linux first, supplied content only, and labeled page/member evidence where exact bytes cannot be proved. Source-map coverage is structural, not a proof of semantic extraction completeness; parser omission/compromise remains documented. Coordinator and worker require the pinned Unicode runtime.

Validation at final source c872932b5f658dfd937332b843dff50e3264c372:

  • Linux CI: 272 passed, no skips, including every 10-format × 9-ingress pair, actual isolation/resource/cleanup faults, raw/live/offline inspection and CLI redaction. Independent builder: the same 272 tests passed with the final protected image.
  • Deterministic normalization properties: 2 passed with seed 0; independent parser dependency audit found no known vulnerabilities.
  • Final builder image sha256:db35bc1ae81bdc94ed8e849421456fb1857bed0541968ed38970825fb4f105fb: all ten packaged source/license hashes match; all three dependency wheel license sets retained. Eight actual duplicate-MIME refusal canaries and valid MIME/CommonMark positives passed.
  • Cleanup assertions verify the invocation's own exact container name, allowing unrelated consumers on a shared host. Two simultaneous 23-test sandbox runs passed.
  • Independent CSO APPROVE final source/test and qualified artifact at this exact commit; its final green-generic-CI condition is satisfied.
  • Generic regression CI: 1,661 passed at 88.80% coverage; 119 runtime/image-specific skips are covered by the separate mandatory Linux job. Existing deterministic fuzz: 55 passed, one pinned-runtime skip; dedicated normalization fuzz: 2 passed. All PR checks green.
  • v2.3.0 wheel and source archive build successfully; the source archive includes the worker build context and dependency notices.

Ernest explicitly approved this security implementation and the full delivery lifecycle in the current authenticated chat. This prepares the normal v2.3.0 release through the existing signed-artifact/OIDC publishing workflow. No new external service, spend, credentials, host security-policy changes, fallback-token retirement or whole-ATK conformance claim.

CI: https://github.com/DataScience-EngineeringExperts/mcp-warden/actions/runs/43604913296
Normalization qualification: https://github.com/DataScience-EngineeringExperts/mcp-warden/actions/runs/43604913380
Ticket: https://linear.app/dseofficial/issue/DSE-718
Contract: docs/CONTENT_NORMALIZATION.md

@ernestprovo23
ernestprovo23 merged commit 8c8b59c into main Nov 14, 2026
16 checks passed
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