Sync Repo-docs-DECISIONS-DOMAIN from project files
@@ -0,0 +1,33 @@
|
||||
<!-- codex-wiki-sync:d19833bd025db47766f8cdf8 -->
|
||||
|
||||
> Mirrored from `/mnt/DATA/git/govoplan-decisions/docs/DECISIONS_DOMAIN.md`.
|
||||
> Origin: `repository`.
|
||||
> Active tasks and changing state belong in Gitea issues; this wiki page is durable project context.
|
||||
|
||||
---
|
||||
# Formal Decisions Domain
|
||||
|
||||
## Ownership And Reconstruction
|
||||
|
||||
Decisions stores immutable formal-outcome revisions. Each outcome retains the
|
||||
responsible human or service actor, represented function/party, effective
|
||||
Mandate and jurisdiction, approvals, fact evidence, legal bases, rule versions,
|
||||
reasoning, operative result, requested and observed effects, delivery,
|
||||
publication, remedy, and review references.
|
||||
|
||||
The ordinary read projection withholds protected reasoning and operative
|
||||
content. A separate sensitive-read permission is required to disclose it.
|
||||
|
||||
## Lifecycle
|
||||
|
||||
Writes use the shared Decision transition matrix and optimistic concurrency.
|
||||
Correction and revocation create linked revisions; they never edit the previous
|
||||
outcome in place. Replaying an identical tenant/decision/revision is idempotent,
|
||||
while a different payload under that revision fails.
|
||||
|
||||
## Recovery
|
||||
|
||||
Database restore is the persistence recovery unit. Requested effects remain
|
||||
separate from observed effects and keep audit/evidence references, allowing an
|
||||
operator to reconcile an outcome whose external effect was uncertain. Domain
|
||||
effect providers retain their own compensation and recovery behavior.
|
||||
Reference in New Issue
Block a user