Repository layout

Top-level surfaces

research.nu

Nushell orchestration for registered research documents and reproducible research builds.

ydmp/

YDMP research workspace templates, models, notes, and supporting research infrastructure.

design/

Pinega Strata canonical tokens, generated cross-platform adapters, Scientific Diagram Language models/layouts, and design tests.

web/

Static multi-page Web platform, native HTML content, Web Components, build scripts, tests, and generated site output.

docs/

Repository-level architecture, audit, workflow, and implementation records that are not themselves the public Web article bodies.

.github/workflows/

CI gates and review-artifact workflows.

Web workspace

web/pages/

Durable semantic HTML for public pages and nested documentation articles.

web/content/

Versioned route, discovery, maturity, and documentation metadata contract; it does not own article prose.

web/src/

CSS, progressive-enhancement Web Components, and shared client-side behaviour.

web/scripts/

Static build, local serving, and build-validation scripts.

web/tests/

Unit/architecture, multi-browser/accessibility, and visual-regression gates.

web/dist/

Generated output. It is a build product, not an authoring source.

Canonical versus generated

Canonical source and generated output must not be confused. For example, Strata tokens originate from the canonical design-token source and generate CSS/TypeScript/Typst adapters; Web article prose originates in native HTML and generates dist pages; documentation discovery records originate in content-index.json and generate navigation/card/manifest projections.

When paths disagree with documentation

Inspect the current repository and the content/research registries before assuming an older path remains valid. Repository state is authoritative for what exists; accepted architecture records govern intended boundaries.