Home Contact
Universal Substratev1.4
/
For agents Markdown

46. Common casework, decision, notice, appeal, and remedy runtime

Title conflicts, insurance claims, moderation, market integrity, incidents, privacy complaints, safety reviews, and transfer disputes share one append-only case kernel. Domain packs add local terminology and deadlines, but they MUST NOT replace the common…

Concept & directionLNK

Title conflicts, insurance claims, moderation, market integrity, incidents, privacy complaints, safety reviews, and transfer disputes share one append-only case kernel. Domain packs add local terminology and deadlines, but they MUST NOT replace the common evidence, authority, notice, appeal, remedy, and accountability boundaries.

#46.1 Append-only case kernel

A CaseFile names the case kind, subjects, participants, initiating records, policy and jurisdiction locks, confidentiality policy, assigned team, accountable principal, reviewer requirements, priority, target dates, and initial state. Each CaseTransition supplies the expected case sequence, from-state, to-state, trigger, actor, authority assignment, evidence or decision references, reason codes, and occurrence time.

Case state is a projection over transitions. Evidence, decisions, notices, appeals, and remedies append. Closing, reopening, correcting, vacating, or remanding a case never deletes the earlier state.

#46.2 Parties, representatives, and confidentiality

Case participants have explicit roles such as reporter, subject, claimant, respondent, victim, witness, representative, reviewer, decider, regulator, or observer. Representation authority is attributed and time-bound. Confidentiality is field- and artifact-specific; membership in a case does not imply access to every submission, reporter identity, protected signal, minor-associated record, or privileged material.

#46.3 Evidence submission and disclosure

A CaseEvidenceSubmission binds submitter, represented party, artifacts, propositions, custody references, disclosure class, restrictions, submission time, admission disposition, and challenges. The system distinguishes submitted, admitted, excluded, disputed, unavailable, and withdrawn-for-use evidence without erasing bytes held for audit or legal retention.

Disclosure creates a receipt naming recipient, purpose, exact fields/artifacts, policy decision, redactions, duties, and expiry. Evidence made available for one case purpose MUST NOT silently enter advertising, training, public profiles, recruitment, or vehicle-agent context.

#46.4 Decision authority and reasoned outcomes

A CaseDecision binds decider, current authority assignment, conflict declarations, candidate outcomes, selected outcome, policy digest, evidence-set digest, findings, reason codes, exact scope, effective time, review time, notice duties, and appeal policy. A high-impact decision MUST have one named accountable human principal even when models triage, summarize, or recommend.

Automated output is evidence or a recommendation unless a domain pack explicitly authorizes an automated low-impact decision. Scores MUST NOT directly impose permanent moderation, title clearance, insurance denial, auction cancellation, participant restriction, or physical-control authority.

#46.5 Notice delivery and deadlines

A CaseNotice binds the exact decision or event, recipient, minimized content artifact, disclosed reason codes, channel, dispatch time, delivery disposition, provider receipts, and response deadline. Delivery status is not inferred from a queued message. Protected reporters, minors, victims, integrity signals, security controls, and private evidence are redacted independently from the existence of the case.

#46.6 Appeals, review independence, and stays

A CaseAppeal references the challenged decision; it never edits it. It records appellant, representative, grounds, evidence, requested outcome, filing time, timeliness decision, reviewer requirements, and state. The selected policy pack declares whether review is de novo or limited, the independence rule, deadlines, available remedies, and whether filing automatically stays the effect.

Review may affirm, modify, vacate, or remand through a new decision. A modified outcome appends new effective scope and transition records while preserving what users could have known before review.

#46.7 Remedies, enforcement, and reopening

A CaseRemedy names remedy kind, targets, required and prohibited actions, effective interval, responsible principal, verification requirements, completion evidence, and status. Restitution, refund, access restoration, content relabeling, profile unfreezing, bid reinstatement, title re-review, repair correction, and data-use remediation remain distinct effects with separate authorization and reconciliation.

Reopening a final case requires a separately authorized decision and reason such as new evidence, procedural defect, fraud, external correction, or failed remedy. It does not move the historical case backward.