Documentation / Overview

Understand the representation before the interface.

Our documentation begins with the concepts that remain stable across deployment, ingestion and product UI: where behavior sits, what a record carries, and how evidence limits are expressed.

Scope note

This documentation covers architecture and semantics: where behavior sits, what a record carries and how evidence is expressed. For installation, API and integration questions, contact us.

Choose a starting point

01Getting started

Build a correct mental model of the layer and its evaluation path.

02Architecture

Follow telemetry into behavior and out to downstream consumers.

03Behavior schema

Inspect the six dimensions and a representative record shape.

04Evidence states

Distinguish observation, inference and known absence.

Documentation principles

  • Field names and identifiers use monospace only when they represent real record content.
  • Architecture claims link back to labeled diagrams rather than feature adjectives.
  • Interfaces are documented once they are stable, so what is written here can be relied on.
  • Evidence gaps are part of the model, not footnotes attached after a conclusion.