Jens/MobilityOps
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: sanitize MobilityOps operational evidence and public boundary #8

Merged
Jens merged 17 commits from chatgpt/repo-hygiene-mobilityops into master 2026-09-01 12:29:26 +00:00
Conversation 0 Commits 17 Files Changed 57
-21
1 changed files with 0 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 6fd1d5e5e9 - Show all commits
MASTER_BUILD_PROMPT.md
-21
View File
@@ -1,21 +0,0 @@
# Paste this once into Claude Code
Build MobilityOps autonomously from this repository.
First read `START_HERE.md`, `CLAUDE.md`, `PROJECT_STATE.md` and `docs/15-build-plan.md`. Treat the repository specifications and contracts as binding. Do not ask me questions that the files already answer, do not broaden the PoC, and do not stop after a milestone.
Implement the milestones in order. For each milestone:
1. read only the documents listed for that milestone;
2. implement the smallest complete solution;
3. run the specified validation plus relevant regression tests;
4. fix failures using evidence rather than guesses;
5. update `PROJECT_STATE.md` with concise evidence and the exact next step;
6. commit the completed milestone;
7. continue immediately.
MobilityOps owns operational data and business rules. RAGcore owns retrieval and grounded answers. ITWorx MCP Hub owns MCP publication and policy. n8n only orchestrates post-commit workflows. Use configurable adapters and working degraded modes so the core demo remains usable when any external service is absent.
The finished PoC must be reproducible from a clean checkout, have no dead UI, use deterministic synthetic data, support the documented five-minute demo, and satisfy every criterion in `docs/14-testing-and-acceptance.md`.
Keep chat output brief. Spend the available context on code, tests, validation and final evidence. Begin now and continue until the repository is complete.