Research systems · Dated evidence
Product judgment should leave an engineering record.
In-house research systems used to test product, architecture, evidence, and governance decisions in source.
These builds turn consulting questions into inspectable systems: where authority sits, what evidence advances a gate, how a model is bounded, and what remains unproven. Every detail page now separates implemented source, documented design, and deployment evidence.
Category spine · 03 systems
Method, machine, and organisation form one evidence loop.
LaunchpadOS codifies product judgement. Auralink pressure-tests it against a Physical AI system. TransformationOS carries the resulting decisions into portfolio, operating-model, and Agile-at-scale work.
01 · Category operating system
LaunchpadOS
Source toolkit under active development
Source through 2026-08-25
Makes full-lifecycle product judgement versioned, inspectable, and executable.
Inspect the venture recordProduct decision
Define which product decisions matter, which evidence advances a gate, who owns the call, and what must cause the decision to reopen.
Technical record
Versioned skills, the Operated Product Decision Graph, Release Case boundaries, CLI and MCP surfaces, workflow state, evaluations, and audit records.
02 · Physical AI reference implementation
Auralink
Documented research reference
Source through 2026-08-24
Pressure-tests product and architecture decisions against a real cross-domain Physical AI source system.
Inspect the venture recordProduct decision
Separate the reusable horizontal coordination substrate from vertical protocol ownership and keep final safety authority with the local controller.
Technical record
Signed proposals, resource leases, policy and admission boundaries, local veto, authoritative readback, catalogues, conformance paths, and cross-domain simulation.
03 · Organisational transformation demonstrator
TransformationOS
Demonstration platform
Source through 2026-04-08
Connects portfolio intent, product operating models, Agile@Scale, delivery evidence, and governance decisions.
Inspect the venture recordProduct decision
Represent decision rights, assumptions, approval states, evidence, cadence, and handover across the transformation portfolio.
Technical record
Tenant configuration, workflow modules, connector boundaries, retrieval, DORA and flow metrics, scenario records, proposal-first writes, approvals, and audit state.
Capability experiments · 07 source systems
Bounded builds that sharpen the wider practice.
Each experiment isolates a hard product boundary—from embedded telemetry and security scanning to regulatory evidence, agentic workflows, diligence, and creative orchestration.
Achilles AI
Source under developmentSource prototype, access under NDA
A Rust static-analysis tool focused on AI-generated and AI-application code patterns. It combines tree-sitter parsing, source-controlled rules, SARIF output, command-line and editor surfaces, and optional model-assisted triage.
Exercises: GovernanceReliability
Aegis AI
Source under developmentDevelopment prototype
A regulatory-workflow backend prototype with inventory, retrieval, classification, evidence, remediation, audit, and report modules. It is a decision-support system under development, not legal advice or a conformity assessment.
Exercises: GovernanceData
Athena AI
Source under developmentDevelopment prototype
A multi-tenant business-workflow prototype with departmental modules, queued agent execution, retrieval memory, and model routing. The source demonstrates orchestration boundaries, not autonomous business operation.
Exercises: ArchitectureData
EU AI Navigator
Source under developmentDevelopment prototype
An SME assessment and reporting prototype combining conversational intake, deterministic scoring, country data, retrieval, and a Mistral-assisted report pipeline. It is guidance software under development, not a legal determination.
Exercises: GovernanceData
Kairos VC
Primary buildDevelopment prototype
A full-stack diligence-workflow prototype with deal, research, scoring, portfolio, and reporting surfaces. Its source demonstrates workflow architecture and provider abstraction; it does not establish investment performance.
Exercises: DataArchitecture
Techne AI Studio
Source under developmentDevelopment prototype
A multi-surface creative-workflow prototype with web, API, gateway, worker, mobile, and document-add-in packages. The repository shows routing and workflow structure; provider availability and output quality are configuration-dependent.
Exercises: ArchitectureIntegration
Vectis AI
Source under developmentSource prototype with software and firmware boundaries
A vehicle-data prototype spanning API, user surfaces, embedded source, and a Rust signal-normalisation core. The implemented record supports trace and fixture work; vehicle, hardware, and fleet validation remain outside it.
Exercises: IntegrationArchitecture
Evidence doctrine
The bridge is a closed decision loop, not a slogan.
- 01
Business pressure
Name the customer, economic, portfolio, and operating constraint.
- 02
Product decision
Record the choice, owner, evidence threshold, and invalidation rule.
- 03
Technical record
Express the decision in architecture, source, interfaces, and assurance work.
- 04
Evidence return
Return field and delivery evidence to strategy, scope, funding, and governance.
Thirty minutes with the person who builds these.