You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
README env block: resolve the PROD_FORECASTS TODO placeholders with live-verified values (June phantom-collection postmortem) #104
The README's hand-copy env block (README.md ~line 135) is the only place the APPWRITE_PROD_FORECASTS_* variables were ever documented — and it is where the June 2026 failure's phantom forecasts_metadata collection ID came from (someone hand-exported the documented lie; the postmortem found the collection never existed). After the postmortem the block was flagged TODO: verify and the collection ID left as ... — still unresolved today.
The live-verified values (2026-07-19/20 forensics)
Receipts: verified against live Appwrite on 2026-07-20 (STORE_ACTIVE, real_collection_present: True, 318 files); encoded as constants with regression tests in views-models tools/liveness/appwrite_store.py:37-39; cross-repo review artifact views-models/reports/expert_reviews/2026-07-19_adr013_wire_contract_review_views_models_seat.md §3.4. This closes ADR-013's §7(b) prerequisite and views-models#230 blocker A (the run env itself was fixed locally 2026-07-20).
Beyond the value fix (the mechanism)
Hand-copy-from-README is the failure mechanism, not just the wrong value: an unverified doc block feeding production env by clipboard. When resolving the TODO, consider having the block point at a canonical .env location instead of inviting the copy (the current de-facto canonical file is views-faoapi/.env) — the broader "config that references external reality must be validated" story is views-models register C-100 (Mitigated via tools/liveness) and lands in the delivery acceptance document.
Filed from the views-models seat during the 2026-07-20 FAO delivery push (maintainer-directed).
Done in PR #177 — surfaced by the /falsify audit that disproved "there is nothing more to do in this repo". Actionable with no external dependency; simply never done.
Activity
chore: close the three unblocked items /falsify found (#177)
Polichinel commentedon Aug 1, 2026
Done in PR #177 — surfaced by the
/falsifyaudit that disproved "there is nothing more to do in this repo". Actionable with no external dependency; simply never done.