日本語

A governed mesh of
specialist clinical agents.

Not one giant medical AI — many bounded specialists, each assembled from audited parts, each with stated limits, each under human clinical approval.

Clinical operations under governance — where capability capsules work.

01 — THE ASSEMBLY

How a capsule is built.

Kenkō-W foundation

The sovereign medical base model — owned weights, edge-sized.

+ Speciality adapter

The clinical domain: geriatrics, wound care, medication — a LoRA per speciality.

+ Task adapter

The job: documentation, handover, triage support — narrow by design.

+ Jurisdiction adapter

The rules of the place: terminology, forms, regulatory language for Japan, Brazil or elsewhere.

+ Nyx-W role identity

The professional posture: role fidelity, escalation behaviour, discipline under pressure.

+ Clinical eRAG

Controlled evidence: institution-approved protocols with provenance — cite or defer.

+ KoLo permissions & tools

What it may touch, whom it must ask, and the audit of everything it does.

= A governed capability capsule

One bounded specialist, assembled, versioned and revocable.

The boundary, always. A capsule performs triage support, structured documentation and protocol-grounded guidance. It does not diagnose, does not prescribe, and does not replace clinical judgement — the doctor decides, the capsule records and supports, and everything is auditable.

02 — THE FIRST CAPSULES

The initial line.

Kenkō Scribe Edge

Clinical documentation at the point of care, offline-capable.

Kenkō Handover

Shift-handover structuring — nothing about the patient gets lost between teams.

Kenkō Medication Guardian

Medication-record support and interaction flags for human review.

Kenkō Patient Bridge

Patient and family communication support, multilingual, under clinical control.

Kenkō Geriatric Care Assistant

Long-term-care documentation and care-plan support — the Kenkō heartland.

Kenkō Wound Documentation

Structured wound records over time, consistent and reviewable.

Status, honestly. The capsule architecture is an engineering scaffold on the Kenkō-W training programme. No capsule is called a product before it clears evaluation, and none will make a clinical claim before clinical validation.

04 — HUMAN CLINICAL APPROVAL

What “under clinical approval” has to mean.

The phrase is easy to write and easy to hollow out. An approval step that a busy clinician clicks through a hundred times a shift is not oversight — it is a liability transfer with a user interface.

A named clinician signsNot a role, not a queue — an identified person who is accountable for the output entering the record.
Before it enters the recordApproval happens ahead of the write, not as a retrospective tick on something already filed.
With the evidence attachedThe clinician sees the source the capsule drew on, not only its conclusion.
Refusal is a normal outcomeRejecting output is an expected path, recorded as such, and does not degrade into a system that stops asking.

05 — PROHIBITED USE

Stated with the same weight as intended use.

Every capsule card carries prohibited use alongside intended use. A capability description that lists only what a system is for tells a clinician half of what they need to decide whether to rely on it.

No diagnosisA capsule structures, documents and flags. It does not conclude what is wrong with a patient.
No autonomous treatment changeNothing a capsule produces alters medication, dosage or care plan without a clinician acting on it.
No triage decisionPriority support may be presented. The decision about who is seen and when remains clinical.
No silent writeA capsule never writes to the clinical record without an approval event recorded against it.
No inference beyond evidenceWhere the approved sources do not cover a question, the capsule defers rather than generalising.

06 — CAPSULE LIFECYCLE

Assembled, versioned, revocable.

VersionedBase model, each adapter and the evidence set carry versions. "The capsule" is never an unversioned thing.
RevocableA capsule can be withdrawn centrally, and stops being available at the edge on next contact.
ExpiringEvidence sets and jurisdiction adapters carry review dates. Stale clinical guidance is a safety problem, not a maintenance one.
AuditableEvery invocation records which versions were active, what evidence was cited, and who approved the output.
ReproducibleA past output can be re-examined against the exact configuration that produced it.

Expiry is the one most easily skipped. A capsule quietly citing superseded guidance is more dangerous than one that refuses to answer.

07 — STATUS AND CLAIM BOUNDARY

What is not established.

Not a medical deviceNo capsule described here holds medical-device clearance in any jurisdiction, and none is claimed.
Not clinically validatedNo clinical trial, outcome study or independent clinical evaluation supports these capsules today.
Not deployedThese are described as an architecture and a line under development, not as systems running in hospitals.
Not a substitute for clinical judgementEvery capsule is designed on the assumption that a clinician remains responsible for the patient.

03 — EVERY CAPSULE CARRIES A PASSPORT

Declared, not implied.

Each capsule ships with a passport the institution can read:

Intended use — and prohibited use, stated with equal weight

Model requirement and active adapters, versioned

Evidence sources with provenance

Tool permissions and escalation boundaries

Human approval requirement — who signs, always

Edge hardware profile

Evaluation status and regulatory classification status

The medicine programme →