Skip to content

ADR 0019: ArgusFA, LLC operates Argus

Status: accepted on 2026-11-14 by the owner. Product authority: consumer product requirements 3.1 (markdown/argus-consumer-product-requirements-3.1.md), decision D4, which this record changes.

Context

  1. D4 kept the publisher. Requirements 3.0 and 3.1 recorded decision D4 as "keep the current publisher": NovAI Limited, Hong Kong. The website, the legal documents, the personal application, the SEC User-Agent and the operations documents named it and its contact address.
  2. The owner changed the operator. On 2026-11-14 the owner decided that ArgusFA, LLC operates Argus and that its contact address is [email protected]. Asked the same day, the owner confirmed that the legal name is written ArgusFA, LLC, that the company is registered in Delaware, and that the Terms move to the law and courts of Delaware.
  3. The legal documents are an agreement. Each owner's acceptance is recorded with the revision accepted, and a change to the agreement ships as a new revision that every owner accepts again.

Decision

  1. Operator. ArgusFA, LLC, a Delaware limited liability company, operates Argus. Every text that names the operator names it, and every contact address is [email protected]: the website in its six languages, the legal documents, the personal application, the documentation and the code.
  2. Legal revision 2026-11-14. The Terms of Service, the Privacy Notice and the Account Deletion Guide, in English and Simplified Chinese, name ArgusFA, LLC. The Terms are governed by the laws of the State of Delaware, and the state and federal courts located in Delaware have exclusive jurisdiction, subject to mandatory rights where the user lives. The Privacy Notice says that the operator works from the United States. src/argus/legal_documents.json holds the revision, its effective date, the operator and the contact address.
  3. SEC User-Agent. Requests to SEC EDGAR identify as ArgusFA, LLC [email protected] (SEC_USER_AGENT), and the ETF reference request carries the same address.
  4. Records keep their history. Requirements 3.0, which license records cite, is not changed. Decision D4 in requirements 3.1 and the review report note the change and its date. No sealed file changes.

Consequences

  • Each owner sees revision 2026-11-14 and accepts it the next time they open the personal application. Connected AI apps are not interrupted: the MCP tools do not check the accepted revision.
  • Release 1.1.35 changes SEC_USER_AGENT in the production configuration.
  • tests/unit/test_operator_identity.py fails when a file outside the records of this change names the former operator, and website/tests/unit/legal-pages.test.ts checks the operator, the address, Delaware law and the revision.
  • Left to the owner, outside this repository: the mailbox [email protected] must receive privacy and deletion requests; the identity service's organization name and mail sender, the GitHub OAuth app, the Claude directory listing and the data provider accounts (EODHD, CoinMarketCap) are changed by the owner.