Partners

Structure lets your team build faster and change a running system with confidence.

Your team declares each system in full before it runs. daedal resolves the whole composition before anything runs, and its plan shows what a change will do to every step before your team applies it. Where the system runs on aidion, aidion records each consequential action as it happens.

What you gain: Speed and stability. A component declared once composes into any system that needs it. Your team can rebuild any earlier version of a system from its composition.
What you keep: Your clients, your products and your margin. Operative supports your engineers, and your clients contract with you.
Structure for the systems you run: We help engineering teams bring structure to the systems they already run: every part declared, the whole compiled before it runs and each version rebuilt exactly from its declaration. daedal composes and builds onto the substrates the team already runs: containers, schedulers and hosts.
Systems on aidion: aidion is an excellent substrate for many systems. It resumes an interrupted workflow from its last completed step, carries authority in capability tokens, holds each organisation's keys under a key of that organisation's own and records each consequential action in an audit chain. We support teams building on daedal and aidion together.
What you can promise: To rebuild a system, your team has daedal apply the system's declaration. On aidion, the system's audit chain records each consequential action, and a change to any recorded action shows in the chain.

Work

The engines meet demanding requirements with strong guarantees. Regulated work is one place such requirements arise.

Each system is settled in its structure before it runs, any earlier version can be rebuilt exactly as it was declared, and on aidion its authority and actions are on record. Those guarantees suit work where a result has to hold up long after it is produced.

Take a report prepared under professional liability. It needs evidence gathered, gaps followed up, figures computed and checked, sections drafted and the file assembled. The system does that work, and the expert decides the two or three points that need judgment with every input traced to its source.

The organisation's experts supply the domain knowledge. Six shapes of work make demanding requirements of a system:

The signed opinion: A qualified person puts their name to a conclusion, and the reasoning must remain defensible years later. Competent person statements, expert reports, audit opinions, engineering certification, valuations.
The evidentiary file: The deliverable is the record that the team did the work as required. Audit working papers, maintenance and airworthiness records, trial master files, safety cases, credit files.
The periodic filing: A recurring submission to an authority, due by a deadline and assembled from data held across the business. Its quality depends on tracing each figure to its source. Regulatory returns, emissions and sustainability reporting, tax and transfer pricing documentation.
Adjudication at volume: A queue of cases or alerts, each needing an expert judgment that a reviewer or regulator can examine afterwards. Sanctions and transaction monitoring, claims assessment, credit decisions, grants, eligibility and classification.
The assembled document: A document drawing on knowledge held across the organisation, due by a deadline, whose errors carry legal or commercial consequences. RFP and DDQ responses, board papers, prospectuses, tender responses, submissions.
Continuous surveillance: The system monitors positions or conditions against limits and obligations, then reports, explains and routes each exception to the person responsible. Mandate and limit monitoring, compliance surveillance, obligation and deadline tracking.