# Autonomous build plan

Claude must complete all milestones in one continuous run where possible.

## M0 — Reproducible foundation

Read: `README.md`, `docs/03-architecture.md`, `docs/04-domain-model.md`, `docs/14-testing-and-acceptance.md`.

Deliver:

- stable backend/frontend project structure;
- dependency lockfiles;
- Compose health and clean-checkout bootstrap;
- migrations framework;
- CI-friendly commands;
- initial lint/test gates.

Validate: clean build, API/web health, baseline tests.

## M1 — Operational core

Read: `docs/02-user-stories.md`, `docs/05-api-contract.md`, `docs/06-ui-ux.md`, `docs/13-seed-and-demo-scenarios.md`.

Deliver:

- demo authentication and authorization;
- deterministic seed import/reset;
- dashboard;
- vehicle and booking list/detail;
- audit foundation.

Validate: real persisted metrics, role tests, responsive smoke test.

## M2 — Vehicle return vertical slice

Read: `docs/08-return-workflow.md`, `contracts/events.schema.json`.

Deliver:

- complete transactional return command;
- idempotency and concurrency handling;
- status derivation;
- outbox record;
- result UI and audit.

Validate: success, odometer regression, replay, concurrent submission and rollback tests.

## M3 — Data Quality Workbench

Read: `docs/07-data-quality.md`.

Deliver:

- five rules;
- issue scan/lifecycle;
- duplicate comparison and transactional merge;
- issue UI and dashboard attention integration.

Validate: seeded scenarios, idempotent scans, merge rewiring and audit.

## M4 — n8n automation

Read: `docs/11-n8n-integration.md`, `n8n/README.md`.

Deliver:

- dispatcher with retry/backoff;
- working return workflow and callback;
- Automation UI;
- failed seeded run and manual retry.

Validate: n8n online success, offline pending behaviour, duplicate delivery idempotency.

## M5 — RAGcore knowledge integration

Read: `docs/09-ragcore-integration.md`, `knowledge/manifest.json`.

Deliver:

- provider interface;
- deterministic demo provider;
- RAGcore adapter against the actual available contract;
- Knowledge UI with source cards and honest states;
- document sync support when feasible.

Validate: grounded demo question, insufficient evidence, timeout/unavailable and source metadata tests.

## M6 — ITWorx MCP Hub publication

Read: `docs/10-mcp-hub-integration.md`, `contracts/mcp-tools.json`.

Deliver:

- protected provider APIs;
- registration/configuration documentation or automation compatible with the Hub;
- four validated read-only tools;
- service audit events.

Validate: tool schemas, authorization denial, sample Hub calls, no write or generic tool exposure.

## M7 — Portfolio polish and final acceptance

Read: `docs/06-ui-ux.md`, `docs/14-testing-and-acceptance.md`, `docs/16-portfolio-case-study.md`.

Deliver:

- remove rough edges and placeholders;
- complete Playwright demo;
- screenshots and architecture diagram;
- concise deployment/runbook;
- final evidence, version and case-study text.

Validate: all acceptance criteria from a clean checkout.