Company
For the people building
Clone it, run the gates, read the reasoning. The system explains itself.
Quickstart
From clone to a running site, in the order that matters. Quoted from QUICKSTART.md at the repo root.
1. Install
npm install cd website && npm install2. Verify tokens (order matters)
npm run tokens:build npm run tokens:test3. Regenerate identity
node brand/logo/scripts/generate-mark.mjs node brand/logo/scripts/validate-svg.mjs node brand/logo/export.mjs4. Run the website
cd website npm run lint npm run typecheck npm run build npm run dev
Gates
Every gate that runs in CI, runnable locally with the same command.
| Gate | Command | Checks |
|---|---|---|
| tokens:test | npm run tokens:test | 9-test suite incl. machine-verified WCAG contrast matrix, both themes |
| validate-svg | node brand/logo/scripts/validate-svg.mjs | SVG masters are well-formed and match construction geometry |
| check-links | node tokens/scripts/check-links.mjs | wikilink + relative-link integrity across every vault markdown file |
| lint | npm run lint | ESLint (next/core-web-vitals + typescript), zero errors |
| typecheck | npm run typecheck | tsc --noEmit, strict mode |
| build | npm run build | production static export to website/out/ |
Repository
- github.com/Rubal-Systems/Eyenus
- Architecture overview:
ARCHITECTURE_OVERVIEW.mdat the repo root — data flow, directory map, where to start reading. - Contributing:
CONTRIBUTING.md— authority chain, tokens-are-law rule, commit conventions, the ADR process. - How the platform is engineered →