Credits¶
The Canadian Space is built on the work and generosity of many people and projects. This page is our way of saying thank you.
People¶
Chris Carpenter — Founder, curator, editor, and the human making final calls on what gets published. Keeps the lights on and the quality high.
Robo Chris — Our curator persona and the first voice you hear in every briefing. Robo Chris sources the stories, drafts the pitch, and hands them off for review. (Meet Robo Chris →)
Data sources¶
We're grateful to:
- Spaceflight News API (SNAPI) — Real-time aerospace news aggregation curated by industry experts
- Launch Library 2 API — Maintained by The Space Devs, a volunteer community dedicated to space data
- Wikipedia — Historical context and fact-checking for every topic
- SpaceQ and curated RSS feeds — Niche coverage and regional aerospace news
LLM providers¶
Our content wouldn't exist without:
- Alibaba Qwen — Primary author for daily broadcasts and weekly / monthly reports
- Anthropic Claude — Author fallback (Haiku 4.5) when Qwen errors or stalls, and the workflow-assembly assistant Chris uses to build and debug pipelines
- OpenAI — Fact-checker / editor (GPT-5-mini) that verifies claims and tightens SEO on every draft before it's published
- xAI Grok — Social media caption writer for Facebook and Instagram
- OpenRouter — The unified API making the model routing possible
Open source¶
We build on giants:
- n8n — Open-source workflow orchestration engine, the heartbeat of TCS
- MkDocs and Material for MkDocs — This wiki
- Caddy — Modern reverse proxy and TLS terminator
- Docker — Containerization for reproducible deployments
- Python, JavaScript, and countless libraries that power our data pipeline
The whole picture¶
The Canadian Space is human-and-AI collaboration. We synthesize signal from noise—taking hundreds of aerospace stories from multiple sources, routing them through LLM models trained by teams of engineers and researchers, and publishing what we think matters most.
Every person and project above made that possible.
If you've contributed to TCS and aren't listed here, let us know. We want to make sure everyone gets proper credit.
Email [email protected] or open an issue on GitHub.