Start here
Start here
Your first stops live on the wiki. Open these in order — access, then the first-week checklist, then everything you might get stuck on.
🌱
Start here
The landing page for new joiners — what this program is and where to go next.
✅
First-week checklist
A day-by-day list to get you from account request to productive.
🔑
Access & accounts
Which accounts you need, who grants them, and how to ask.
🧰
Prerequisites
The tools to install and configure before your first task.
💬
FAQ
The questions every joiner asks — answered once, here.
Know the ground
Know the ground
Read the source. These are the repo documents that tell you how the team works, what the words mean, and how to add your own pages.
📜
Team charter
What the team is for, how it operates, and what it commits to.
📖
Glossary
Every term, acronym and codename used across the program.
🧭
RACI — who owns what
Responsible, accountable, consulted, informed — find your row.
🌿
How to contribute
Branch, edit, validate, open a PR — the way we change the wiki.
✍️
Style guide
How we write pages so they read as one voice, not many.
🏷️
Front-matter standard
The metadata every page carries — and why the validators enforce it.
Your first week
Your first week
Work down this list in order. By the end you can run the wiki locally, know who owns what, and have driven the pipeline once yourself.
Germination checklist
- Request your Azure / Entra account and repo access — start on day one, it takes the longest.
- Clone the wiki repo to your machine once your access lands.
- Run the docs site locally: cd docs-site && mkdocs serve -a 0.0.0.0:8086
- Read the charter and the glossary end to end — it is the fastest way to sound like you belong.
- Find your team in the RACI and note who you go to for each kind of decision.
- Skim the architecture plan so you know the shape of what we are building.
- Open the API console once (make serve) and drive the pipeline end to end.
- Skim the FAQ so you know where the answers already live before you ask.
- Open your first pull request — fix a typo, add a note — to prove the contribution loop works for you.
Tip: if a step blocks on access, keep going down the list — most of it runs offline against the repo.
Where to go next
Where to go next
Once you have found your footing, step into the working sections. Each one is a portal into a part of the program.
🌾
Silo · Monitoring
Everything we watch and store — Prometheus, Grafana, exporters and alerts across three regions.
Enter →
🚜
Tractor · Automation
The heavy work done for you — the auto-docs pipeline, adapters and a live API you can drive.
Enter →
💧
Irrigation · Workflows
The channels that carry the flow — n8n workflows, pipelines and the Terraform IaC modules.
Enter →