BetterFleet Workflow

This file is the repository-level workflow entrypoint for Codex sessions and future Symphony-style automation. It intentionally stays short. The human operating model lives in Product Development System, with a compact visual companion in Workflow Map.

Runtime Contract

Before acting:

1. Start from the relevant Linear item when one exists.
2. If the work is new or unowned, create or request one Linear triage issue before turning it into a challenge, project, or implementation plan.
3. Confirm the route: support/bug, incident, small fix, process/docs, governed product, or explicit opt-out.
4. Keep Linear aligned with the work actually happening: active item, owner, status, blockers, and remaining gaps.
5. Use the target repo instructions for implementation and verification.
6. Update shipped-output artifacts when needed: tests, ADRs, release notes, help docs, operational docs, and MR/release evidence.
7. Hand off with concise verification evidence and the current Linear state.

For governed product work, do not treat a Linear issue alone as enough context unless triage has deliberately waived the normal path. Confirm the chain:

1. Index challenge.
2. Linear Project specification.
3. Active Linear issue.
4. Target repo instructions and code.

If a required upstream artifact is missing, shape that stage or produce a shaping handoff instead of guessing scope.

Drill Down

Use these docs for details:

• Product Development System: core operating model for all BetterFleet work.
• Workflow Map: compact visual overview.
• Work Intake and Weekly Planning: Linear triage, backlog, cycle planning, and self-serve pickup.
• Product Engineering Workflow: governed product route.
• Product Engineering Workflow in Linear: Linear Project, issue, estimate, dependency, cycle, and status rules.
• Product Engineering Delivery: delivery evidence, done conditions, and staging validation.
• Release Notes: shipped-scope release communication.
• In-App Docs Authoring: product help-doc updates.
• GitLab Feature Flags: staged rollout, release-note handling, help-doc timing, and retirement.

Symphony Placeholder

Future Symphony configuration can attach tracker, workspace, hook, agent, and runtime metadata here. That configuration must point back to the same operating model instead of creating a second process.