See the refund-window conflict resolved live
The hosted demo runs the exact same container image and server binary as self-host, seeded with a curated synthetic fixture — no signup, no real customer data, ever.
What you'll see
The fixture (acme/store, a synthetic organization used consistently across every
test file) deliberately includes two findings so you see a real conflict without needing to set
anything up:
Jira
SHOP-412: Done
Ticket text states a 30-day refund window.
Docs
14 days
Stale policy page, last updated before the code/Jira value was settled.
Code
30 days
REFUND_WINDOW_DAYS = 30, agreeing with Jira.Production
Still v1.8.0
v2.0.0 is live on beta, not on production.Open the capability's timeline in the demo to see both transitions as discrete, dated events, and follow any claim's citation back to the exact evidence it rests on. See the full hosted demo walkthrough in the docs for what's running underneath, and connect an MCP client to this same demo without installing anything.
This is a demonstration environment on free-tier infrastructure, not an SLA-backed service — it
may be reset or briefly unavailable. That's a statement about this specific demo, not about
Horologium's Public Alpha generally.