Changelog

Wave 1 — element and crosswalk layer

The first public release. 58 elements across nine active tracks (N1–N9), each with an operational definition sourced to at least one real primary document, and a shadow-mapping crosswalk of 415 rows showing how named labs, evaluators and government instruments each use the concept — every row explicitly labelled as CASRAI's own unconfirmed reading, never a declared mapping.

Shipped

• 58 nikolai_element entries, extracted from the deep primary-source crosswalk research (Anthropic RSP v3.4 and Risk Report, OpenAI Preparedness Framework v2 and Frontier Governance Framework, Google DeepMind Frontier Safety Framework v3.1, xAI Frontier AI Framework, Meta Advanced AI Scaling Framework v2, the EU GPAI Code of Practice, California SB 53, METR, the Frontier Model Forum) and independently re-verified line-by-line against those source documents before publication.
• 415 crosswalk rows, each carrying is_shadow:true and declared_by:null — enforced three times over: the write endpoint rejects a row missing the flag, the one-shot seeder skips it, and the read resolver hard-codes the value regardless of what is stored, so the guarantee cannot silently regress.
• Ten nikolai_track taxonomy terms (N1–N10) registered; N10 (Assurance roles, the CRediT-pattern accountability layer) is deliberately unpopulated — a separate, later piece of work.
• The landing page, all nine populated track hubs, and every element page live and indexed, with a JSON-LD DefinedTermSet at /nikolai#set and per-element DefinedTerm payloads.

Explicitly not included in this release

• The other eight CPTs the full build package specifies — nikolai_instance, nikolai_attestation, nikolai_incident, nikolai_mapping, nikolai_eval, nikolai_model, nikolai_checkpoint, nikolai_role — are not built. No lab document has actually been encoded as a full risk-report or framework-card instance yet.
• No MCP tools, no /api/v1/nikolai/* REST surface, no validator, no JSON Schema or SKOS/Turtle export bundle.
• No registry or conformance-scoreboard pages, no working-group pages.
• No Mapping Declaration mechanism — an organisation cannot yet file its own declared mapping to convert a shadow row into a confirmed one.
• Meta descriptions were deliberately left empty rather than hand-written for all 58 elements (matching the house rule for dictionary_term: never send the full operational definition as a SERP snippet) — each falls back to Layout.jsx's render-time truncation. A future release should replace these with real, short, per-element SERP copy.