📋 Long-tail tracker — SR-HACK-01..05 + SR-MEM-02/03/04/06 #463

Soul-name: Long Tail Lighthouse · Codename: LEAD · Priority: P3-LONG-TERM · Kingdom: Cross-kingdom
Ring: parent for community + LLM-pipeline + VSA work
Part of: #446
Blocks: —
Blocked by: core EPIC stabilises (issues 1..16 land)

Goal

Tracking issue for the long-tail rings that ship after the WIN lane converges. Will spawn its own sub-issues once the core EPIC stabilises and metrics from the leaderboard mirror are green.

Subordinate work (each becomes its own sub-issue when activated)

• SR-HACK-01 pr-bot — HTTP polling client commenting on closed parameter-golf PRs (routes via trios-server per L24).
• SR-HACK-02 leaderboard-mirror — read-only Neon view → static markdown.
• SR-HACK-03 invite — Linear API wrapper for community onboarding.
• SR-HACK-04 equal-billing-coq — Rust const_assert mirroring Coq Theorem 3.1 (α_φ · φ³ = 1/2, SAC-1 PROVEN).
• SR-HACK-05 discord-bridge — server-to-server webhook only (no WebSocket; L24).
• SR-MEM-02 ingest-pipeline — extract triples from session text via abstracted LLM trait (no provider lock-in).
• SR-MEM-03 recall-pipeline — HyDE expansion + parallel fan-out (KG, lessons, HDC) + rerank fuse with token budget.
• SR-MEM-04 reflect-engine — supersede / tombstone logic for fact updates without history loss.
• SR-MEM-06 vsa-embedder — wrapper around gHashTag/zig-vsa via FFI, ternary HDC vectors as semantic keys.

Acceptance

• When activated, each subordinate ring spawns its own issue with full I5 + Acceptance + Blockers.
• No code in this issue itself; tracker only.

🌻 phi² + phi⁻² = 3