ADR 0014: Dictated holdings are saved directly; fractional quantities; watchlist member removal¶
Status: accepted on 2026-11-13 by the owner. Product authority: consumer
product requirements 3.1 (markdown/argus-consumer-product-requirements-3.1.md).
Context¶
Three rules make everyday use of holdings and watchlists harder than the risk warrants.
- Holdings are never saved from a conversation.
record_holdingsonly previews. Itscommitoption creates an approval plan that the owner must open in the web app, because the core treats every import commit as a bulk operation and only a web session can approve one. Requirements 2.1 line 290 say an import is previewed and written after the user confirms. - Quantities must be whole. The default precision is zero decimal places, and a higher precision needs a unit evidence id that no production code supplies. Requirements 2.1 line 289 allow fractional precision "supported by a source unit". The column already stores twelve decimal places.
- Removing two watchlist members needs web approval. Requirements 2.1 lines 102 and 106 require bound confirmation for bulk deletion or overwrite. The threshold of two members is the code's reading; the requirement names no number.
A hosted AI app already asks the user before it calls a tool that writes, and the tools carry truthful annotations.
Decision¶
- Direct save. New holdings that the user dictates in a conversation are
written by
record_holdingsonce the host has confirmed the tool call. This covers rows that do not replace an existing snapshot of the same security at the same time, up to 20 rows per call. - Still previewed and approved in the web app: a row that replaces an existing snapshot, a call with more than 20 rows, and every file import.
commitis removed from the tool's input.- Authorization and audit. The asset write scope and the app's holdings
consent are still required. Each write keeps its audit id, mutation receipt
and
user_providedprovenance, and also records which app wrote it. - Fractional quantities. A quantity has up to eight decimal places. The user is the source of a quantity the user reports, so no separate unit evidence is needed. Input is accepted as a decimal string.
- Watchlist members. Removing members from a watchlist runs directly, up to 50 per call. Deleting a whole list, and deleting notes or holdings in bulk, still need bound approval.
- Unchanged.
- Requirements 2.1 lines 293 and 294: no computation across a period whose corporate actions are not verified. Valuing at the latest close stays inside that rule.
- Requirements 2.1 line 96: account deletion and revoking all authorizations need recent personal verification in the web app.
Consequences¶
- Requirements 3.1 section 4 records these as changes to 2.1: line 290 is superseded for dictated holdings, line 289 is clarified, and lines 102 and 106 are read as not covering member removal. The 2.1 file is sealed and is not edited.
- The confirmation and holdings rules are updated to match, and the consumer tools page describes the behaviour. The contract label for member removal is renamed.
- A host that approves tool calls without showing them could write a holding the user did not see. The controls are: a direct save only adds, never overwrites; it is limited to 20 rows; every write is audited; and the user can read and remove it at once.
- Fractional quantities are a precondition for crypto holdings (ADR 0011).
- Tests that pin the preview-only behaviour and the two-member threshold are updated to the new rules. They are not deleted.