Bossman
Autonomous Work Contract

Execution Plan

This is the standing agreement for how Codex can keep building Bossman through bounded slices without asking Jason to approve every small step.

Current Objective

Build Bossman into the human-first cockpit for fleet site truth, standards, evidence, priority, actions, and agent-safe operations.

Human first Agent safe Repo owned

Next Slice

Upgrade the Sites page into the main working surface for accepted sites, with priority, repo, lifecycle, and source information.

Sites Priority tiers

Completion Rule

Implement a focused slice, run preflight, commit and push when green, verify production, then continue to the next ordered slice unless blocked.

Preflight Deploy verify

Ordered Slices

Slice 1

Improve the Sites surface so the 25 accepted sites are readable and useful.

Slice 2

Add manual priority tiers for accepted sites.

Slice 3

Publish or verify live /bossman-site-manifest.json files for accepted sites.

Slice 4

Import fleet standards and per-site applicability.

Slice 5

Add compliance evidence summaries to each site.

Slice 6

Build the action queue for standards failures, drift, and follow-ups.

Slice 7

Add scheduled refreshes for manifests, standards, and evidence.

Slice 8

Add evidence-led priority signals from traffic, leads, and quote data.

Autonomy Allowed

Edit Bossman code, tests, docs, and views.

Run format, static analysis, tests, and preflight checks.

Commit and push focused green slices to main.

Let Forge auto-deploy from pushed commits.

Verify production pages and agent APIs after deploy.

Use protected Bossman APIs to import evidence into staging.

Create proposals from trusted repo manifests and system-owned evidence.

Approve low-risk proposals that match accepted source contracts and do not conflict with accepted truth.

Stop And Ask

DNS, Synergy, registrar, server, billing, or provider changes.

Creating, rotating, or exposing secrets or production env values.

Deleting production data or destructively rewriting accepted truth.

Approving proposals where evidence conflicts with existing accepted truth.

Changing customer quote flows, booking flows, or live payment behavior.

Broad UI/product direction changes not covered by the ordered slices.

Failed tests, failed deploys, or unclear production behavior when the fix is not obvious and low risk.

Repo Source

The durable markdown version lives at docs/autonomous-execution-plan.md.