swayfx-mosaic/docs
2026-10-10 08:33:34 +02:00
..
assets docs: establish canonical Spatial Canvas documentation 2026-10-10 08:33:34 +02:00
ARCHITECTURE.md docs: establish canonical Spatial Canvas documentation 2026-10-10 08:33:34 +02:00
DEVELOPMENT.md docs: establish canonical Spatial Canvas documentation 2026-10-10 08:33:34 +02:00
KNOWN_LIMITATIONS.md docs: establish canonical Spatial Canvas documentation 2026-10-10 08:33:34 +02:00
PACKAGING.md docs: establish canonical Spatial Canvas documentation 2026-10-10 08:33:34 +02:00
README.md docs: establish canonical Spatial Canvas documentation 2026-10-10 08:33:34 +02:00
ROADMAP.md docs: establish canonical Spatial Canvas documentation 2026-10-10 08:33:34 +02:00
STEP20A.md docs: establish canonical Spatial Canvas documentation 2026-10-10 08:33:34 +02:00
STEP20B.md docs: establish canonical Spatial Canvas documentation 2026-10-10 08:33:34 +02:00
UPSTREAM.md docs: establish canonical Spatial Canvas documentation 2026-10-10 08:33:34 +02:00
UX.md docs: establish canonical Spatial Canvas documentation 2026-10-10 08:33:34 +02:00

Documentation

Documentation is a first-class project artifact. Architecture and UX contracts are updated before implementation when behavior changes.

The root README is the public summary. For a specific topic, use the canonical document below. Within its own subject, a canonical document takes precedence over a historical STEP report. If two canonical documents disagree, resolve the conflict before implementation; do not silently choose one.

Source-of-truth order

  1. Architecture: compositor ownership and technical invariants.
  2. UX contract: user-visible behavior and interaction invariants.
  3. Packaging: binary and package coexistence.
  4. Upstream maintenance: provenance and forward ports.
  5. Development: reproducible workflow.
  6. Known limitations: current support boundary.
  7. Roadmap: ordered future work, not proof of implementation.
  8. STEP20A and STEP20B: historical evidence.

Project

Document Role Purpose
README Summary Public landing page and current status
Contributing Normative Scope, docs-first flow, checks
Changelog Historical Repository evolution
Notice Normative Attribution boundary

Architecture and user experience

Document Role Purpose
Architecture Normative Runtime model, ownership, IPC, transactions, scene
UX contract Normative Interaction rules, row behavior, undecided choices
Known limitations Planning/current evidence Unsupported and unvalidated paths

Development, packaging, and upstream

Document Role Purpose
Development Normative Build, test, staging, patch workflow
Packaging Normative File ownership, versioning, fallback
Upstream maintenance Normative SwayFX relationship, pinned base, forward ports

Roadmap and historical reports

Document Role Purpose
Roadmap Planning Step goals, exit criteria, required documentation
STEP20A Historical Native foundation implementation evidence
STEP20B Historical First scrollable-row implementation evidence

STEP reports record what was observed and decided at the time. They are not the canonical source for current behavior. When a STEP report conflicts with current canonical documentation, the canonical documentation wins. The original French reports are preserved as historical artifacts; their opening notices point here.