Dartmouth
A system that stays yours.
Evidence connects the policy, its approved interpretation and the resulting action.
Illustrative workflow · Synthetic example
Retain the policy clause, approved rule version and inputs used.
Record the reviewer or accountable role, the outcome and the reason.
Keep records accessible alongside the configuration and operating context needed to inspect and improve the capability.
Select a stage to inspect its detail.
Ownership is not a launch date. It is custody of the working system, an inspectable record of decisions, and the understanding to operate and improve it. Each approved change builds on what the institution has already established.
The following register and its detail views contain synthetic examples only.
Illustrative workflow · Synthetic example
On smaller screens, scroll the table horizontally to inspect every column.
| Record ID | Source / version | Decision or event | Accountable role | State | Record link |
|---|---|---|---|---|---|
| DR-001Illustrative workflow | Illustrative IPS §4.1 / v3 | Interpret concentration limit | Policy owner | Reviewed | Inspect example ↗ |
| DR-002Illustrative workflow | Illustrative rule / v3 | Validate single-issuer check | Risk reviewer | Approved | Inspect example ↗ |
| DR-003Illustrative workflow | Illustrative assessment / v1 | Escalate missing assessment | Compliance owner | Human review | Inspect example ↗ |
Illustrative workflow · Synthetic example
The policy owner reviews an interpretation of a synthetic single-issuer concentration clause. The review records what the limit measures, where it applies and which ambiguity still needs resolution. Reviewed means the interpretation was examined; it does not itself grant deployment authority.
Synthetic proposed concentration: 3.2%.
Interpretation reviewed; implementation remains subject to rule validation.
Synthetic and unsigned. These records illustrate a presentation schema, not a live evidence register or completed client approval.
Back to the registerIllustrative workflow · Synthetic example
A synthetic rule checks exposure against the illustrative 4.0% ceiling. Boundary cases at, below and above the ceiling are inspected, together with missing inputs. Approved describes this example’s rule-validation state, not a certification or permission for every proposed action.
Synthetic test cases: 3.2%, 4.0%, 4.1%, and an absent assessment.
Illustrative rule validation approved within its stated scope.
Synthetic and unsigned. These records illustrate a presentation schema, not a live evidence register or completed client approval.
Back to the registerIllustrative workflow · Synthetic example
The proposed action is inside the numerical ceiling but its required assessment is absent. The workflow withholds automated permission and routes the missing context to the compliance owner. A person must resolve the assessment before the action can be reconsidered.
Synthetic concentration: 3.2%; required assessment missing.
Human review required; no automated permission granted.
Synthetic and unsigned. These records illustrate a presentation schema, not a live evidence register or completed client approval.
Back to the registerAgree the artifacts, responsible roles and operating knowledge that make transfer real.
Illustrative workflow · Synthetic example
This is an illustrative delivery framework, not a claim that a specific client has completed these actions. Each item is a delivery requirement; none indicates a completed sign-off.
Authoritative sources and responsible policy owners documented.
Handover artifact: Source register and custody location
Approved rules, versions, and escalation paths catalogued.
Handover artifact: Rule catalogue and approval history
Test, shadow-run, and acceptance evidence transferred.
Handover artifact: Test pack and acceptance record
Configuration, code, deployment instructions, and runbook delivered as agreed.
Handover artifact: Agreed repository and operating runbook
Roles, access boundaries, failure recovery, and change-control owners assigned.
Handover artifact: Access matrix and recovery procedure
Ongoing review and governed rule-update process established.
Handover artifact: Review cadence and version approval process
Delivery requirements · No completed sign-offs.
Reviewed outcomes and expert corrections inform the next approved version.
Review the retained decision context and where the current system falls short.
Document the correction, its policy basis and the affected rules or configuration.
Test the change and secure owner approval before releasing a new version.
Select a stage to inspect its detail.
Learning does not mean unsupervised rule mutation. The written source stays authoritative, earlier versions remain traceable, and new authority passes through change control.
Inspect the distinct output architectures, proposals and original documents.