Informational Fresh jira_story: GOV-322

Lesson 3 of 4 — Active-plane runtime posture signals

Scale & Intelligence · Source: Jira Story GOV-322 (13 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Feed runtime (Active-plane) signals into governance posture.

Why it matters

Design-time posture is incomplete; runtime behaviour is the real risk.

Where this lives

Runs in the Customer AI Governance platform (components: active). The Active enforcement plane streams runtime events into posture computation. Learn teaches this read-only.

Workflow

Given runtime events
When they arrive
Then posture reflects live runtime signals

Worked example

A system is documented as compliant but drifting at runtime. How does posture catch it?

Active-plane runtime signals feed posture, so live drift is reflected, not just design-time state.

Acceptance criteria (authoritative — GOV-322)

Given runtime events, when they arrive, then posture reflects live runtime signals.

Common pitfalls

Governing only paperwork while runtime drift goes unseen.

Knowledge check

Scenario: A system is documented as compliant but drifting at runtime. How does posture catch it?
Look for: Active-plane runtime signals feed posture, so live drift is reflected, not just design-time state.

Key concepts

runtime signals
Active plane
live posture

For the AI Tutor

Summary: Feed runtime (Active-plane) signals into governance posture.
When to use: teaching or answering questions about "active-plane runtime posture signals".
When NOT to use: the design-time recompute on task close (that is GOV-135).
Key concepts: runtime signals, Active plane, live posture.

Completion criteria

Learner passes the scenario knowledge check and can point to the system state that satisfies GOV-322's acceptance criterion.

Module: LEARN-MOD-011 (Scale & Intelligence)
Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
Next: LEARN-LSN-057