Conductor
Part of Kundi · For Banking, Asset Management
Conductor is the part of Kundi that turns data and algorithms into running applications. Teams assemble pipelines and applications from blocks or a single specification instead of writing application code. Conductor enforces the controls the specification declares and records every decision on a hash-linked lineage chain. Models can propose; rules and people decide.
Applications from specifications, not software projects.
A Conductor application is a declaration of collections, roles, views, actions and controls. The platform does the rest and refuses anything the declaration does not allow.
-
Application Studio
Build and operate an application from blocks. The Studio checks the build as you go and refuses missing, reordered or duplicated steps.
-
Pipelines With Reasons
Source, extract, shape, compute, decide, infer and consensus steps. Every rule that fires records why.
-
Controls That Refuse
Four-eyes approval, closed reason codes, gates before writes and role checks are declared once and enforced everywhere, with refusal messages that name the cause.
-
Decision Lineage
Every decision is linked into a hash chain. Verification reports separately whether the chain is intact and whether the decision is reproducible.
-
Algorithms on Call
Pipelines call COSMIC algorithms directly, and Studio ensembles require at least two distinct models.
-
Learns From Analysts
Models refit on analyst findings, and Conductor stores the exact training data and hashes behind every refit.
-
Model Budgets and Consensus Rules
Each application has a model budget. A missing vote is not a smaller electorate, and a split panel returns no answer rather than a guess.
AI proposes. Code and people dispose.
Conductor keeps models in an advisory role by construction.
-
No Pipeline Ends on a Model
A pipeline cannot finish on a model answer; a rule or a person always makes the call.
-
No Model Inside a Gate
Gates that protect writes cannot contain a model.
Locked down before it leaves loopback.
Conductor will not serve beyond the local machine until it has an identity store and a certificate.
-
Identity and TLS Gate
Off-loopback serving requires both an identity store and a certificate. Repeated failed sign-ins lock the account.
-
Inside Your Perimeter
Runs on infrastructure you control. Models and data stay inside your perimeter, and nothing calls home.
-
Quantum-Resilient
Built for the post-quantum transition that federal deadlines put in 2030 and 2031. Records and decisions stay confidential and verifiable after a cryptographically relevant quantum computer exists.
-
SOC 2 Type II
Frontier Foundry is SOC 2 Type II.
See it inside your environment.
Conductor walkthroughs are available under NDA. Watch an application built in the Studio, a decision traced through its lineage, and a refused action, inside your environment.