Artifact routing
The site is unified; the underlying executable artifacts can still use the shipper that best fits their technical surface.
Canonical static site, roadmap, case studies, methodology and downloadable proof assets.
Frontend-heavy interactive diagnostics or demos that benefit from Git-based previews.
Proof-stage FastAPI/Postgres services where the backend behavior itself needs to be inspected.
CLIs, packages, benchmarks, fixtures, tests and tagged downloadable releases.
| Artifact | Primary surface | Ship gate |
|---|---|---|
| Case study / journey documentation | This site | Claim links to evidence; limitation explicit |
| Interactive diagnostic | Vercel or Netlify | Direct route works; real input/output is understandable |
| CLI / benchmark / test harness | GitHub | Quickstart works; tests pass; fixture/reproduction included |
| Backend/API integration | Railway + GitHub | Health check, environment contract, seed/demo path |
| KPI / operating ledger | Download from this site | No private data; formulas/claims verified |