Platform / Behavior model

A behavior is more than an event with a better label.

The representation carries execution context, capability, actions, immediate effects, persistent effects and observability together. [schema]

Read the documentation Platform overview
The six questions a behavior answers Six stacked rows, each a plain-language question: who or what acted, what it can do, what it did, what changed immediately, what remained afterward, and how certain we are. The sixth row is drawn dashed and hatched because it represents what was not observed. Every behavior answers six questions 1 Who or what acted? execution context 2 What can it do? functional profile 3 What did it do? actions 4 What changed immediately? immediate effects 5 What remained afterward? persistent effects 6 How certain are we? observability The sixth question is the one most systems never ask.
Six plain-language questions define what a complete behavior record needs to carry.
01 / Behavior model

Context identifies the actor

The record names the process, service, user or system behind an action and preserves the execution conditions that shaped it.

[schema]
02 / Behavior model

Effects make change explicit

Immediate effects describe what changed now. Persistent effects describe what remained after the activity completed.

[schema]
03 / Behavior model

Observability sets the boundary

Each part can state whether it was directly observed, inferred from adjacent evidence, or unsupported because telemetry was absent.

[schema]

Next step

Continue from concept to reference.

The documentation describes the shared vocabulary, architectural boundaries and evidence-state semantics used throughout the platform.

Read the documentation