A title change split one case into two
I found the problem while testing HR Mission Control. A proposed law changed names after it passed the House. The earlier version already had a decision attached: keep watching it.
When the new title arrived, HRMC treated it as a separate issue. The screen showed the same law twice. One record was being monitored; the other looked undecided. An HR team could repeat the review, assign two owners, or send the same issue down different paths.
The decision has to follow the case
I changed the system so the record could preserve alternate titles while keeping one case identity. The source label was allowed to change. The review, decision, owner, and history stayed attached to the underlying issue.
Then I reran the workflow through source review, packet review, legal approval, implementation, and audit history. In the small local test I published, HRMC found all ten expected law signals, handled six harder workflow scenarios, and completed a five-minute stability run without a failure. Those results describe that test. They are not evidence of complete legal coverage or production readiness.
If a source changes its name, the team should not lose the decision it already made.
What belongs in the receipt
- Source — the canonical source, title, version, date, and any identifiers or aliases
- Case identity — the stable record that connects renamed or updated material
- Facts and gaps — what was supported, what conflicted, and what remained unknown
- Challenge — the questions, objections, and checks raised before the decision
- Reviewer and decision — who owned the judgment, what they decided, and when
- Correction — what changed from the AI-prepared draft and whether the change survived
- Approved action — the exact next step a person authorized
- Owner and timing — who took the action and when it was due
- Verification — the evidence that the approved action happened or the reason it did not
An activity log is useful and still incomplete
A log can show that a page was fetched, a draft was generated, or a button was clicked. It may not show whether the right source was used, which facts were missing, what the reviewer corrected, or why a person approved the final action.
The receipt connects those pieces around the decision. It should be readable by an HR, legal, privacy, security, or business owner who was not standing beside the original operator. If that person has to reconstruct the meaning from raw events, the workflow has kept activity and lost accountability.