Build / Makes software
Agents plan, write and check software in isolated workspaces, returning changes with test evidence.
Sarvagya
Free to try anything. Careful about what you keep. Sarvagya is the proposed experimentation and governance subsystem within Tracient—designed to make each model, agent and idea earn its place before anyone depends on it.
Proposed trust lifecycle
Registered and checked, but given no real work.
Evaluated against a fixed exam for its intended task.
Works beside the current model. Its answers are compared, never used operationally.
A named person signs off on the evidence. No agent promotes itself.
Receives real work and remains under monitoring.
Agents plan, write and check software in isolated workspaces, returning changes with test evidence.
Version-controlled experiment recipes make trials inspectable and repeatable.
Permission-checked examples train leaner agents that must pass fixed evaluations.
A shared gate assesses task fitness, watches model health and controls routing after human approval.
Proposed design: isolated execution, bounded run budgets, protected evaluation sets and an auditable decision record. These are design rules, not measured results.
How it fits within Tracient
Saola maintains the data-to-model workflow and versioned catalog. Sarvagya is intended to add controlled experimentation, comparative evaluation and approval gates. Approved model outputs can contribute to Sanjaya; live operational feeds do not need to pass through experimental agents.
Sarvagya is exploratory and not yet generally available. Its proposed governance workflow is not claimed as part of the earlier defense POC.
Where we are
Core platform, shared foundation and agents that build software.
Repeatable experiments.
The five-step model gate and teaching smaller agents.
Explore the proposed governance model, experimentation workflow and where human approval sits in the lifecycle.