BetterFleet Dev Wiki¶

Start from the task in front of you. The main entry points are the governed product-workflow docs, the current work set, and the recurring delivery guides.

JTBD Entry Points¶

Start Governed Work

The system-level entry point for governed product work.

Use it for the full model: quarterly prioritisation, discovery, definition, delivery, artifacts, reviews, and skill boundaries.

Work From A Story

The day-to-day operating path for developers and agents.

Use it to confirm Challenge -> Specification -> Story, stay inside the story boundary, and follow the governed path.

Execute Delivery

The delivery companion for ready work.

Use it for readiness checks, the delivery loop, staging validation, and done conditions.

Keep Linear Accurate

The BetterFleet Linear operating guide.

Use it when updating mirror status, checking readiness, estimating, or working from a Linear issue.

Find The Current Work

The live challenge, specification, and story sets.

Use it to find the current initiative slug and the canonical work artifacts behind the story you are picking up.

Handle Recurring Follow-Through

The recurring guides that sit alongside delivery.

Use it for release notes, in-app docs updates, and feature-flag rollout handling.

Common Starts¶

If you need to...	Start here
Understand the full governed system	Product Development System
Pick up day-to-day delivery work	Product Engineering Workflow
Deliver a ready story	Product Engineering Delivery
Update the Linear mirror	Product Engineering Workflow in Linear
Find the current initiative or story set	Active Work
Update release notes or docs follow-through	Process Guides
Look up stable implementation context	Reference
Check long-lived technical decisions	Decisions
Run or troubleshoot BFDev	Operations

Section Map¶

Section	Use It For	Start With
Process	Workflow rules, companion guides, templates, and publishing rules	Process Handbook
Work	Initiative-specific material that belongs to one work slug and can move through backlog, active, and archived states over time	Work
Reference	Product, platform, shared, system, and system-design knowledge	Reference
Decisions	Cross-product engineering decisions	Decisions
Operations	Onboarding, runbooks, troubleshooting, testing, tooling, and evidence	Operations

Place New Pages Correctly¶

Put it in Process when it explains how BetterFleet should shape, deliver, review, publish, or govern work.
Put it in Work when it belongs to one specific initiative or delivery slice and should travel with that slice from backlog to active to archived.
Put it in Reference when it describes stable facts or models that multiple work items may need to reuse.
Put it in Decisions when it records a ratified or ratifiable cross-cutting choice that should constrain future work.
Put it in Operations when it helps someone run, validate, diagnose, or support the BFDev environment or docs pipeline.

Direct Links¶

Run Locally¶

./docs/serve-wiki 8088
./docs/validate

Open http://127.0.0.1:8088.