Trust starts with the boundary. Octeryx OS should be described clearly enough for people to understand the ambition, and carefully enough that nobody mistakes active research and architecture validation for production deployment.
The public stage is active R&D. That means the important claim is not that Octeryx OS is already running care environments. The important claim is that the core runtime boundaries and contracts are being separated, tested and validated against synthetic fixtures.
What Is Currently Evidenced
Public copy can talk about accepted modular product doctrine, historical typed Kasa contracts and boundary proofs, target identity, context, policy, runtime, evidence and PostgreSQL ownership, and Kasa/Film profile isolation requirements.
It can also describe deterministic historical Kasa fixtures, replay and architecture validation. Those are meaningful repository proof points, but they are not current Octeryx runtime, live deployment or clinical validation.
What Is Not Claimed
Octeryx OS does not currently claim live production deployment in a care provider, hospital, robotics OEM or other operational environment.
It does not claim clinical validation, regulatory approval, certified operation, production readiness, universal robot compatibility, unsupervised autonomous decision-making or replacement of clinicians, carers, safety systems or robot control stacks.
Why The Markdown Boundary Stays Public
The article is for readers. The Markdown proof boundary is for citation, crawlers and answer engines. It gives machines a stable, unambiguous source for maturity and non-claims.
That is why proof-boundary.md should remain public. It protects the story from over-compression when an LLM summarises the product.
How To Read Future Claims
As Octeryx OS matures, public language can expand only when the evidence expands. A design partner, pilot, certification, live deployment or clinical validation should be named as such only when it exists and can be cited.
Until then, the strongest accurate phrase is active R&D context operating system for autonomous machines, with care as the first reference environment.