Ways of Working
Status: Active Owner: @bilal Last Updated: 2026-02-17
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
Two Tracks
All work runs on two parallel tracks. They feed each other but are prioritised independently.
| Track | Owners | What | Tracked In |
|---|---|---|---|
| A: Engineering | @bilal, @deen | Product development, AI pipeline, infra, quality | Backlog, Active Work, TASKS.md |
| B: Business & Ops | @danny, @bilal | Pricing, packaging, GTM, onboarding, support, scaling | plan and session outputs |
Track A ships code. Track B ships decisions. Neither waits on the other, but they sync at natural touchpoints (capability informs pricing, customer feedback drives roadmap).
See Session Plan for the full Business & Ops session schedule.
How We Track Work
| Level | Track | Where | What |
|---|---|---|---|
| Strategy & priorities | Both | This vault → Backlog | What matters and in what order |
| Active focus | A | This vault → Active Work | Engineering work in progress |
| Business sessions | B | This vault → Session Plan | Session schedule, outputs, decisions |
| Code-level tasks | A | Linear | Implementation tickets and issue tracking |
| Decisions | Both | 01-Architecture/ADRs/ | Why we chose X over Y |
| Slide decks | B | presentations/ | Visual outputs from sessions |
Linear is the primary work tracker for engineering. Lightweight setup — no heavy process, just issue tracking and status updates.
Workflow
- Pick work from Linear (or Backlog for strategic priorities)
- Move it to Active Work with your tag
- Do the work in
envo-dashboard/, track progress in Linear - 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.