Products
From model to post: five layers integrated on one server.
XingBan OS for elderly care has five layers: compute, operating system, model, agent layer and digital workers. Each can be delivered on its own; together they form the foundation of an entire care home.
- L1 Ark
- The compute-storage-orchestration server and the compute.
- L2 XingBan OS
- The operating system and scheduling.
- L3 XingHan
- The model and judgement.
- L4 Agent layer
- Division of labour and orchestration.
- L5 Digital workers
- The roles delivered at the post.
A general model cannot say which nine risks Chinese care homes actually guard against, and it cannot parse the abbreviations in a nursing note. We build the corpus, the model, the system and the hardware ourselves, and that is how we take responsibility for the site.
- Corpus
- Continued pre-training on elderly-care text, then supervised fine-tuning on care records.
- Model
- MoE architecture, deployed across device, edge and cloud, with private deployment supported.
- System
- Built in-house on the full OpenHarmony foundation.
- Hardware
- Our own compute-storage-orchestration server, models pre-deployed at the factory.
The path of one signal
Data collected by devices becomes a record, then a judgement.
The perception layer admits six elements through one interface. Data is stored on site, the model forms a judgement, and an agent turns that judgement into a specific action at a post. The chain still runs when the network is down.
- One intake
- People, devices, materials, environment, systems and data.
- On-premise
- Raw data stays inside; only conclusions are shared.
- Judgement
- Reads medical orders, care records and ordinary conversation.
- Action
- A judgement becomes a task, an alert or a completed ledger.
What is delivered
An institution buys the capacity of nine posts, not a software licence.
Each of the nine digital workers is defined by remit, permission and deliverable. It is not a general assistant: deliverables can be reviewed, traced and returned for rework.
- A remit
- Each one states what it covers and what it must not touch.
- A deliverable
- Daily briefs, checklists, ledgers and reminders in fixed formats.
- A stage
- Demo, in build, planned, stated for every item.
Implementation path
Validate the machine first, then two posts.
One on-site demo shows the Ark as shipped, then two roles run against the institution's own scenarios. If the evaluation finds no fit, the process stops there and no procurement begins.
Book a demo
Title
Thirty minutes to observe nine digital workers operating in a real care setting. An advisor will call to confirm the time and focus.