type: email_thread
thread_id: github-seed-256-notifications-bug
source: github
repository: seed-hypermedia/seed
issue_number: 256
issue_url: https://github.com/seed-hypermedia/seed/issues/256
total_messages: 3
language: en
archived_at: 2026-02-27
Messages
Message 1
type: email_message
message_index: 1
from_name: Eric Vicenti
from_email: notifications@github.com
to: seed-hypermedia/seed
cc:
mentioned_user: GaboHBeaumont
date_local: 10:17
relative_time: hace 6 horas
source_platform: github
github_issue: 256
github_repo: seed-hypermedia/seed
Body
ericvicenti left a comment (seed-hypermedia/seed#256)
@GaboHBeaumont please provide repro steps on bug reports
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
Message 2
type: email_message
message_index: 2
from_name: Eric Vicenti
from_email: notifications@github.com
to: seed-hypermedia/seed
mentioned_user: GaboHBeaumont
date_local: 13:06
relative_time: hace 3 horas
source_platform: github
github_issue: 256
github_repo: seed-hypermedia/seed
Body
ericvicenti left a comment (seed-hypermedia/seed#256)
Many times, when I then click the content button, I get this error:
[Image attachment referenced]
This looks like an unrelated issue? Please file a different issue and explain what is the "content button"
Message 3
type: email_message
message_index: 3
from_name: Eric Vicenti
from_email: notifications@github.com
to: seed-hypermedia/seed
mentioned_user: GaboHBeaumont
date_local: 13:07
relative_time: hace 3 horas
source_platform: github
github_issue: 256
github_repo: seed-hypermedia/seed
attachment_url: https://github.com/user-attachments/assets/10e328b4-2e29-4f1b-8cb8-863c185531bb
Body
ericvicenti left a comment (seed-hypermedia/seed#256)
@GaboHBeaumont I can't reproduce this issue. Please explain how the notification is created where the issue exists
I guess its for discussions that were started on an older version of a document, and it takes you to that older version?
Linking Model in Seed
In Seed, this would ideally be structured as:
One email_thread document
Three linked email_message documents
Attachment as a linked document (if downloaded)
Cross-links to:
GitHub Issue #256 document (if mirrored)
Mentioned user document (GaboHBeaumont)
Repository document (seed-hypermedia/seed)
🧬 Provenance Strategy
For full traceability, each message document should include:
_source_email_file: original.eml
_source_message_id: <raw message-id header>
_source_import_timestamp: 2026-02-27TXX:XX:XXZ
_source_hash: sha256-of-eml
Each block can optionally include:
_source_block_offset: char-range
🏗 Recommended Production Structure (Cleaner Version)
Instead of storing all messages inside one doc, I recommend:
Email Thread Doc
├── Email Message Doc 1
├── Email Message Doc 2
└── Email Message Doc 3That way:
Each message has its own revision history
Replies can become new changes in the DAG
You can embed/query messages by thread_id
If you want, I can next give you:
A canonical frontmatter spec for Seed email archiving
A CLI import template for .eml → seed document create
Or a normalized “GitHub notification email schema” (since those are semi-structured and very automatable)