Durable execution
Work that can resume.
Executions retain their state, steps and outcomes, so work can be followed and resumed under control after an interruption.
Skyeos Core / Technology
Built deeper.
Think further.
Business knowledge, access and execution come together. AI moves work forward while people retain oversight and decision-making.
Explore the architecture
Intelligence beneath the experience
A model thinks.
A system delivers.
Every useful AI application depends on concrete responsibilities. This is the technical foundation of Skyeos.
Skyeos Core / Intelligence in motion
Design principle · Neuro-symbolic AI
The flexibility of AI.
The control of your product rules.
Generative AI makes product knowledge accessible. Explicit rules govern calculations and checks. In a connected application, this gives NEXUS a defined role in the product process.
- Generative AI
Understand the request.
NEXUS helps explore a question, interpret permitted information and prepare a next step.
- Deterministic product logic
Validate the choices.
Configured product rules determine which combinations fit and how quantities and prices are calculated.
- Human oversight
Keep people in control.
Your team manages the product knowledge. Permissions and agreed approvals determine which changes and actions go ahead.
What does neuro-symbolic mean?
Neuro-symbolic AI combines neural models, such as language models, with explicit knowledge and logical rules. At Skyeos, it describes the design principle behind the collaboration between AI and product logic. What NEXUS can access or act on is configured for each application.
Deterministic means the same inputs and rule version produce the same result. The quality of that result still depends on the source data and rules. Testing and expert review therefore belong within product management.
Try visual product management
The public demo illustrates product management with fictional example data.
01 / The engineering foundation.
Trust is a design decision.
From an initial proposal to an external action: authority, progress and outcome each have their own place.
Human oversight
Decisions, explicitly recorded.
Where permission is required, the proposed action is presented for review. Approval remains bound to the content of that action.
Access control
Access defines what is possible.
Identity, roles and permissions define which data and actions are available. The model does not grant itself those rights.
Reviewable engineering
Changes that can be reviewed.
Version control, automated checks and maintained architecture documentation make changes traceable and reviewable.
A closer look at technical execution
Execution state and checkpoints preserve progress. An append-only event history records steps and outcomes. Retries follow controlled rules; idempotency limits repeated processing where the execution path supports it. An uncertain external outcome requires review before resuming. Model proposals, authority and actual execution remain separate steps.
Engineering discipline
Built to evolve. Built for review.
Your organisation keeps building on its platform. We connect software changes to consistent checks, versions and documentation, so quality remains reviewable with every new release.
- 01
Automated tests
Critical behaviour under review.
An extensive test suite checks access boundaries, approvals and execution behaviour, among other areas. Changes are checked against behaviour that already works.
- 02
TypeScript · strict
Errors visible earlier.
Strict type checking examines how data and functions fit together during development and build. Interface changes become visible wherever other code depends on them.
- 03
Architecture parity
The design moves with the code.
Code changes must be accompanied by architecture documentation. A separate check verifies that the generated architecture overview is up to date.
- 04
Continuous integration
Consistent checks. Every change.
Type checking, linting, tests, architecture checks and the application build run together in CI. Their results remain tied to the software version being assessed.
These checks make development and maintenance easier to assess. Acceptance in the customer environment remains part of each implementation.
02 / The architecture of Skyeos Core
Four pillars.
One connected system.
Four architecture pillars connect business knowledge, customer boundaries, improvement and accountability.
01
Memory Fabric
Knowledge with provenance.
The memory design connects current working context, past events, business facts and approved procedures. Sources, ownership and validity keep knowledge traceable. New lessons pass through review before they influence actions.
A closer look at the design
Four kinds of context
Current working context, episodic events, semantic business facts and procedural ways of working each have a distinct role in the memory design.
From source to usable knowledge
Provenance, access and validity determine which knowledge an execution may use. A new lesson starts as a proposal for review.
02
Customer Cells
A defined boundary around your organisation.
The cell model is designed to keep data, memory, access and execution within one customer boundary. Central software development combines with scoped operations, recovery and data management. The physical setup follows the requirements of the implementation.
A closer look at the design
One coherent customer boundary
The target architecture treats identity, data, memory and execution as parts of the same bounded environment.
Management across the lifecycle
Recovery, retention, export and deletion belong in the design of that boundary. The technical and physical setup is defined for each implementation.
03
Controlled Improvement
Improvements that must earn their place.
The proposed improvement loop turns signals from work into testable proposals. Evaluation and a human decision precede a controlled trial. Versions, measured results and a rollback path keep changes governable.
A closer look at the design
A proposal is not yet a change
The design separates observation, proposals, evaluation and decisions. A candidate reaches a controlled trial only after review.
Measure and retain a way back
Results are tied to a version. A previous version and explicit stopping criteria belong in the proposed improvement process.
04
Causal Execution Ledger
From trigger to recorded outcome.
Existing execution ledgers provide the foundation for a connected record of triggers, decisions, approvals and outcomes. The target architecture links these events to make work easier to reconstruct. An uncertain outcome calls for review before retrying.
A closer look at the design
Events in context
In the target architecture, triggers, decisions, approvals and outcomes should refer to one another so their relationship can be examined.
Reconstruction without repetition
The design distinguishes rebuilding a work history from repeating an external action.
03 / Your environment
Your data.
Defined boundaries.
Every customer gets their own hosting environment and database. Skyeos Core provides intelligence through agreed connections. Roles, source selection and permitted processing determine which context a model or agent can use.
Processing locations, model providers, retention and recovery follow the implementation requirements. Having a dedicated database does not by itself mean every inference occurs in that same environment.
Core and your customer environment ↗04 / Agentic internet
A business that
AI can discover.
New customer journeys can start beyond your own website. Imagine a buyer asking an AI assistant to find a suitable product. We design product knowledge, rules and permitted actions as connected, readable building blocks.
This is a development direction for the vertical digital architecture. We explicitly define which external systems may search, configure or prepare a request. A request becomes an order only through the agreed checks and approval.
From strategy to your architecture ↗Security & AI governance
Technical safeguards. Clear accountability.
Information security and responsible AI require technology, working practices and independent assessment. We make the safeguards and the status of external review explicit.
ISO/IEC 27001
Application in progress
Information security management
The application for information security management system certification is in progress. No certificate has been issued yet.
About the ISO/IEC 27001 standardSOC 2
Application in progress
Independent attestation
The request for an independent SOC 2 examination of the agreed controls is in progress. A completed SOC 2 report is not yet available.
About SOC examinations and reportingEU AI Act
Human oversight is part of the design.
The EU AI Act ties obligations to how AI is used and an organisation's role. Skyeos supports responsible use through explicit authority, human review and traceable execution.
The European framework for AIPeople retain decision-making authority
Where approval is required, the proposal, human decision and execution remain separate steps. A model cannot grant itself additional authority.
Permissions define the available context
Identity, roles and permitted sources determine which business data and actions are available to an execution.
Execution leaves a trace
Recorded state, events and outcomes support investigation and review. An uncertain external outcome requires a check before retrying.
Each use case determines the assessment
Purpose, risks, data use and responsibilities are defined per implementation. The role, risk classification and applicable obligations determine the additional safeguards and assessment required.
A formal EU AI Act conformity assessment has not yet been completed. This describes the concrete safeguards and the assessment needed for each use case.