Know what has—and has not—been verified.

A core work-order, worksheet, review and PDF certificate path has been demonstrated with synthetic records. Other modules have varying test coverage and known gaps. Screenshots are demo data; the animated tour is an illustration, not live execution. See /readiness.

This site does not present verified customer deployments, approved testimonials, independent penetration-test attestations, SOC 2 reports or ISO 27001 certification. No certification timetable, adoption figure or guaranteed outcome is asserted.

Standards references identify evaluation requirements, not certified or fully validated compliance. Qualified personnel must assess methods, uncertainty, traceability, signatures and records in the intended deployment. See /compliance.

Historical audit-verification mismatches remain. Role separation, organization isolation, account recovery, encryption, backup restoration and other safeguards need verification. Read /security; do not infer that a listed control is fully deployed or independently tested.

The assistant matches questions to manually written documentation on this server. It is not a general-purpose AI model and cannot analyze your laboratory records. Product AI, predictive outputs and deployment-wide data flows need separate testing. Do not send confidential records through the public assistant.

Implementation and private deployment can be discussed during evaluation. Prices are indicative scope figures, not a promise of immediate readiness. License rights, operating costs, support, acceptance and data-processing arrangements must be confirmed in writing. No air-gap, uptime, response-time or recovery guarantee is implied.

Privacy, Terms of Service and DPA obligations are not proof of tested implementation. These status corrections do not waive existing rights or signed commitments. Subscription-oriented clauses and the proposed perpetual-use model need contractual reconciliation before any new agreement.

• Product status — /readiness
• Security status — /security
• Standards evaluation — /compliance
• Privacy Policy — /privacy
• Data Processing Agreement — /dpa
• Terms of Service — /terms

Write to philip.montford@calbrixos.com about test scope, open gaps and acceptance requirements. Available evidence must be distinguished from documents or controls still to be prepared; naming an attestation in a questionnaire does not mean it exists.