Migration Notes

What changed from the previous repo state and what V1 explicitly does not promise yet.

From mixed-state repo to V1

The old repo had three conflicting stories:

• a Python MCP service,
• an unfinished multi-runtime “Universal AI Coding Agent” product,
• a stock nested Turborepo starter.

Documint V1 resolves that by centering one real product path:

• Next.js for the public site and dashboard,
• Python for backend orchestration and MCP,
• Git as the source of truth,
• Documint documenting itself first.

Explicit non-goals for the first public deployment

• no full visual CMS,
• no silent autonomous pushes to default branches,
• no enterprise-first compliance program,
• no promise that every historical Rust, Go, or VS Code experiment is part of the launch path.