Reference document
About Slowwire
Slowwire is a public research desk for prediction-market moves, implied probabilities, source rules, and visible gaps. Outputs are sourced records, not advice.
- Status
- static
- Updated
- 2026-04-27
- Owner
- Slowwire
01
Identity
- System
- SlowwireA public analysis system for prediction markets, probability movement, resolution criteria, and source-aware market context.
- Primary unit
- runA durable record containing target market, probability context, evidence, probable causes, gaps, governance, and cost metadata.
- Public product
- 1Slowwire's public experience is focused on prediction-market intelligence.
- What does Slowwire publish?
- Structured records that explain what moved, which public evidence supports the explanation, what remains unknown, and which source timestamps matter.
- What does Slowwire not publish?
- It does not publish trading calls, portfolio tools, investment positioning, private-information claims, or unlabelled live telemetry.
- Who is the first reader?
- Prediction-market watchers, analysts, journalists, and other users who need sourced public records without a sales gate.
02
Product boundaries
- Prediction-market boundary
- Slowwire explains market reactions, probability movement, and probable causes. It is not an execution, pricing, arbitrage, or betting product.
- Advice boundary
- Slowwire provides prediction-market intelligence and analysis. It does not provide financial, legal, betting, or investment advice.
- Access boundary
- The first public surface is open. Account-bound workspaces, saved objects, and protected admin views are separate product surfaces.
03
Operating model
- Repository
- github.com/jxi5410/SlowwireThe application, runtime contracts, tests, release gates, and agent-organisation records live together.
- Deployment
- ./deploy.shProduction deployment requires explicit human approval and uses the repository deploy wrapper only.
- Persistence
- PostgresRuns, evidence, decisions, workspaces, and release-critical records are persisted in Postgres.
- How is the project governed?
- Changes run through issue files, claim files, tests, release gates, and documented acceptance criteria before deployment.
- How should defects be reported?
- Use feedback@slowwire.ai for product feedback and the public repository for code issues when a GitHub issue is appropriate.
04
Version log
| Date | Version | Change |
|---|---|---|
| 2026-04-27 | desk-static.v1 | Static pages rewritten as Desk reference documents with question rows, facts, versions, and sources. |
| 2026-04-26 | static-release.v1 | Initial public static pages added for about, methodology, and transparency. |