Directory structure

Layout

.
|-- .github/workflows/
|-- bin/sealion
|-- docs/engineering/
|-- docs/site/
|-- examples/hello/
|-- include/sealion/
|-- include/sealion/ui/
|-- infra/compose/
|-- infra/schemas/
|-- scripts/
|-- src/
|-- src/ui/
|-- templates/default/
|   |-- src/main.c
|   `-- view/
|-- tests/fixtures/
|-- tests/integration/
|-- tests/regression/
|-- tests/unit/
`-- install.sh

Ownership

• .github/workflows: CI and documentation deployment.
• bin/sealion: installable CLI entry point.
• docs/engineering: source-of-truth engineering plans.
• docs/site: static GitHub Pages artifact.
• examples: generated or hand-written sample apps.
• include/sealion: public C headers.
• include/sealion/ui: public component and style-system APIs.
• infra: Compose templates and infrastructure schemas.
• scripts: repo-owned checks and maintenance commands.
• src: framework implementation.
• src/ui: component rendering, utility parsing, token resolution, and CSS generation.
• templates/default: starter app used by sealion new and sealion init.
• templates/default/view: editable starter HTML templates rendered by the generated C app.
• tests: fixtures, unit, integration, and regression coverage.
• install.sh: GitHub URL installer.

Rule

Empty directories are placeholders until a real file belongs there. When a directory gains behavior, its first file should make that behavior testable.