Understand the system.
Start with Sven’s purpose, explore the architecture and follow the research over time.
Find a guide or component
Search the titles and descriptions below by name or topic.
No guide matches these words. Try a component name or a different topic.
Overview
The purpose of Sven and the idea of a continuing machine-first intelligence system.
How it fitsArchitecture
The relationships between semantic continuity, authority, execution and communication.
ExploreComponents
The responsibility of each named component and the boundaries between them.
Follow the workDevelopment
Selected dated records, with experiment scope and historical context preserved.
AvailabilityReleases
What this public site offers and how to discuss a specific use case.
Find your wayAccess & contact
Public information, related sites and the route to contact 47Network.
From architecture to a taskRhapsode workflow guide
Illustrative draft, publication and research journeys, with a clear action boundary and a checkable result.
Ownership and accessDeployment guide
Plan a Rhapsode integration around your environment, data and support needs.
Component · Governed executionRhapsode
The execution layer that connects work with capabilities while preserving authority, evidence and continuation.
Component · Authority & evidenceArcheion
The authority and evidence layer: identity, policy, permission and the basis for consequential decisions.
Component · Semantic continuityEnnoion
Semantic continuity for evidence, concepts, relationships and their changing meaning over time.
Component · CommunicationSymploke
Communication between the working parts of Sven, carrying messages and relevant work state.
Component · Documented delivery roleKeryx
The documented role for outward delivery and attributable receipts within Sven’s architecture.
Component · Documented interaction rolePhaneum
The documented role for human-facing continuity across Sven’s devices and interaction surfaces.
Start from the intended use.
These guides introduce the architecture and research. For implementation guidance, start with the component and environment you have in mind.
For a concrete project, contact 47Network with the problem and environment you have in mind.