Event-Driven Market Intelligence

IRIS documentation that matches the live system.

Architecture, governance, runtime boundaries, Home Assistant integration, AI planning, and generated HTTP artifacts are grouped around the current repository instead of the legacy wiki model.

Get started Market data keys Read architecture View generated API docs

FastAPI + Redis Streams TaskIQ worker runtime Home Assistant bridge Governed HTTP contracts

Disclaimer

IRIS provides informational and operational tooling for self-directed investors. It is not a broker, investment adviser, execution guarantee, or promise of profitability. Users remain solely responsible for any investment, trading, automation, and risk-management decisions.

Platform snapshot

The docs site follows the same product language as the frontend: dark shell, glass panels, tide green highlights, and amber action accents.

Backend domains

13

Accepted ADRs

21

Primary doc classes

6

API governance snapshots

2

Start from the right place

Use the navigation below according to intent, not by folder guesswork.

Architecture

Accepted system shape

Runtime model, persistence boundaries, control plane, service-layer policy, and accepted ADRs.

Open architecture docs

Delivery

Execution plans and audits

Refactor rollout state, implementation audits, localization planning, and AI platform working docs.

Open delivery docs

Generated

Code-derived API truth

Availability matrix and HTTP capability catalog exported from the live codebase and used in CI governance.

Open generated artifacts

Home Assistant

Bridge and protocol surface

Server-driven integration docs, backend plans, HACS integration planning, and protocol contracts.

Open Home Assistant docs

Product

Framing and review checklists

Higher-level product value framing and endpoint review guidance that supports the architecture work.

Open product docs

OSS

Repository model

Contribution, security, licensing, and repository expectations for an external contributor path.

Open OSS guide

Current sources of truth

Not all markdown in the repository has the same authority.

• Generated artifacts first: use code-derived HTTP snapshots when validating what the platform actually exposes.
• Accepted architecture second: use ADRs and architecture policy docs for target boundaries and operating rules.
• Integration specs third: use integration-specific protocol docs when the question is scoped to Home Assistant.
• Execution docs fourth: use delivery and audit docs for rollout state, refactor campaigns, and principal implementation plans.