Archive Bichon Communications with Stored Files and File References #6

New issue

Closed

opened 2026-06-14 10:21:21 +00:00 by liang · 1 comment

liang commented

2026-06-14 10:21:21 +00:00

Owner

Parent

Parent PRD: #2

What to build

Re-import Bichon email as Communication Archive evidence first. The ingestion path should preserve Communication Records and Communication Evidence, including raw/readable/html content when available, metadata, chunks, attachments, inline images, Stored Files, and File References. This slice deliberately stops before Project Matter classification and must not create Project Matters, Tasks, or Agent Memory.

Acceptance criteria

Bichon-like fixtures can be ingested into Communication Records with raw source, readable content, original HTML when available, metadata, and chunks.
Attachments and inline images are stored as Stored Files outside the database by content hash and connected through File References with original evidence roles.
Exact email addresses create lightweight Contact placeholders when needed.
Email ingestion does not create Projects, Project Matters, Tasks, or Agent Memory.
Automated tests verify evidence preservation, file deduplication, File Reference metadata, Contact placeholder creation, and the no-direct-write constraints.

Blocked by

## Parent Parent PRD: #2 ## What to build Re-import Bichon email as Communication Archive evidence first. The ingestion path should preserve Communication Records and Communication Evidence, including raw/readable/html content when available, metadata, chunks, attachments, inline images, Stored Files, and File References. This slice deliberately stops before Project Matter classification and must not create Project Matters, Tasks, or Agent Memory. ## Acceptance criteria - [ ] Bichon-like fixtures can be ingested into Communication Records with raw source, readable content, original HTML when available, metadata, and chunks. - [ ] Attachments and inline images are stored as Stored Files outside the database by content hash and connected through File References with original evidence roles. - [ ] Exact email addresses create lightweight Contact placeholders when needed. - [ ] Email ingestion does not create Projects, Project Matters, Tasks, or Agent Memory. - [ ] Automated tests verify evidence preservation, file deduplication, File Reference metadata, Contact placeholder creation, and the no-direct-write constraints. ## Blocked by - #5

liang added the

ready-for-agent

label

2026-06-14 10:21:21 +00:00

liang referenced this issue

2026-06-14 10:21:21 +00:00

Apply explicit Project Match Signals and thread drift rules #7

liang commented

2026-06-14 10:54:22 +00:00

Author

Owner

Implemented issue #6.

Summary:

Added services.communication_archive.archive_bichon_communications.
Archives Bichon-like Communications with raw/readable/html content, metadata, chunks, Contact placeholders, Stored Files, and File References.
Deduplicates Stored Files by content hash and does not create Projects, Project Matters, Tasks, or Agent Memory.

Verification: .venv/bin/pytest tests/test_communication_archive.py -q -> passed.

Implemented issue #6. Summary: - Added `services.communication_archive.archive_bichon_communications`. - Archives Bichon-like Communications with raw/readable/html content, metadata, chunks, Contact placeholders, Stored Files, and File References. - Deduplicates Stored Files by content hash and does not create Projects, Project Matters, Tasks, or Agent Memory. Verification: `.venv/bin/pytest tests/test_communication_archive.py -q` -> passed.

liang closed this issue

2026-06-14 10:54:22 +00:00