pki.sgit.ai / experiments

Experiments

Game-like environments for the workflows this estate serves — simulated first, then supported. One experiment, one folder, one workflow, one visualisation, each with its own generator, its own gates, and its own bench entry saying what it does not prove.

The chain room Workflow: the full chain, reality → monitoring, with the library/instance boundary drawn on the floor Visualisation: a point-and-click room: eight desks, four verbs, a work item that travels Honesty: left half real artefacts; right half SYNTHETIC, marked on every surface · brief v0.33.66 The table Workflow: actions resolving against grants and mandates, and the consequences — forward as replay, backward as audit Visualisation: a card table: six suits, players that include the systems, four turns of a real incident Honesty: one hundred per cent real — the estate's own 26 August incident, from the artefacts it left behind, with the enforcement tool re-run at build time · brief v0.33.67 Push to GitHub Workflow: the grant chain behind a hosted agent changing a repository, and the three places a soft mandate could live Visualisation: a scenario world rendered by one JSON-driven engine: players, a grant chain, a capability deck with one micro-animation per capability kind Honesty: one hundred per cent real — the twin is this session's own environment, measured from inside; every card is a node in that library entry, gated one-to-one · brief v0.33.68 The Deploy Workflow: the environment a permitted push lands in — a CI runner with no agent, no hooks, and one platform-enforced grant Visualisation: the same engine, a different scenario.json: nothing else changed, which is the claim the pair exists to prove Honesty: one hundred per cent real — the twin is the estate's CI runner, measured from inside by the same tool on the same day · brief v0.33.68 The control room Workflow: both worlds at once, as an operator sees a plant — state at a glance, and the 26 August incident replayable on a sequence-of-events log Visualisation: a SCADA board with a game HUD: mimic diagrams, annunciator tiles lit by tier, faceplates on click, transport controls over the replay Honesty: one hundred per cent real, and zero new data — a second renderer over the same scenario.json worlds, every verdict re-run through mandate.py at build, mode chip pinned to REPLAY · brief v0.33.69

The rules every experiment inherits

  1. Every word derived at build time from the files the pipeline runs on; no typed counts.
  2. Real and synthetic never blend — a surface is derived from real artefacts, or it carries the SYNTHETIC marker beside every value.
  3. Every visual claim has a gate comparing the drawing to the declaration.
  4. Genre, not work: a genre's conventions are for using; a specific game's art, names or wording are not.
  5. Render it, screenshot it, read the screenshot before shipping.

Manifest: experiments.json — the hub is generated from it, and a manifest entry without a folder (or a folder without an entry) fails the build. Convention declared in brief v0.33.67.