Summary
Lyra — Short Links & Attribution — regenerated from canonical/guides/tools/lyra.md. Do not hand-edit this page — update the canonical file and re-project. Status: live. Primary domain: [lyra.stoicagent.com (admin) + l.getrealstl.com (short links)](https://lyra.stoicagent.com (admin) + l.getrealstl.com (short links)). Pipeline role: link intelligence layer — sits between Spark and Hermes.
Content
Purpose
Short URLs, pixel injection, click tracking. Every Spark-built showcase page automatically gets a Lyra short link with a tracking pixel, so when Hermes distributes the page organically, clicks flow back into our attribution.
Current state
- Status: Live (deployed at scale April 16, 2026)
- Replaces: Geniuslink (~$20/month saved)
- Pipeline position: Auto-baked into Spark output, feeds downstream distribution
Where it lives
- Code:
Tools/Lyra/site/ - Admin UI: lyra.stoicagent.com (Netlify:
lyra-admin.netlify.app) - Short-link hostname:
l.getrealstl.com(also reference in inventory asl.connectbyreal.com— reconcile in refresh pass) - Access code:
artemis2026(see memory: Artemis Tool Access Codes)
Integrations
- Spark — auto-creates short URL on every page build
- Hermes — distributes short URLs in social posts
- Analytics backend — click events flow to ??? (verify target: FUB? custom DB? Google Analytics?)
Related
- Inventory row:
canonical/business-state/tool-stack-inventory.md→ "Lyra" - Access codes location: every Artemis tool's ACCESS_CODE in Netlify site env
Typical development touchpoints
- Short-link hostname DNS
- Pixel injection template
- Click-event storage / retention
- UTM parameter handling
- Per-agent attribution
Active WIP location
working/drafts/tools/lyra/ (create as needed during active development)
Open questions / gaps
- Two hostnames cited in different places (
l.getrealstl.comvsl.connectbyreal.com) — which is active? - Click data destination: where does it accumulate for attribution analysis?