How to Import an AI-Generated Plan Into Minty Path

Two routes, and the difference is privacy

There are two ways to get an AI-generated plan into Minty Path, and they differ in whether anything of yours leaves the app.

Prompt-only. Minty Path builds a prompt. You paste it into whichever assistant you use. You bring the result back as CSV. Minty Path never contacts a model and nothing of yours is transmitted by it. Works with any assistant, needs no account with a provider, available without configuring anything.

Connected. A signed-in user connects their own OpenAI, Anthropic, or Google Gemini account, and Minty Path calls the provider directly using that user's own credits. Fewer steps, and the AI can read the Growth Path context you select for the workflow.

Neither route applies anything without your review. There is no configuration in which generated structure lands in your workspace unexamined.

The CSV format

Whichever route produced it, the structure arrives as CSV with these columns:

id, parent_id, title, description, status, area, priority, evidence

id and parent_id define the hierarchy explicitly, which is why CSV beats indented text — no ambiguity about whether four spaces meant one level or two. A row with an empty parent_id is a top-level branch.

Ask for exactly these columns when prompting. Assistants produce them reliably when named.

What the server checks before anything is created

Preview is mandatory, and it is a real validation rather than a display step. The import is rejected if:

• Any id is duplicated
• A parent_id points at a row that does not exist
• The parent references form a cycle
• Status or priority values are outside the accepted set
• Total branch count or maximum depth exceeds the limits

So a malformed generation fails cleanly at preview instead of half-importing and leaving you to clean up a broken tree. The whole import then runs in a single transaction — it either completes or it does not happen.

Import always creates a new Growth Path. It never overwrites the map you are currently looking at.

The evidence rule

Worth understanding before you prompt, because it changes what you should ask for.

If a row claims a completed status, Minty Path accepts that only when the evidence column actually contains something. Rows claiming work is already done, with no evidence, import as in-progress instead.

This exists because models generate plans in which portions are conveniently already finished. That is a judgment about your life the model is not in a position to make. A branch reaching Proven requires real proof, and a generated CSV does not get an exemption.

Setting up the connected route

If you want Minty Path calling the provider directly:

Provider credentials are encrypted under a versioned server keyring held outside the web root. They are never returned to the browser, and they do not appear in exports, diagnostics, or backups — once stored, there is no path that reads them back out.

Proposals are one-time and expire. You approve them change by change rather than accepting a batch. If the Growth Path has been modified since the proposal was generated, the stale proposal is rejected rather than applied over your newer edits. Ownership is rechecked at application time, and generation is rate-limited per account.

What the AI can and cannot see

In this first release, the model is given structure and not much else. Private Details, branch attachments, Notes, Todos, Proof, and Reminders are all held out of AI context entirely.

That is a real boundary, not a roadmap item. Private Details in particular are encrypted in your browser with your own passphrase — Minty Path stores ciphertext and could not send the plaintext anywhere if it wanted to.

After the import

The map arrives. It is a first draft written by something that did not know your situation, so:

Delete first. Usually a quarter of it. Generated maps are evenly balanced and include branches that are common rather than applicable.

Fix the first level. Ask of each top-level branch: could this fail for its own reasons? If it fails only because a sibling failed, it belongs inside that sibling as a Todo.

Set Focus to one to three branches. Nothing generated sets Focus, and it should not — that is the decision the whole map exists to support.

Add what it could not know. The constraint you did not mention, the thing you already tried, the branch you have been avoiding. That material is the difference between your map and the average one.

If you have not tried the workspace yet

Understanding what a good map feels like makes reviewing a generated one much faster. Open the workspace without an account — the real Plan View and Work View, in your browser, no signup — and build something small by hand first.

Current connected workflows

Connected Path Assistant workflows can create or improve a Growth Path, organize selected Inbox items, hold a durable conversation about one Path, and run optional advanced research. Every proposal remains reviewable before it changes the workspace. Scheduling is deliberately left to calendar and scheduling tools.