Line
Decides fast. Irreversible.
At the line, control decisions happen in milliseconds and physically commit. If the surrounding context is not captured at that instant, it is gone — there is nothing to reconstruct afterwards.
ms · irreversibleScope: this page is an architecture model, not a list of features shipping in TrailMQ 3.1.0. Current core capabilities are MQTT transport, two-gate policy enforcement, attributed decision records and a scope-defined system/action chain. Context extraction, historical baselines, deviation calculation and decision traces are planned.
Perspective
Decision layer
Proximity
GMP scales with proximity
The closer to the physical process a decision is made, the faster and more irreversible it becomes — and the harder the evidence is to reconstruct later. Switch perspective above; filter by decision layer to focus on one system level.
Site
Decides formally. Approval required.
Release, deviation and disposition decisions are deliberate, reviewed and signed. They are slower by design — accountability matters more than speed.
reviewed · signedCloud
Contextualizes and recommends.
Cloud and analytics layers can use aggregated history to surface signals and support review. Decision authority and required evidence should follow the intended use and risk assessment.
context · recommendationLine
Real-time window
Context exists for milliseconds to seconds. If it is not recorded at decision time, it cannot be reconstructed — the value loses its meaning the moment it passes.
ms – sSite
Batch & shift window
Decisions span a batch or a shift. Intervals are not abstractions — they are commitments that define meaning, responsibility and comparability.
min – hCloud
Historical window
Baselines and trends are built over days to months — from structured snapshots, not raw logs. This is the reference live values are compared against.
days – monthsAttributable
Who & what
Every record carries the identity behind it — which client, user or service triggered the event, and under which permissions.
Contemporaneous
At the moment
Evidence is captured when the decision happens — not assembled after the fact from scattered logs.
Original
First record
The structured record is the source of truth, not a copy or a transformation that can drift from the original.
Accurate
Checked against intended context
Conceptually, a value should be evaluated against the context and reference that apply. TrailMQ context and baseline plugins are planned, not current.
Complete + Consistent
Missing context stays explicit
A complete evidence design records that required context was unavailable. Deferred context-driven calculations are part of the planned plugin direction.
Enduring + Available
Scope-defined integrity
TrailMQ's local hash-linked check covers system and action entries. It is not WORM storage, external notarization or a check over the separate MQTT decision store.
Line
Accept / Block
Current core: role permission and namespace/topic policy are enforced inline, and the attributed MQTT outcome is recorded.
current coreLine
Rate-limit
Architecture direction: protect downstream systems from floods while keeping throttling decisions visible.
plannedSite
Defer / Queue
Architecture direction: make a missing-context calculation explicit and reviewable instead of silently skipping it.
planned context flowSite
Escalate / Approve
Architecture direction: route a GxP-relevant decision to the organization's approved human workflow.
conceptualCloud
Flag / Recommend
Architecture direction: surface anomalies and recommend a review while decision authority remains defined by intended use, risk and approved procedures.
conceptualPlanned plugin scenario: the seven steps below illustrate the proposed live-versus-historical recipe. They are not executable in TrailMQ 3.1.0.
1
Machine publishes a live value
An OEE / temperature value arrives over MQTT from the filler on line 1.
2
Domain context extracted
Line, machine, batch and metric are resolved from the topic and payload.
3
Historical baseline resolved
The expected reference value is fetched from the historical context feed.
4
Deviation calculated
Live vs. baseline is compared; the deviation and its severity are computed.
5
Decision gate evaluated
The proposed decision trace explains whether the value was accepted, blocked, rate-limited or escalated.
6
Missing context is deferred
If a baseline is unavailable, the calculation is queued for review rather than skipped.
7
Evidence linked for review
The proposed plugins link value, context, baseline, deviation and decision trace into a reviewable path.
No decision object sits at this layer in this perspective.
This is a conceptual model of how regulated decisions and evidence can relate across system layers. It informs product direction; it is neither a certification claim nor a statement that every illustrated capability ships today. Read the underlying concepts →