SYSTEMS / WHAT IS BUILT AND WHAT IS NOT
Four control problems. One architecture.
Consequential software needs more than generation. It needs a defensible answer to four questions: what deserves trust, what context may be used, what route may be taken, and what may actually be done. Kairos maps those problems to Invariant, Context Passport, Valence, and Lightcone. The maturity of each system is stated beside it.
What the states mean
- OPERATING
- Running now in the founders' working environment and producing evidence the work relies on.
- PRIVATE PREVIEW
- Working privately with a bounded audience; not represented as broadly deployed.
- IMPLEMENTED
- Built and tested. Not represented as a production customer deployment.
- SPECIFIED
- Architecture and boundaries are defined; not yet represented as a finished product.
- 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.
Maturity labels describe current evidence, not promises or release dates.
Evidence
What deserves trust? Kairos separates generation from qualification so a candidate has to earn advancement rather than inherit confidence from the system that produced it.
Invariant
OPERATINGHas this candidate earned the right to advance?
The first commercial wedge. A customer supplies a research mandate, data, universe, risk limits and privacy boundary. Invariant performs recurring generation, challenge, preservation, qualification and forward monitoring, returning a qualified candidate stream with evidence, lineage and advancement state attached.
Context
What information may be used? Useful software needs context, but context should remain scoped to purpose and should not silently become identity or authority.
Context Passport / PHC
SPECIFIEDCan context travel without surrendering control of the person it describes?
A user-controlled context architecture for carrying scoped, provenance-aware information across AI hosts. The format is intended to remain portable and separable from permission to act; commercial value, where created, sits in implementations and management tooling rather than ownership of a person's context.
Coordination
What route may be taken? Goals often depend on relationships, organizations and private context that should not be flattened into a public graph.
Valence
PRIVATE PREVIEWCan software surface a legitimate route to a goal without exposing more context than the route requires?
Privacy-preserving coordination and intent routing with canonical identity, consent and local/private deployment options. Valence is the coordination system in the Kairos architecture; it is not evidence qualification and it does not inherit authority merely because it can identify a route.
Authority
What may actually be done? Knowing what should happen and knowing who wants it are separate from having permission to execute it.
Lightcone
IMPLEMENTEDWas this action allowed, and can you prove it?
A control boundary for autonomous systems: authority delegated in bounded envelopes that fail closed, consequential actions checked before they leave, and decisions recorded with receipts. It is implemented and tested; the site does not represent it as a production customer deployment.
Under the systems
Kairos Core is the reusable deployment layer being productized beneath these systems. Finance is the first proving domain, with market-specific connectors, costs, regimes and evaluation rules kept in a Domain Pack rather than embedded in the cross-domain control architecture.
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.