SYSTEMS / WHAT IS BUILT AND WHAT IS NOT
One discipline, applied to more than one problem.
Consequential systems should have to earn trust and authority before they advance. That principle is old and the applications are not: a prediction has to earn belief, an agent has to earn permission, and a person's context has to travel without carrying permission with it. Everything below comes out of work that exists. How far along each part is varies, and is stated next to it.
What the states mean
- OPERATING
- Running now, in real use, producing evidence this work relies on.
- IMPLEMENTED
- Built and tested. Not in live use by anyone.
- PRODUCTIZING
- Being turned into something a customer can run.
- DIRECTIONAL
- A credible path out of work that already exists. Not being built as a product yet.
Release dates are published only when there is an operating plan behind them.
Research and qualification
Deciding whether a prediction has earned the right to be acted on. This is the oldest part of the company and the part with the most evidence behind it.
-
Kairos Core
PRODUCTIZINGCan the loop run on somebody else's problem?
The shared machinery: authorized data in, candidates generated, attacked, mostly rejected, failures kept, survivors watched forward, advancement controlled. It runs today as research infrastructure. Turning it into something a customer can operate on their own data is the work.
-
Invariant
OPERATINGDoes this prediction deserve to be acted on?
The model side of the loop, running continuously against real market data. It runs on XGCS research infrastructure planned for licensing to Kairos. Its record, including the results that failed and the ones later found to be contaminated, is open to read.
-
Finance Domain Pack
PRODUCTIZINGWhat does this loop need to know about markets specifically?
Connectors, cost models, regime tests, baselines and evaluation rules for the first domain. Markets were chosen because a weak model fails there quickly and measurably, not because the company is a finance company.
Authority and autonomous systems
The same discipline pointed at actions rather than predictions. Knowing what someone wants is not the same as being permitted to act for them.
-
Lightcone
IMPLEMENTEDWas this action allowed, and can you prove it?
A control boundary for autonomous systems: authority delegated in bounded envelopes that fail closed, every consequential action checked before it leaves, and the decision written to a hash-chained record. Nothing has deployed it in production, nobody uses it, and it has never governed a real agent.
-
Controlled operations
OPERATINGCan an agent be given real operational reach without giving it the keys?
Intent becomes a typed request, authority decides, a bounded worker executes, and a receipt comes back. This runs internally today against a narrow set of operations. It is the same shape as Lightcone, applied to the company's own infrastructure rather than a customer's.
Human context
One architecture track, not a second company. What a system is allowed to know about a person, how that travels between tools, and why knowing it grants no permission to act.
-
Portable Human Context
DIRECTIONALCan context be owned by the person it describes?
A draft interoperable standard for user-owned AI context: what a tool may be told, scoped to a purpose, with provenance attached. It is being drafted as an open standard rather than a Kairos product. Implementations, custody and management tooling around it may be commercial; the format itself is not intended to be.
-
Context and intent systems
DIRECTIONALWhat would it take for software to understand a person well enough to be useful, and no further?
Working prototypes exist for conversational intake, intent extraction and matching within a trusted network. How much of this becomes a Kairos product rather than adjacent research is not settled, and the ownership question behind it is open.
Evidence-bound communication
The newest and least proven of these. A generative layer may explain what the evidence says without gaining the ability to change it.
-
Evidence-bound generation
DIRECTIONALCan a model explain a finding without being able to invent one?
A pipeline exists that composes and renders from a sanitized snapshot and cannot reach past it to the underlying research. Whether that becomes a product or stays internal plumbing depends on evidence that has not been gathered.
Further out
As the finance stack matures, Kairos may eventually sponsor or support an affiliated vehicle that uses this infrastructure in a live capital environment. Any such vehicle would be separately structured and separately regulated, and would be an application of the software rather than a description of the company. Nothing about it is offered here.