Initial MobilityOps build pack (docs, contracts, scaffold)

START_HERE.md

@@ -0,0 +1,39 @@
+# MobilityOps — Claude build pack
+
+MobilityOps is a deliberately scoped, working proof of concept for a fictitious Belgian mobility-rental company. It demonstrates how operational data, workflow automation, data-quality review, a central RAG service and a central MCP hub can work together without pretending to be a full ERP.
+
+## Use this pack efficiently
+
+1. Extract this archive into a new repository.
+2. Open the repository in Claude Code.
+3. Paste the contents of `MASTER_BUILD_PROMPT.md` once.
+4. Let Claude continue autonomously through the milestones in `docs/15-build-plan.md`.
+5. Only intervene if the environment itself is unavailable or credentials for an external service are required.
+
+Claude must use `PROJECT_STATE.md` as its compact memory between sessions. Do not restate the full project in later prompts.
+
+## What is included
+
+- locked product scope and non-goals;
+- architecture and domain decisions;
+- API and event contracts;
+- realistic deterministic synthetic seed data;
+- ten fictitious procedures for RAGcore;
+- an initial n8n workflow export;
+- MCP tool definitions for ITWorx MCP Hub;
+- a minimal bootable frontend/API scaffold;
+- acceptance criteria and a five-minute demo script;
+- a master prompt optimized for one autonomous build run.
+
+## Core responsibilities
+
+| Component | Responsibility |
+|---|---|
+| MobilityOps | Operational data, business rules, UI, audit and data-quality review |
+| RAGcore | Document ingestion, retrieval and source-grounded answers |
+| ITWorx MCP Hub | Controlled AI access to MobilityOps tools and MobilityOps knowledge |
+| n8n | Cross-system orchestration after committed domain events |
+
+## Build principle
+
+Finish a small vertical slice completely. No placeholder pages, fake buttons, invented production claims or scope expansion.