Editions
日本語: エディション
Kurahi is one runtime with four Editions. Each Edition is a different working environment for a different kind of organisation: its own home screen, navigation, vocabulary and default agent team. Underneath, every Edition is the same Kurahi, with the same security model.
| Edition | For | Main canvas |
|---|---|---|
| Industrial | Plant engineering, operations, maintenance, legacy modernisation, OT/IT security | Estate health and active missions |
| Business | Back-office teams: cases, documents, workflows, approvals | Case and process desk |
| Scholars | Universities and research institutes, with separate Research and Education layouts | Studies and notebooks; courses |
| Core | Teams whose domain does not need a specialised Edition yet | Chat-first Project command centre |
What every Edition shares
Section titled “What every Edition shares”The Editions are configurations over one shell. These parts are the same in all of them and an Edition cannot weaken them:
- identity, Projects and their folder boundaries, permissions and connectors;
- chat and push-to-talk entry;
- versioned Artifacts with their producer and export hash;
- approvals and authority requests;
- the signed timeline and evidence provenance;
- the security model: policy, sandbox, exec approvals, audit log, supply-chain lock, memory provenance and signed agent messages (see Security overview).
An Edition’s manifest describes presentation and capability needs only. It has no fields for permissions, Project isolation, security, approval or audit policy. Routes and permissions come from capabilities, not from hiding things on screen; a connector that is missing or disabled stays visible with its current status.
Japanese and English are the launch languages for every Edition.
Capability packs
Section titled “Capability packs”Inside an Edition, domain lanes are capability packs. A pack adds agents, tools, templates and views; it does not add new global navigation and cannot change Edition policy. Each pack shows its readiness in the console: active, configured, disabled or planned.
The Industrial Edition has five packs today:
| Pack | Readiness | What it covers |
|---|---|---|
| Analysis | Active | Deterministic legacy analysis (COBOL/JCL, Java, SQL DDL) with path:line facts |
| Modernisation | Configured | Target design, transformation plan, equivalence evidence |
| Maintenance | Configured | Work orders, manuals and condition data, once those connections are set up |
| Controls | Disabled | Offline PLC review; stays off until an approved offline export is connected |
| Cybersecurity | Planned | Authorised-scope inventory and finding review; no scanner connection claimed |
What this release includes
Section titled “What this release includes”As of 29 October 2026, release 2.3.0. The status column says what is built and what is not.
| Item | Status |
|---|---|
| Edition and workspace manifests (all four) | Built: the shared shell selects an Edition’s navigation, vocabulary and layout |
| Industrial Edition workbench | Built: the first reference Edition, with the five packs above |
| Legacy analyser and design documents | Built: see Industrial modernisation |
| Work Console terminal and push-to-talk | Built: the Industrial Project terminal runs through the gateway broker; voice capture and transcript review are available; the run timeline is not complete, see Work Console |
| Business Edition | Available: work queue with approval routes (稟議), delegation and its withdrawal, expense requests, decisions, draft previews and evidence checks in the console, and 15 department workspaces; linked cases across departments, hand-off tracking and in-app notifications; quotations (見積管理) from CSV or Excel (.xlsx) price lists, supplier quote comparison and purchase-order drafts; five functional packs as starter workflows; see Work queue and Quotations |
| Autopilot (all Editions) | Built: routines per Project at autonomy levels L0 to L3, with standing approvals, triggers, a watchdog, a global stop and a morning brief; the reasoner runs on a command-line model backend or, with backend: api, an OpenAI-compatible model API or a local Ollama model; routines run only in Projects that define them (the templates include starter routines), see Autopilot |
| Enterprise identity and enterprise package | Built: OIDC and SAML sign-in, SCIM and roles (off by default), and an enterprise package without consumer channels; see Enterprise identity and Enterprise profile |
| Business connectors | Available, off by default: Microsoft 365, Gmail, Entra ID and six Japanese SaaS connectors (see Business connectors) |
| Data governance (all Editions) | Built: retention, legal hold, eDiscovery export, a My Number guard on outbound tools and data subject requests (APPI); see Data governance |
| Scholars Edition (Research, then Education) | Not built: navigation is defined; the Research and Education screens are not built. Available now through the Research & academic Project template: literature watch, citation check and grant reminders (Scholar sources, Autopilot) |
| Core Edition | Not built |
| Edition licences | Not published: licence identifiers are defined; terms and pricing are not published |
An Edition is considered ready when representative users can complete its three most important workflows without going through generic chat, and every agent action can be traced through the common evidence model.
Scholars: free for non-commercial academic use
Section titled “Scholars: free for non-commercial academic use”Kurahi Scholars is free for non-commercial research and teaching at universities and research institutes in any country. Commercial use needs a commercial licence. See Kurahi Scholars.