Skip to content

feat(assurance): nine-promise foundation (draft test candidate) - #426

Draft
RAMBULLS wants to merge 5 commits into
mainfrom
assurance/nine-promises-20261111
Draft

RAMBULLS wants to merge 5 commits into
mainfrom
assurance/nine-promises-20261111

Conversation

@RAMBULLS

@RAMBULLS RAMBULLS commented Nov 11, 2026 •

Copy link
Copy Markdown
Owner

Draft-only nine-promise assurance foundation, native-result diagnostics and search repair. No merge or deployment until required exact-head checks and independent final acceptance pass.

Current head: 9baece9. Exact tree: 75218d0ccfdc44407db364e289bb0fd2bed7d2f7. Main base: 8b47ab6.

This change rebuilds assurance work from the verified published baseline fc4c21b; it is not recovery of the missing unpublished layer. Sixteen cumulative paths add actual native event diagnostics, paired TAP reporters, guarded scripts, bounded affected checks, retained CI diagnostics, stronger search tests and corresponding documentation.

The nine-file increment corrects the real-reporter abort fixture using an Error reason and native cancellation event, preserving the strict cancellation expectation. Reports retain native failure_type and summary success is checked against actual subprocess exit status. No classifier relaxation grants a pass.

Broad MFA discovery preserves IA-2(1) and IA-5 and adds IA-2(2), within the unchanged top-five budget. It preserves query qualifiers and facet restrictions, retains the strongest spelling match, and leaves exact-ID lookup intact. These are editorial discovery targets, not applicability or compliance conclusions. Source review used NIST SP 800-53 revision 5 IA-2 and IA-5.

Rendered browser tests exercise every reviewed query's complete expected set, canonical record links, unique identities, intentional zero results, and separate index-manifest/shard failure and user retry. Existing record-artifact tests now have accurate titles. The stronger native and browser sources are referenced without claiming they ran.

Separate AI static review covered the cumulative thirteen-path candidate through local 9fb3b9aa90f51c383502ce2cb38610d91770c4f1 (/root/assurance_independent_review), native abort correction (/root/native_abort_review), and exact four-path rendered-search increment e8280a0c684dbd281010d3746d91645bc17de049 (/root/assurance_coverage_review). Reviewers executed no candidate tests. The uploaded tree matches that final local checkpoint; commit metadata differs. Cumulative patch SHA-256: 48e53cb64be3f1beaee3ea88da73f53abacc9c198984b6c11c013877741e878b. Local hygiene passed. Hosted Linux/Windows, recall/regression/latency, CI/Security, provider readback and independent final review remain required.

This is not full nine-promise acceptance. Exact reviewed assertion inventory, browser/job/shard/provider binding, behavioral coverage and actual-domain evidence remain incomplete. Native reports record requested head and checkout as claims requiring independent verification; annotations and green jobs cannot alone certify coverage. Source-meaning holds and final integration/live acceptance remain required. AI review is not practitioner certification or corpus-wide semantic review.

The previous head's CI showed native abort and complete MFA recall failures, plus Ubuntu DNS failures while installing browser dependencies. Those browser jobs did not run; infrastructure failure is not a passing result. Security, immutable build, push audit and Lighthouse budgets passed for that previous head only.

Recovery checkpoints are preserved in Library with version history. CSS #428 remains held and separate. DISA archive/native reconciliation and AC-2 speed remain unresolved. Responsible AI stays quarantined.

Equivalent reviewed tree of local 837a91aa652da658c83dcfda5acb6e057deb8520. Hosted checks pending; no release acceptance.
…recall

Add reviewed rendered search recall, canonical links and index recovery checks. Native and browser evidence remain incomplete until hosted validation and independent execution binding.

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