jBOK is the organization-neutral blueprint for decision ecosystems where AI and simulation carry real consequences — built on one conviction: trust is earned.
High-consequence decisions increasingly run through AI models and physics simulation. What's missing isn't capability — it's an architecture of trust: shared contracts that let independent organizations build interoperable capabilities, prove claims with evidence, and replace any component without unwinding the whole. jBOK is that architecture, kept deliberately free of every vendor, product, and use case so it can serve all of them.
Every capability sits behind six versioned interface-contract families (ADR-0005), each with a versioned JSON Schema and executed conformance tests. Adaptable by Design: replaceability behind stable interfaces is the testable floor; governed adaptation within validity envelopes is the goal.
Model contracts classify every parameter's origin — down to hand tuning without an external anchor
and undischarged assumption
. Disclosure is legitimate; disguise is a contract violation. Absence of a declaration never reads as confidence (ADR-0006).
Accreditation is a use-specific decision by an identified authority, with recorded basis, conditions, and revocation triggers. Runtime assurance means monitoring plus an assured intervention path. Human authority boundaries stay explicit.
An RFC-style living document: versioned chapters, appendices, and specs; seven ADRs guarding narrative and taxonomy; five review gates; 30 executed conformance tests in CI. External research is incorporated fully attributed and severable — replaceable as the field moves.
Use cases, products, and organizations reference the architecture. The architecture references none of them back. One implementation profile — JWM — is documented as evidence, and the book can never depend on it.
jBOK doesn't just describe architecture — it metabolizes implementation experience.
ADR-0006 (parameter provenance & completeness) was generalized from JWM's PROV-0 register — the profile is the origin of, and first conformance data point for, that contract language.
Principle evolution is governed by ADR-0007. Terminal values are durable, not frozen — mechanisms adapt continuously under evidence; the values themselves are revised only by human insight, deliberately, through an ADR.