Skip to content
GitHub
Customer

World Model Card

Generated

This page is generated from qa/customer/specs/world-model-card.md — the source of truth. Edit the spec, not this page.

Last run: not yet recorded (run the replay suite to populate status).

Overview

The Ruleset Card (design 03 surface F) is the version-scoped methodology disclosure of the ruleset governing a domain — the per-version, immutable record of the standard itself, distinct from the deployment-scoped System Card (Trust) per ADR-082. It is reached at /world-model-card (no tab; linked from the Trust version-history timeline at /world-model-card?version=N) and is read-only + curated. Its content: the authority basis (what the ruleset is grounded in), where the rules come from (the five-tier source families), the build configuration pinned at deploy, the action registry (absorbed from the retired Actions tab), the gates passed (review checks + verification), and what changed across versions. It leads to Rules for the full corpus rather than re-listing every rule. This spec verifies the active-version card renders, the deep link into a pinned version resolves, and the card carries the alpha-preview footer.

Preconditions

  • Signed in as the seeded QA customer (see CUST-AUTH-GATING scenario 2).
  • The customer’s domain is bound to a deployed world model version (seeded; produced by the operator journey + seed_customer_fixture).

Scenarios

1. Active-version Ruleset Card renders

  • Navigate directly to /world-model-card
  • Expected: The card renders the authority basis (“What this ruleset is grounded in”), “Where the rules come from”, the action registry, and the review-checks / verification sections — not a blank page.

2. The card leads to Rules rather than re-listing every rule

  • On the Ruleset Card, find the link to Rules
  • Expected: A link to Rules (/world-model) is present; the card shows a rule count, not the full rule corpus.
  • Navigate directly to /world-model-card?version=1
  • Expected: The card resolves to an explicit state — the version-1 methodology record if version 1 was deployed, otherwise the not-deployed empty state — never a blank or crashed surface.

4. Identifiers are masked (no full UUIDs)

  • On the active-version card, inspect the authority reference
  • Expected: The authority reference renders as a short handle, not a full UUID.
  • On the Ruleset Card
  • Expected: The non-dismissible alpha-preview footer is present.

Test Data

LabelValueNotes
Deployed world(bound via seed_customer_fixture)Customer domain → deployed version