The single source of truth for oxFlow — a construction project management platform being built by 361 for Oxcon, covering the full lifecycle from tendering through project delivery.
This wiki holds every planning decision, piece of research, meeting note, daily log, and formal spec behind that work. If you want to know why the product looks the way it does, it’s here.
The basics
| Thing | Where |
|---|---|
| Wiki (you are here) | oxflow-wiki.design.3sixtyone.co |
| Static design hub (landing page, prototypes, presentation deck) | oxflow.design.3sixtyone.co |
| Source repo for this wiki | github.com/361-coders-nz/oxflow-hub (private) |
| Team roster | TEAM.md |
| Branding / visual system | BRANDING.md |
| Authoring rules for humans + agents | CLAUDE.md |
Start here — by role
If you’re new to oxFlow
Read in order:
- concept-map — the entity model in one diagram
- business-rules — numbered rules (
BR-019,BR-023a…) every downstream doc references - Progress — what’s decided, what’s in flight, what’s next
- Skim the decisions folder — four ADRs so far, all short
If you’re writing a doc (human or AI)
- Pick a template:
templates/README.md— one per doc type - Copy it to the right folder (
research/YYYY-MM-DD-slug.md,meetings/YYYY-MM-DD-slug.md, etc.) - Fill in frontmatter (the YAML block at the top — schema:
meta/frontmatter-schema.md) - Run
python3 meta/scripts/lint-wiki.py --check— exits 0 if clean - Open a PR against
maininoxflow-hub. One doc = one PR. Do not push to main directly.
If you’re an AI agent
Read CLAUDE first, then meta/frontmatter-schema.md. Those two files cover every rule. When in doubt, copy a neighbour — if you’re writing research, copy the most recent file under research/; if an ADR, copy the most recent under decisions/.
If you just want to browse
- Formal product model — docs
- Decisions — decisions
- Research — research
- Meetings — meetings
- Daily logs — daily
Using this wiki
This isn’t a flat doc site. Three features pay off if you learn them:
- Search. Press
/(forward slash) anywhere, or click the magnifying glass top-right. Full-text, instant. Try it withBR-019orneon. - Graph view. Click the graph icon (top-right). Every doc is a node; edges are links. Zoom out for a whole-corpus view, zoom in on any page to see its immediate neighbours.
- Backlinks. Scroll to the bottom of any page. You’ll see every doc that links to this one. Follow them to find context authors didn’t think to link forward.
Wikilinks. Anywhere in the body you can write [[business-rules]] and it resolves to the Business Rules spec regardless of which folder it lives in. Change the display text with [[business-rules|the rules]]. Business-rule IDs like BR-019 auto-link.
Sections map
| Section | What’s there |
|---|---|
| docs | Formal product specs — foundation (concept map, business rules, roles, NFRs), five entity layers, flows |
| decisions | ADRs — every non-trivial choice, with context, alternatives, consequences |
| research | Agent-written research writeups: database, infrastructure, agentic workflow, etc. |
| meetings | Cleaned transcripts from workshops and team syncs |
| daily | Daily to-do logs (one file per day, whole team) |
| prompts | Reusable prompts for running agents on this repo |
| raw-dumps | Unrefined research inputs — promote to research/ once cleaned |
| bmad | BMAD output synced from the real codebase repo (read-only) |
| Progress | Birds-eye view of what’s decided, shipped, in flight |
Contributing in one screen
# 1. Copy the right template from templates/
cp templates/research-note.md research/2026-04-21-my-topic.md
# 2. Edit frontmatter (title, date, author, status: draft, tags: [2, 3, tags])
# 3. Check yourself
python3 meta/scripts/lint-wiki.py --check
# 4. Open a PR against main in github.com/361-coders-nz/oxflow-hubFull details: CLAUDE and templates/README.md.