SI & SeniorCRE Intelligence
How do operators prevent SI from acting on bad data?
Last reviewed
Direct answer
Prevent it with structure rather than hope. SI should only act on governed values. Unresolved conflicts and missing lineage should block or downgrade actions. Grants should limit what the SI may execute, and higher-impact actions should require a person’s authorization. Each action should be recorded with the inputs it used.
Why this happens
Asking a model to "be careful" is not a control. Permissions and input rules are.
Recording inputs alongside actions makes problems traceable and fixable.
Hypothetical example: an si agent asked to schedule staff
EHR census
92
Includes a bed hold.
Accounting census
90
Billable residents only.
SI agent
Chooses 92 with high confidence
Confidence reflects the model, not the operator’s authority.
- Evidence
- Disagreement
- Authority
- Operator-Controlled Operating Record
- Intelligence
- Execution
Illustrative figures. Coherence before Intelligence.
The model’s confidence says nothing about which census the operator has approved for staffing.
The governance question
Coherence before Intelligence. SI should reason from an operator-controlled operating record whose authority has already been established by the operator, with execution confined to explicit grants. Model confidence never creates organizational authority.
Evidence → Disagreement → Authority → Operator-Controlled Operating Record → SeniorCRE Intelligence → Execution
What good operating infrastructure should do
- SI reads governed values, not raw conflicting sources.
- Unresolved disagreements are visible to the SI and to people.
- Explicit grants for what SI may read, recommend and execute.
- Human determination for anything outside approved rules.
- A record linking each SI recommendation to its governed inputs.
SeniorCRE perspective
SeniorCRE Intelligence is designed to sit downstream of the Operator-Controlled Operating Record: it reasons from numbers whose authority the operator has established and acts only within authority already granted. It never decides which number governs. Status: the Operator-Controlled Operating Record is designed and not yet implemented in any community. Current capability states and production-entry gates are published in the Evidence Record at the Trust Center; nothing here should be read as a production result.
