Methodology
Tension OS v2.1
A decision-and-governance methodology: the engine and process by which a conforming implementation produces a Decision Plan Brief that satisfies a structural specification — what must be done, in what order, under what thresholds and gates, to produce an auditable decision record. Version 2.1 (2026-04-24) is an errata pass after an independent benchmark of the previous version. It was drafted to a ceiling-quality decision set (an academic methodological posture; a linear-additive multi-attribute value core with explicit value functions) against a stated bar: defensible to a Big-4 partner and to a regulator.
The specification set is being consolidated into a single presentation-grade document so that it can be read in one sitting and tested through the demonstrator below. Until that document is published here, the v2.1 specification set is available on request through LinkedIn.
Conformance cross-walks
The methodology's decision artifacts are cross-walked to the EU AI Act, ISO/IEC 42001 and the NIST AI Risk Management Framework inside Keel's decision architecture. The propagation of v2.1 into the demonstrator was specified in June 2026 and has not yet been applied to it; the demonstrator is labeled accordingly.
Keel — the methodology in practice v3 demonstrator
Keel is an AI-governability decision system that productizes the methodology: a decision frame coupled to a conformance scope, producing an auditable artifact. The hosted demonstrator implements the MVP specification and predates the Tension OS v2.1 propagation and the ceiling-quality build target, both specified in June 2026. It runs in the browser, makes no network calls to model providers, and stores nothing. It loads React and Babel from unpkg and fonts from Google.
Three public GPTs
- Tension OS Business Edition — executive-ready decision packs: trade-offs, experiments, seven-day plans.
- Tension OS Decisions, Personal Edition
- Tension OS Journal, Personal Edition
Free to use with a ChatGPT account; not paid products.
Documentation discipline
Every build on this site ran under a written protocol: corrections by supersession rather than silent edit; a session-close package for every working session; a gate of three consecutive identical green runs before anything ships; and a defect-and-change register kept across build sessions. The register on this site is the same practice applied to the instrument.