FlowMap — Explainable implementation map for vibe coding

After AI writes code, auto-generate an implementation map of who changed which business logic with which prompt

Problem

Teams using Loop and AgentTeam patterns can no longer explain their implementation; ask about the logic behind a feature and nobody can answer. One developer built seven desktop apps in two months, burning tokens happily, yet couldn't clearly explain how each feature was actually implemented.

Solution

A lightweight local recorder that sits beside the IDE/CLI, captures each AI coding session's prompts, changed files and key decisions, and distills them into a feature implementation map: every feature point carries the last person who touched it, the model and prompt summary used, and a traceable diff link.

Users

Small teams adopting AI-assisted development, tech leads, indie developers who need to explain implementation to non-technical stakeholders.

MVP

Runs locally and reads Claude Code / Codex history; clusters changes into feature modules; generates readable implementation notes and decision timelines per module; exports Markdown for non-technical colleagues; never modifies the repo.

Revenue

Free for individuals, per-seat subscription for teams; enterprise self-hosted plan with SSO.

Why now

AI coding makes output outpace team understanding, while existing tools only show diffs or commit history without explaining business logic; an indie developer can build the first version entirely from local files with no cloud infrastructure.