OntologyVersion 2.4 · Personal standard
11 / Agents & Adoption
BS"D
System index

11 / Reference

Agents &
Adoption.

The same versioned contract serves people and agents: inspect the canon, adopt the assets, validate the result, then preserve the evidence.

Status
Canonical · 2.4.0
CLI
ontology check
Agent
Skill + read-only MCP
Authority
design-system.json

11.1 / Adoption contract

Inspect, install, implement, validate.

Agents never infer the current house style from screenshots or memory. They read the manifest and skill, consume the local assets, and run the shared checker before handoff.

What improves

Hierarchy, cross-media coherence, diagrams, operational legibility

Inter and Plex Mono behave consistently across web, document, and film. The same semantic fields and token set can travel.

What changes

Less literary warmth, more structural severity

Playfair, Newsreader, cream, and amber recede. Personal warmth must come from writing, subject, imagery, and material—not a default serif.

11.2 / Applied artifact contract

The system travels with proof.

Every implementation declares the exact Ontology release, profile, semantic signals, interactions, and verification scope in one schema-backed manifest.

Static gate

ontology check <path>

Validates visual constraints, manifest structure, release hash, signal meaning, and tab relationships. Unclassified green fails closed.

Rendered gate

npm run audit:surface -- <path>

Exercises both themes at all five canonical widths, then checks WCAG, local fonts, overflow, targets, visible labels, and declared keyboard interactions.

Start from examples/applied-artifact/. Reuse patterns/tabs.js for tab behavior and validate artifact.json against schema/applied-artifact.schema.json.

11.3 / Migration map

Preserve identity. Adopt system. Retire drift.

Each decision names what moved and why. Provenance is explicit; the canonical boundary is now settled.

01

Ontology name

Keep the personal system’s name and role as Clark’s canonical design language.

Preserve
02

BS"D

Retain as a quiet authorship and worldview marker in personal system surfaces.

Preserve
03

Inter role hierarchy

Use 800 for short uppercase monuments, 700 for sentence-case theses, 500 for display and claims, 400 for headlines and body, and 300 only for oversized ledes. Select monument or thesis by semantic load, never by taste.

Adopt
04

IBM Plex Mono

Use for labels, indices, technical state, ledgers, dates, and specifications.

Adopt
05

Black / white / silver

Replace the warm paper/carbon pair as the canonical foundation.

Adopt
06

Signal Green

Replace amber as the single semantic accent across current and verified state.

Adopt
07

Briefing Paper

Keep #F7F7F4 as an editorial application field, not the global canvas.

Adapt
08

Claim + proof composition

Use asymmetric editorial statements beside semantic diagrams, ledgers, or source visuals.

Adopt
09

Recipient briefing anatomy

Keep it inside briefing products; do not make every website follow its linear sequence.

Bounded
10

Transformative wordmark

Remain outside the personal system. Rules transfer; corporate identity does not.

Exclude
11

Playfair / Newsreader / amber

Retire from the canonical personal system; preserve only in legacy or explicitly literary artifacts.

Retire
12

Soft cards and dashboard chrome

Remove where present. Prefer fields, rows, rules, and negative space.

Retire

11.4 / Verification gates

The standard must keep proving itself in real artifacts.

Canonical status is a responsibility, not an exemption from review. Every application must show that the system improves the actual work.

  1. 01

    Personal writing surface

    Rebuild one essay or note where warmth matters and confirm the sans-serif system still feels personal.

  2. 02

    Operational document

    Apply it to a real decision memo or working packet and test whether the claim/proof grammar improves comprehension.

  3. 03

    Private briefing

    Use the exact current packet system and inspect desktop/mobile reading, gate boundary, and embedded film.

  4. 04

    Narrated film

    Produce one new film from the shared token set and verify semantic visual quality at player scale.

  5. 05

    Agent implementation

    Give the machine-readable contract to a new agent and see whether it reproduces the system without visual coaching.

11.5 / Profile boundary

One default, two explicit document lanes.

Ontology 2.4 remains the default for strategic, technical, product, briefing, and film work. Literary serves sustained reading; Working Paper serves quiet alignment notes, letters, terms, and decision memoranda.

Default lane

Structural

Inter, Plex Mono, black/white/silver, semantic green, claim/proof composition.

Editorial adaptation

Reading

Briefing Paper, wider leading, centered thesis mast, flush-left modules, dark system fields.

Bounded profile

Literary

A named serif mode for books, Torah, ritual, memory, or genuine long-form reading.

Bounded profile

Working Paper

A quiet mono document voice for alignment, terms, letters, decisions, and provisional work.

Ontology 2.4 is canonical. Literary and Working Paper are bounded profiles, not alternate defaults. Changes to either boundary require an explicit versioned decision.