Informational Fresh jira_story: GOV-223

Lesson 4 of 6 — Posture rollup cache on workspaces

Command Centre Enhancements · Source: Jira Story GOV-223 (3 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Serve the landing posture from a cache, fast.

Why it matters

Recomputing on every landing is slow at scale; a rollup cache fixes it.

Where this lives

Runs in the Customer AI Governance platform (components: command-centre). A posture rollup cache serves the landing from a single indexed read, invalidated on change. Learn teaches this read-only.

Workflow

Given a landing render
When it loads
Then it is served from one indexed read

Worked example

The landing page is slow because it recomputes posture each load. What's the fix?

Serve it from the posture rollup cache (one indexed read), invalidated when posture changes.

Acceptance criteria (authoritative — GOV-223)

Given a landing render, when it loads, then it is served from one indexed read.

Common pitfalls

A stale cache that isn't invalidated on posture change.

Knowledge check

Scenario: The landing page is slow because it recomputes posture each load. What's the fix?
Look for: Serve it from the posture rollup cache (one indexed read), invalidated when posture changes.

Key concepts

rollup cache
single indexed read
cache invalidation

For the AI Tutor

Summary: Serve the landing posture from a cache, fast.
When to use: teaching or answering questions about "posture rollup cache on workspaces".
When NOT to use: the recompute that fills the cache (that is GOV-135).
Key concepts: rollup cache, single indexed read, cache invalidation.

Completion criteria

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

Module: LEARN-MOD-008 (Command Centre Enhancements)
Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
Next: LEARN-LSN-043