Expose decision filing and search sources
This commit is contained in:
@@ -29,3 +29,21 @@ 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.
|
||||
|
||||
## Records Filing
|
||||
|
||||
Decisions publishes the optional `records.source.decisions` capability. It
|
||||
resolves only an exact immutable `decision_revision` in the acting tenant and
|
||||
requires both ordinary and protected Decision read authority because the
|
||||
filing digest represents the complete formal outcome, including protected
|
||||
reasoning and operative content. Records stores a bounded label, lifecycle
|
||||
metadata, and SHA-256-bound source reference; Decisions remains authoritative
|
||||
and current access is checked again whenever the source is reconstructed.
|
||||
|
||||
## Search
|
||||
|
||||
When Search is enabled, `decisions.decisions` indexes only bounded Decision
|
||||
metadata, subject identifiers, legal-basis references, effect references, and
|
||||
the linked Case route. Operative results, reasoning, and conditions are never
|
||||
copied into the search index. Every result is tenant-bound and rechecked against
|
||||
the current Decision read permission before disclosure.
|
||||
|
||||
Reference in New Issue
Block a user