Skip to content

feat(qualification): capture local institutional judgment cases - #111

Closed
abrichr wants to merge 6 commits into
mainfrom
codex/desktop-judgment-case-capture
Closed

feat(qualification): capture local institutional judgment cases#111
abrichr wants to merge 6 commits into
mainfrom
codex/desktop-judgment-case-capture

Conversation

@abrichr

@abrichr abrichr commented Aug 8, 2026

Copy link
Copy Markdown
Member

Summary

Adds the optional Desktop qualification path for reviewed institutional-judgment cases.

  • Captures reviewed typed facts, source provenance, a local evidence inventory, optional local review note, contrast cases, and the three disposition states.
  • Uses only Flow-owned local contracts and the qualification.set_judgment_cases capability.
  • Preserves direct decision authoring as the fast path.
  • Does not create a runtime decision, a signer, a policy inference path, or a VERIFIED outcome.

Dependency

This draft depends on Desktop PR #110 (branch codex/desktop-business-decision-authoring-20260808) and Flow branch codex/judgment-case-qualification. Rebase onto fresh main after #110 merges. Then update the embedded Flow pin after the Flow case contract releases.

Validation

  • Focused UI tests: JudgmentCaseCapture, BusinessDecisionAuthoring, Qualification
  • Production UI build
  • Python compile: engine/qualification.py and engine/dispatch.py

@abrichr

abrichr commented Aug 8, 2026

Copy link
Copy Markdown
Member Author

Updated at bf68246. The Desktop now creates an atomic pair of reciprocal automatic-rule cases. The protected integration test proves that Desktop sends both cases, binds their reciprocal contrast IDs, and uses the Flow-owned judgment-case command. Full UI suite: 75 tests pass. Production build and Python compile pass. Please re-review this exact head.

@abrichr
abrichr deleted the branch main August 8, 2026 20:40
Base automatically changed from codex/desktop-business-decision-authoring-20260808 to main August 8, 2026 20:40
@abrichr abrichr closed this Aug 8, 2026
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