Preserve the decision, not just the telemetry.
Logs can show that something happened. Vidamonti preserves why the institution allowed it to happen: recommendation state, policy, evidence, authority, human action, exception state, authorization, and final outcome.
Reconstructable path
Preserve the material decision packet, not disconnected events.
Vidamonti captures the recommendation, control state, human actions, authorization, and outcome while preserving the relationships that explain how the decision moved. The record becomes an operational product output rather than a manual reconstruction exercise after the fact.
Recommendation
Capture the proposed action, relevant context, source or model identifier where appropriate, and when it entered the controlled workflow.
Decision context
Source identifier
Timestamp
Control state
Preserve applicable policy outcomes, evidence status, authority path, review requirement, escalation state, and exceptions.
Evidence status
Authority path
Exception state
Human action and outcome
Capture approval, rejection, modification, request for evidence, escalation, override, hold, rationale, and downstream outcome where supported.
Rationale
Authorized state
Outcome link
Keep the decision basis attached to chronology.
A useful decision record connects timestamps to the policy, evidence, authority, reviewer actions, exceptions, and state transitions that made those events meaningful. That context supports later assurance, incident analysis, acceptance, review, and operational learning where supported.
The record needs enough context to make policy, evidence, authority, review, and exceptions intelligible after the fact.
Context and source captured.
Applicable rule and material basis preserved.
Reason and authority path captured.
Final state advanced within boundary.
Separate telemetry from institutional decision evidence.
Observability and logging systems remain useful for operations and debugging, but by themselves they do not preserve the policy, evidence, authority, human action, and exception relationships required to reconstruct an institutional decision.
Chronology without enough decision context.
- System events and timestamps
- Technical traces
- Component activity
- Useful for operations and debugging
Material decision context and relationships.
- Recommendation and operating context
- Policy and evidence state
- Authority and human action
- Exceptions, rationale, and authorized outcome
Govern retention, access, export, and sensitive fields.
Record retention, export, reviewer access, and sensitive data handling remain governed by the institution's actual policies, deployment model, and configured controls.