Ojas is a generic runtime. Specific workloads are expressed as domain packs. The use cases below are representative of the patterns the envelope supports.
A user describes what they want in natural language. The query is routed to Ojas, which matches against the governed workflow catalog and returns ranked candidates with rationale — the match grade, which stages align, which inputs overlap, and why each candidate scored where it did.
The user picks. Execution proceeds through the platform's durable workflow runtime. Ojas never executes on the user's behalf, the human decision remains the commit point.
The PDF/JRXML domain pack is the worked example in the freeze specification. An incoming PDF is classified into one of three processing modes — replica, template, or official form — each with its own evidence threshold and gate requirements.
The pack emits a JRXML template proposal plus an evidence report. Gate results are attached. Every run's evidence is recorded, a regression failure on any corpus item blocks auto-approval until resolved or explicitly waived.
A document enters the runtime without a declared type. A registered Classifier agent proposes one or more candidate types with confidence, backed by evidence features — detected headers, layout fingerprint, field signatures, language.
The proposal carries the full classification vector, not just the top candidate. External approval may accept the top label, pick a lower-ranked one, or mark it for human review. Calibration is against a held-out set of labeled documents.
A stream of events — alerts, transactions, log spikes — enters the runtime. A Correlator agent links related events across the window. An Analyzer proposes candidate root causes with rationale: which events cluster, which precede others, which policies might apply.
The output is a ranked list of candidate explanations, each with supporting evidence and a recommended next action. An external responder or on-call authority reads the evidence and acts. Ojas does not page or act on the infrastructure itself.
The runtime is generic. Any high-trust catalog can become a domain pack: declare task types, register specialist agents from the nine generic roles, list allowed tools, attach gates and a regression corpus.
The runtime does the rest — sandbox, tenancy, budgets, tracing, proposal emission, calibration enforcement, simulation gating. Your pack inherits the full governance envelope.
See how domain packs register, the lifecycle from draft to active, and the nine generic agent roles they compose from.