Ways of Working
Status: Active Owner: @bilal Last Updated: 2026-02-15
Principles
- Autonomy — Each person owns their area and moves independently
- IaC mindset — Automate and codify decisions, don’t rely on tribal knowledge
- Reasonable pace — Stable, safe, paced. No hype-driven development
- Ship small — Small, reviewable changes. Commit often
- Docs as code — This vault is committed to git. Decisions are written down
How We Track Work
| Level | Where | What |
|---|---|---|
| Strategy & priorities | This vault → Backlog | What matters and in what order |
| Active focus | This vault → Active Work | What’s being worked on right now |
| Code-level tasks | envo-dashboard/TASKS.md | Implementation tickets with IDs |
| Decisions | 01-Architecture/ADRs/ | Why we chose X over Y |
No Linear, no Jira. Three people don’t need ticket overhead. If we grow past 5-6 people, revisit.
Workflow
- Pick work from Backlog (top = highest priority)
- Move it to Active Work with your tag
- Do the work in
envo-dashboard/, track code tasks inTASKS.md - When done, update Active Work and Backlog
- If it’s a significant decision, write an ADR
Agentic Usage
This vault is designed to be read and written by Claude Code and similar tools:
CLAUDE.mdat the root tells agents how the vault works- Markdown is the native format — no proprietary tooling
- Agents can read context, update docs, and propose changes
- All changes are git-trackable
Communication Norms
- Default to async (write it down)
- Sync for: blockers, design reviews, anything faster said than written
- Tag people in docs with
@bilal,@deen,@danny - If it’s not written down, it didn’t happen
Publishing
Future: Vault will be published as a static site via Quartz on Cloudflare Pages. Internal docs visible to team, selected pages public.