AUTHORING + INTERCHANGE CONTRACT · SCHEMA VERSION 3

Write meaning.
Render many ways.

A lesson is an ordered set of semantic learning scenes, typed evidence and assessment artifacts, and inspectable local media. Screen layout is derived; the reviewed source remains portable.

01 / ARCHITECTURE

One reviewed source drives every rendered view.

One reviewed source. Several faithful views.

01 · AUTHOR

Semantic source

Constrained MyST-compatible Markdown carries teaching prose. JSON carries identity, sequence, objectives, assessment logic, claims, sources, glossary, and provenance.

  1. lesson.json
  2. content/*.md
  3. Typed JSON artifacts
  4. Local inspectable assets
Canonical and reviewable
02 · COMPILE

Bounded build

Validated directives become trusted semantic templates. TeX and \ce{...} compile to MathML; diagram JSON and sanitized SVG remain non-executable.

  1. Schema validation
  2. Pack-path isolation
  3. HTML sanitization
  4. Deterministic artifact
No contributor code execution
03 · READ

Adaptive outputs

The SPA presents book-like scenes and stable navigation. The same semantics can reflow for narrow screens, assistive technology, print, and future exports.

  1. Interactive web reader
  2. Accessible document flow
  3. Typst / LuaLaTeX target
  4. EPUB, DOCX, JATS targets
Web implemented · exports planned
02 / LESSON PACK

A lesson pack is a small repository inside the repository.

Everything a reviewer needs travels with the lesson.

The manifest is the table of contents. Scene filenames aid humans; stable scene IDs and array order govern links, corrections, assessment mappings, and rendering.

  1. Manifestlesson.json: identity, graph outcomes, objectives, ordered scenes, duration, rights, authorship, and agent provenance.
  2. Teachingcontent/*.md: one bounded instructional purpose per scene, with no front matter, raw HTML, JavaScript, or executable plugin.
  3. Learning evidenceassessment.json: outcome-aligned prompts, answer reasoning, feedback, rubric, retakes, and recovery.
  4. Scholarly evidenceEvery scene declares its claim coverage. Learner-visible source notes map material claims to exact records in references.json, including scope, uncertainty, and review state.
  5. Languageglossary.json gives stable definitions, symbols, aliases, and scene references.
  6. Rights + decisionLocal assets, ATTRIBUTION.md, independent reviews, and separate adjudication.json travel with the lesson.
03 / SEMANTIC SCENES

Instructional purpose, not layout, defines a scene.

Purpose defines a scene. Pixels do not.

  1. 01

    Orient + diagnose

    orientation and diagnostic establish relevance, boundaries, prerequisites, and recovery routes.

  2. 02

    Build the model

    concept, definition, derivation, and investigation make reasoning explicit.

  3. 03

    Show reasoning

    worked-example exposes representation, decisions, execution, checks, and interpretation.

  4. 04

    Practice + repair

    retrieval-check, misconception, and practice provide feedback without one-shot penalties.

  5. 05

    Transfer + synthesize

    transfer, synthesis, assessment, and references connect mastery to the wider graph.

04 / SCIENTIFIC MEDIA

Scientific media stay inspectable and accessible.

Equations are source. Images carry meaning.

Math + chemistry

Constrained TeX remains copyable source. Display math uses an {equation} directive; chemistry uses \ce{...}. The current build produces accessible MathML and rejects file, macro, HTML, link, and resource-loading commands.

Diagrams + data

Format v1 uses schema-valid *.diagram.json for bounded processes and relationships. Mermaid, DOT, and Vega-Lite may become generated adapters only after validators and deterministic renderers exist.

Scientific images

Sanitized local SVG or raster assets include provenance, meaningful alt text, and a long description when relationships cannot fit in a short alternative. Color and position never carry the only meaning.

05 / LEARNING CONTENT

Lessons pair clear explanation with generative practice.

Clarity builds a model. Practice makes it usable.

GROUND

Declare the learner

Define outcomes, prerequisites, the target explanatory model, likely learner ideas, mastery evidence, and recovery route before drafting polished prose.

EXPLAIN

Expose relationships

Use coherent causal or relational prose, stable terminology, relevant evidence, explicit assumptions, and connected representations. Difficult ideas stay difficult; hidden inference gaps do not.

MODEL

Show expert decisions

Worked examples reveal representation, model selection, plan, reasons, checks, and interpretation. Completion problems then fade support toward independence.

GENERATE

Retrieve before reveal

Learners recall, explain, predict, compare, calculate, or construct before feedback. High-value knowledge returns after a delay and in changed contexts.

DISCRIMINATE

Compare, repair, transfer

Contrasting cases expose boundaries, evidenced misconceptions receive refutation and a replacement model, and transfer requires selection or adaptation—not changed numbers alone.

VERIFY

Audit the learning claim

Accuracy, accessibility, rights, and deterministic validation are gates. Completion, readability scores, interaction count, model agreement, and agent self-review are not evidence that students learned.

Authoritative writing contract: read the complete Learning-Content Standard v1. Its dated evidence synthesis distinguishes robust defaults from conditional findings; Lesson Format v1 remains the separate storage and rendering contract.

06 / BOUNDARIES

Lesson content is accessible by design and treated as untrusted data.

Accessible by design. Untrusted by default.

ADAPTIVE READING

No-body-scroll is a shell rule

Desktop navigation stays fixed while a semantic scene owns bounded overflow. Mobile, zoomed, print, and assistive layouts may reflow normally; authors never encode viewport dimensions.

SAFE CONTRIBUTIONS

Lesson content is data

Raw active content, remote embeds, executable notebooks, path escape, unsafe SVG, and contributor-controlled build code are rejected. Validation never executes lesson code.

PUBLICATION

Format is not approval

A valid standard pack remains a candidate until two isolated reviews inform one fresh finalization and adjudication. The specimen below never counts toward published coverage.

SOURCE RIGHTS

Evidence is not permission

Authors independently synthesize facts instead of closely paraphrasing sources. Any quotation, adaptation, media, or dataset reuse needs a compatible recorded rights basis; agents must honor source-specific access terms. Read the source and reuse policy.

REFERENCE IMPLEMENTATION

Inspect the source.
Then open the book.

  1. The machine contract is public as JSON Schema 2020-12 under /schemas/.
  2. The specimen source pack lives at examples/lesson-pack/ and is validated separately from production.
  3. The build deterministically compiles eight source scenes, MathML, a typed diagram, an SVG image, assessments, claims, references, and glossary data.
  4. The interactive reader consumes that generated artifact; it is not a second handcrafted lesson.
  5. Premed remains at 0 contributed and 0 published lessons because examples never enter the production ledger.
Open the Format specimen