NodetteHQ/PureXML
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Production readiness for IDE use #3

New Issue
Open
opened 2026-07-05 03:44:52 +00:00 by Mihaela · 0 comments
Mihaela commented 2026-07-05 03:44:52 +00:00 (Migrated from codeberg.org)
Copy Link

Status (2026-07-05)

Active. Recreated on Codeberg after the original epic went down with the deleted GitHub tracker; this is the pin issue for the path to 1.0.

The bar

docs/production-readiness.md defines four stoppers, each of which blocks production on its own. Current state per the enforced ratchet in Tests/XSTSSuiteTests.swift (v0.4.8):

  1. Rejecting valid input: met. Valid schemas rejected 0, valid instances rejected 0, on the full 2006-11-06 XSTS archive, corroborated by the libxml2 differentials.
  2. Silently accepting faulty input: not at 0. Invalid schemas accepted 8, invalid instances accepted 4. Tracked by the two gate issues.
  3. Uncharacterized correctness: the schema-compile determinism differential, the generated facet-value differential, and the generated instance-validation differential against libxml2 all exist and run opt-in; remaining gap is real-world corpora beyond XSTS.
  4. Interactive safety: located diagnostics shipped; the graph-structured-stack content matcher now has a proven, count-asserted linear bound. Remaining gap: proven bounds for the rest of the pipeline, not caps.

Exit criteria

All four stoppers cleared and the gates at zero, per docs/production-readiness.md and the milestone table in docs/roadmap.md.

## Status (2026-07-05) Active. Recreated on Codeberg after the original epic went down with the deleted GitHub tracker; this is the pin issue for the path to 1.0. ## The bar `docs/production-readiness.md` defines four stoppers, each of which blocks production on its own. Current state per the enforced ratchet in `Tests/XSTSSuiteTests.swift` (v0.4.8): 1. Rejecting valid input: **met**. Valid schemas rejected 0, valid instances rejected 0, on the full 2006-11-06 XSTS archive, corroborated by the libxml2 differentials. 2. Silently accepting faulty input: **not at 0**. Invalid schemas accepted 8, invalid instances accepted 4. Tracked by the two gate issues. 3. Uncharacterized correctness: the schema-compile determinism differential, the generated facet-value differential, and the generated instance-validation differential against libxml2 all exist and run opt-in; remaining gap is real-world corpora beyond XSTS. 4. Interactive safety: located diagnostics shipped; the graph-structured-stack content matcher now has a proven, count-asserted linear bound. Remaining gap: proven bounds for the rest of the pipeline, not caps. ## Exit criteria All four stoppers cleared and the gates at zero, per `docs/production-readiness.md` and the milestone table in `docs/roadmap.md`.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: NodetteHQ/PureXML#3
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?