A continuing system.
Distinct responsibilities.
Sven’s architecture connects identity, meaning and work over time. Its components have separate responsibilities, so that changes in models, hardware or execution do not have to redefine the whole system.
Four central responsibilities
| Component | Responsibility | Why it matters |
|---|---|---|
| Ennoion | Semantic continuity | Connect evidence, concepts and their history while preserving uncertainty and changes in meaning. |
| Archeion | Authority and evidence | Keep permissions, policy and evidence attached to consequential decisions. |
| Rhapsode | Governed execution | Connect a task with the appropriate capabilities and return attributable results. |
| Symploke | Communication | Carry messages and work state between the system’s working parts. |
From understanding to action
Permission stays attached to the work.
In this design, semantic context informs a task, authority determines what may happen, execution performs the permitted work, and communication carries the relevant state.
Being able to request an action does not grant permission to perform it. A returned result must still be understood in the context of the action and the evidence behind it.
Delivery & interaction
Connecting the system to the outside.
Continue the conversation
Work with 47Network.
For research, technical collaboration or a project related to Sven, tell us what you are working on.
Contact 47Network