Current engine & evidence

Operational evidence - Without exposing the Core.

AXIS demonstrates that the product exists while protecting thresholds, weights, identifiers and proprietary rule logic. DBSI means Deterministic Biological State Index: the explainable 0–100 episode-level synthesis generated above the four axes. This page separates functional execution from the external evidence and production work still required.

Functional Core BloodSanitized disclosureTraceable outputValidation pending
AXIS Core Blood · engine v0.5.1Operational evidence
Functional
This screenshot is taken from the functional AXIS environment. It is sanitized and does not disclose patient identifiers, thresholds, weights or rule logic.
01 / Current engine

Operational execution is already visible.

The current Blood engine runs the complete deterministic hierarchy from normalized parameters to patterns, blocks, axes and global synthesis.

  • 40 normalized parameters in the current public configuration
  • 27 deterministic functional patterns
  • 10 functional blocks in the current ruleset; 8 are active in the displayed operational run
  • 4 biological axes
  • 1 traceable synthetic state
  • Confidence, coverage, coherence, conflict and version context
02 / Three views

Operational view, inference, structure and synthesis.

The operational view is real and sanitized. The pattern view uses synthetic display values so the hierarchy can be explained without disclosing proprietary rules or source data.

01 / Sanitized operational interface

The current engine in its real working environment

Operational screenshot from AXIS Core Blood, shown in its present internal language configuration. US-English localization is part of productization. No patient-identifiable data or proprietary calculation logic are disclosed.

03 / Evidence boundary

Proof of execution is not proof of clinical performance.

A functional deterministic engine demonstrates reproducible execution. Clinical validity, professional utility and regulated performance require separate evidence.

Demonstrated now

Operational execution

  • Complete deterministic hierarchy executes end-to-end
  • Same input and version produce the same output
  • Outputs retain confidence, coverage and calculation path
  • Current episode outputs retain module and version context for longitudinal comparison
Still to establish

External performance evidence

  • Clinical or professional utility in defined populations
  • Calibration and performance under frozen versions
  • External and prospective validation
  • Regulated intended use and jurisdiction-specific clearance
04 / Readiness map

What exists, what is being built and what still requires evidence.

The readiness map makes the boundaries between functional capability, development work and external evidence explicit.

Available

Deterministic infrastructure

Hierarchy, rules, confidence, coherence, conflicts, axes and traceability.

In development

Multimodal cross-pattern configuration

Within-domain patterns and cross-patterns across genetics, fecal microbiota, metabolomics, wearables and phenotypic and contextual data.

To demonstrate

Professional utility

Retrospective and supervised evaluation in defined clinic or laboratory workflows.

Later medical phase

Regulated performance

External validation, QMS, technical documentation and jurisdiction-specific approval.

Qualified access

See the real engine at the appropriate disclosure level.

Operational screens, deeper traceability and technical documentation can be reviewed under a qualified process.

Request private access