PASTE THE THREAD.
KEEP ONE RECORD.

Five steps from pasted thread to a reconciled project

Dashboard banners: AI Processing while unparsed; Parsing Failed if still unparsed after 30 minutes. Inline status edits write am_updates.

Thread in, banner while Ollama runs

CSS mock — not AWS Console. Not a screenshot of Gmail.

Clarifications are first-class

unknown_owner, low_confidence, contradiction, naming_collision.

Cutover-complete is an event, not a tweet

MaintWindow + Herald. Telegram function may no-op. Do not fake a Telegram screenshot.

JSON-mode truncates long threads

The extractor is Ollama-only because this blueprint historically has no OpenRouter key. Do not “upgrade” it to MiniMax in the landing copy.

No cross-user projects. No blocking gunicorn.

Will not parse in-request for 180s. Will not clobber a human-edited field. Public landing lists no thread bodies.

The DCIS migration operator

People drowning in reply-all who still need one golden record. Not a generic email client.

The same product, without the mock chrome

The problem is not “Jira but for AWS.” The problem is a DCIS on-prem → AWS migration whose source of truth is email. This tracker pastes a raw thread (subject from Subject:), runs local Ollama (gemma4:26b then qwen3:latest) with pipe-delimited extraction — not JSON-mode, not cloud Claude — in a daemon thread (2–3 minutes). Ingest returns immediately. A Python reconciler merges action items, decisions, validation targets, people; protects manual edits; raises clarifications (unknown_owner, low_confidence, contradiction, naming_collision). Seeded sample: DCIS on-prem → AWS. Per-user owner_user_id. Cutover-complete when the last open action is done fires MaintWindow, Herald, and a Telegram call that is a no-op without tokens — treat Herald as the live ping. Health has no DB. URL prefix /aws-migration/ (folder aws_migration).

Dashboard banners: AI Processing while unparsed; Parsing Failed if still unparsed after 30 minutes. Inline status edits write am_updates. /aws-migration/app/projects. Ownership checked on every app/API route. Subject auto-detected. Ingest returns; parse is background. Pipe-delimited Ollama output. Not a MiniMax call. Not Claude. Match titles/workstreams, skip manual edits, dedup decisions, upsert validations, resolve aliases. Pinned questions resolve/dismiss. AI status report HTML/PDF from DB state. Last action done → handoff events.

No invented AWS org chart importer. Paste; Subject: detected. gemma4 then qwen3; pipes. Daemon thread; live banners. Python merge + manual-edit lock. Four question types pinned. am_updates on every change. HTML/PDF from current DB. owner_user_id on all routes. MaintWindow + Herald.

How you verify: login, open seeded DCIS project or create one, paste a tiny thread, watch processing banner, confirm items appear, edit status, confirm audit. Hit health no DB. Confirm /aws-migration/ public. Confirm parse is not MiniMax. Confirm Telegram is not required for Herald handoff.

Ingest, extract, reconcile, report

No invented AWS org chart importer.