Good evening, Z — Platform Steward; Director-A · Email Intake
18:05 MDTSubmitting as Director-A · zhvhoa@proton.me. One email per submission. Phase-0 routing: matches against DT-001 (Storm Limb Cleanup) by topic; anything else files to UNTHREADED rather than fabricating a new thread.
Submit one email
Paste the email body (with From: / To: / Date: / Subject:headers if present) OR upload a .eml file. The pipeline parses, writes evidence to lane/email_intake/<date>/EI-…, appends an entry row to DT-001.md, regenerates DT-001.state.json (the 8-field thread state), and emits a per-email cumulative inferability snapshot. Rolling summary stays operator-curated.
OR upload .eml files (one or many) — preferred path
Pick one or many .eml files. Each is read locally and its Date: header is extracted. Files are sorted ascending by that timestamp (with filename-timestamp fallback) and rendered below for you to verify before any submission. Only after you click Begin sequential ingestdo submissions start — one at a time, in chronological order, so DT-001 E# numbering matches the actual email chronology.
Submit a transcript (voice memo / markdown)
Paste or upload a .md transcript of a conversation or voice memo and link it to a topic. Persists under lane/voice_intake/<date>/VI-… as INTAKE / OPERATIONAL_CONTEXT — never an official board record or board action. Candidate tasks are extracted as PROPOSED chips on the topic page and are never auto-promoted to active. Audio is not stored.
What this surface does NOT do
- Bulk-ingest from Proton or any mailbox. (Single-submission only — Phase 0.)
- Auto-rewrite the rolling summary in DT-001.md. (Operator pen.)
- Promote a confidence label. (Doctrine §16 transitions only.)
- Expose raw homeowner-sensitive content on the dashboard. (Body excerpt is ≤140 chars; full body lives in seat-gated EI-…md.)
- Cross-route to threads other than DT-001. (Doctrine §13 — single thread for alpha.)