ADR 0008: Consumer repositioning¶
Status: accepted on 2026-11-08 by the owner. Supersedes the conflicting clauses of personal-agent requirements 2.1. Product authority: consumer product requirements 3.0, since replaced by requirements 3.1, which keeps this decision.
Context¶
Argus grew as an institution-grade governed data layer: tenant-scoped institution_id throughout the code, a 13-stage service boundary on every read, a per-call archive of the full response package, and quantitative tools (options, bounded streams, PIT export, feature DAG). A personal layer was added on top (67 owner-scoped personal_* tools), but OAuth users get it disabled by default.
Organic consumer usage is very small: 26 OAuth subjects, and OAuth accounts for 1.55% of audited calls. Most audited traffic is internal connector work.
Requirements 2.1 kept the "Agent-Readable Financial Data Layer" identity (line 27), required every advanced tool to be kept (line 217), and limited alerts to the inbox (line 272). That makes a consumer pivot a requirements violation unless the baseline changes.
Decision¶
- Positioning. Argus is a cited-facts and private-memory service for individuals and their own AI agents. The user's AI is the primary interface. The public tagline is "Every number, with its source". "Agent-Readable Financial Data Layer" survives only as a technical description in developer documentation.
- Audience and regions. The service is for individuals aged 18 or over, for non-professional use. Mainland China and sanctioned regions are excluded through an account-level eligibility decision that every entry point enforces.
- Languages. The site and apps support en, zh-CN, zh-TW, ko, es and pt. URLs for the removed locales (ja, hi, de, fr, it, vi) redirect permanently to English and are dropped from the sitemap and hreflang.
- Data rights.
- EODHD end-of-day bars may be displayed and delivered to users' agents.
- EODHD reference data (daily close, identity, splits, symbol changes and dividends) may be delivered to users' agents to value their recorded holdings (owner decision D11, 2026-11-08).
- Real-time quotes, websocket trades, intraday bars and ticks are not offered, and their capture is disabled.
- EODHD news and the other non-public sources are hidden from consumers.
- Consumer reads enforce source rights in the read layer instead of relying on per-tool filters.
- Business model. Free public beta, with no billing in this phase. A paid tier is a separate, later decision.
- Readiness. Required coverage is computed from the sources that are enabled and licensed for the deployment, so a stopped or unlicensed source cannot block a release.
- Privacy. Practice must match the published notice:
- account deletion covers audit linkage, response archives and identity mappings;
- audit retention can actually prune;
- backups are encrypted with a 35-day retention.
- Edge and operations.
- Machine and connector-administration routes are not exposed publicly.
- Rate limits see the real client address behind Cloudflare.
- The application database login is least-privilege.
- Delivery. Delivery is phased, as set out in requirements 3.0 §8, and each phase has exit criteria.
Consequences¶
- Website gates and tests that pinned the old tagline, the 12-locale list or the inbox-only alert rule are updated in the same change. They are not deleted wholesale.
- Advanced and diagnostic tools leave consumer discovery first. Their code is retired only after their remaining use has been inventoried.
- Requirements 2.1 remain in force wherever they do not conflict with 3.0. The no-advice, no-trading, no-enterprise and no-return-rate boundaries are unchanged.
- The earlier decision on the personal application boundary stays in force until the identity-provider and front-end changes reopen it.