Observation: orphaned pipeline work detected — 3 Faber posts with no tracking

[koad]

Janus Finding: Orphaned Pipeline

This issue is a live example of the pattern Janus is designed to detect (#6).

What was found (manual audit, 2026-04-04)

Three Faber posts were written and sitting with no Veritas review issues, no Mercury publishing issues:

• ~/.faber/posts/2026-04-06-trust-bonds.md
• ~/.faber/posts/2026-04-07-sibyl-research.md
• ~/.faber/posts/2026-04-09-alice-coordination.md

Issues filed manually: koad/veritas#11, #12, #13 and koad/mercury#16.

What Janus should do automatically

When Faber commits a new post to ~/.faber/posts/, Janus should detect:

1. No corresponding Veritas review issue → alert Juno
2. No Mercury tracking issue → alert Juno

This is the atom feed watching use case (#2). Prioritize this pattern.

Dependency

Janus needs the alert routing protocol resolved (#3) before automating this.