Empty Sources Should Still Leave a Discovery Trail
Validates that the joelclaw discovery path can preserve source intent and publishing metadata even when extraction fails.
This isn’t a summary of Example Domain. The fetch didn’t return content, and Joel’s note was just “test discovery mapping only.” That’s the useful part: a discovery note can still prove the mapping path without pretending the source said anything.
For Obsidian and joelclaw, the shape matters: URL, source type, target site, visibility, date, tags, and relevance. Those fields can survive even when web extraction returns nothing.
The clever move is treating missing content as data, not a reason to make shit up. A null-content discovery should be visible in the Vault, tagged honestly, and ready for a later human or agent pass if the source becomes worth expanding.
Key Ideas
- Missing extraction should be represented explicitly instead of backfilled with fabricated summary text.
- YAML front matter is the durable handoff between the discovery capture step and the joelclaw publishing surface.
- Example Domain is a safe fixture for validating public Obsidian note generation without coupling the test to live article content.
- A clean null-content branch keeps Vault artifacts auditable instead of burying extraction failures in logs.