3AIS / Framework design
Framework design
Four layers, one adapter interface, and no domain logic in the core.
The four layers
Perception parses input, whatever form it arrives in: feeds, documents, images, sensor streams. Cognition turns perception into a decision. Ethics constrains what may be decided and what must be escalated. Execution carries out the approved action and records it.
They are separate on purpose. A system that can see something but cannot be stopped from acting on it is not a system you deploy near infrastructure.
The adapter interface
Every domain package implements the same interface. It declares what data sources it can perceive, what decisions it wants to make and what actions it needs. The core never learns what a traffic light is; the package tells it.
This is what keeps the framework honest. If a feature cannot be expressed through the adapter, it belongs in the domain package, not in the core.
The command center
The reference deployment is a desktop command center: a login window, a main window holding a geospatial view, department widgets and a unified command overlay, all wired through a message bus so any widget can react to anything else without being coupled to it.
Data arrives through an ingestion adapter rather than being hard-wired into the widgets, so swapping a city's feed source is configuration, not a rewrite.