OBSERVE
Maintain context across the permitted environment.
System authorityPUBLIC ARCHITECTURE
Domain depth.
Shared understanding.
Controlled action.
Ollandi creates one continuous reasoning plane across infrastructure domains while preserving the operating boundaries, authority, and evidence required for consequential decisions.
THE ARCHITECTURAL IDEA
Specialized intelligence should make the whole environment more understandable, not create another collection of disconnected tools.
01 · DOMAIN INTELLIGENCE
DIPs bring the depth.
Each Domain Intelligence Pack understands a particular operating environment. The ATM DIP interprets estate condition and service exposure. Cloud, Identity, Runtime, Network, Endpoint, and On-premises DIPs contribute their own domain context.
- Purpose-built domain semantics
- Current state and developing change
- Interpreted evidence, not another raw feed
05EVIDENCEContinuous record
04AUTHORITYPolicy and people
03REASONINGContext to consequence
02SHARED STATEInfrastructure relationships
01DIPsDomain intelligence
02 · SHARED INFRASTRUCTURE CONTEXT
Relationships turn observations into consequence.
Ollandi relates events to assets, identities, services, owners, dependencies, policy, and previous conditions. The shared picture updates whenever relevant evidence changes.
ENTITYATM-10442Terminal · Wuse 2
CONDITIONNot dispensingService state changed
DEPENDENCYNetwork availableCommunication confirmed
OBLIGATIONService windowExposure developing
OWNERATM operationsVendor route available
AUTHORITYAssisted responseOperator approval required
03 · COLLECTIVE REASONING
Agreement is useful. Dissent is evidence.
Domain contributions can support, challenge, or refine a developing explanation. Ollandi keeps uncertainty and conflicting evidence visible instead of compressing the situation into a single unqualified answer.
Supporting evidenceRefuting evidenceConfidence and gapsEscalation when unresolved
SUPPORTSREFINESCHALLENGES
ATMService state supports the condition
NetworkCommunication path remains healthy
IdentityNo privileged change observed
PolicyOperator authority required
04 · POLICY AND AUTHORITY
The system knows where it must stop.
05 · CONTINUOUS EVIDENCE
The operating record develops with the event.
Observation, interpretation, competing explanations, policy evaluation, approval, action, and verified outcome remain connected in one chronology.
Explore the evidence model ↗1Observe2Relate3Evaluate4Authorize5Verify