Skip to content

Build an evidence-linked change-review and decision workflow - #15

Merged
MatthewPaver merged 2 commits into
mainfrom
feat/evidence-desk
Oct 22, 2026
Merged

MatthewPaver merged 2 commits into
mainfrom
feat/evidence-desk

Conversation

@MatthewPaver

@MatthewPaver MatthewPaver commented Oct 22, 2026 •

Copy link
Copy Markdown
Owner

Reviewers currently lose source context while navigating a large readiness result, and unrelated public-record examples block recording a decision. This change introduces a compact finding/source desk and makes supplemental context optional, with explicit used, ignored and not-reviewed dispositions.

The journey now covers supported XER intake, identity/chronology and field-coverage checks, all findings retained behind three priorities, exact activity and relationship evidence, evidence questions, an accountable decision, owned dated conditions, deliberate local draft recovery and an evidence-rich export with SHA-256 input identity. Mobile preserves selection and scroll when returning from evidence. Storage errors preserve the open form.

Validation:

  • Five existing browser suites, including desktop/mobile, parser variants, own-file intake, invalid pairs, chronology/identity/coverage, relationship evidence, draft recovery, storage failure, export and follow-up.
  • Eight existing asset/fixture tests.
  • Full hosted verification passes. Arrow is constrained below 26 for compatibility with the existing NumPy 1 analytics stack.
  • Actual updated workspace capture included in README assets.

Limits: deterministic keyword checks and supported single-project XER fields; no critical-path, entitlement or causation conclusion. Browser storage is local and unsigned. Real client export validation and user trials remain outstanding. No deployment is included in this draft.

@MatthewPaver
MatthewPaver marked this pull request as ready for review October 22, 2026 11:25
@MatthewPaver
MatthewPaver merged commit 65755d4 into main Oct 22, 2026
2 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