Skip to content

Add no-write SEC fundamentals preview - #115

Merged
YuzeJ21 merged 5 commits into
mainfrom
codex/sec-fundamentals-preview
Aug 19, 2026
Merged

Add no-write SEC fundamentals preview#115
YuzeJ21 merged 5 commits into
mainfrom
codex/sec-fundamentals-preview

Conversation

@YuzeJ21

@YuzeJ21 YuzeJ21 commented Aug 16, 2026

Copy link
Copy Markdown
Owner

What changed

  • reveal existing lower-case screener context in the single-stock report
  • add a capped, official-SEC-only annual fundamentals comparison for up to five explicit tickers
  • produce a field-level review packet with ticker/CIK, retrieval time, annual period, filing/accession, unit, source reference, source-rights status, schema status, exact delta, and required owner action
  • add an explicit filing-date review row while preserving its anchoring fact unit separately
  • keep the comparison inspection-only: no cache, import, canonical, readiness, or output writes and no apply path
  • document the AAPL/NVDA/AMD review workflow and its fail-closed boundary

Why

Canonical fundamentals can be stale or mix reporting periods. Reviewers need a safe, reproducible way to compare official SEC annual facts before any source-rights expansion, schema decision, or canonical apply. The report renderer also expected display-case screener keys while real payloads used lower-case keys.

Product impact

A reviewer can inspect source-backed annual facts for an explicit cohort without activating product readiness. Only changed direct fields already allowed by the registered SEC scope and already present in the canonical schema can become future owner-review candidates. Derived, mixed-unit, out-of-scope, incoherent-period, malformed, and missing evidence remains blocked.

The live AAPL/NVDA/AMD packet is inspection_only, reports repository_writes=[], and keeps canonical_apply_authorized=false. AAPL and AMD expose only revenue and filing date as future review candidates; NVDA exposes none because its reviewed values are unchanged. Shares remain blocked when their latest explicit facts do not match the annual anchor.

Verification

  • exact-head GitHub local-engineering-gate: 6,795 passed, 0 failed, 1 warning
  • dashboard smoke, Personal Research rendering, public wording, artifact hygiene, and whitespace checks: passed
  • affected local SEC/provider/launcher/public-doc suite: 228 passed
  • focused filing-date provenance and deterministic-rebuild checks: 2 passed
  • Ruff on all changed Python files: passed
  • independent current-byte review: Critical 0, Important 0, Minor 0
  • live packet SHA-256: e8fc79cac4eca29a52815db14052bd46e96d1886fef0e6ab0e4109bb975ddff8
  • protected data/, outputs/, and docs/assets/: 7,315/7,315 file hashes unchanged; path, directory, and link topology unchanged

Boundaries

This PR does not apply data, expand registered commercial field rights, refresh readiness, add generated repository artifacts, publish a hosted app, merge, deploy, or provide investment recommendations.

@YuzeJ21
YuzeJ21 marked this pull request as ready for review August 19, 2026 23:40
@YuzeJ21
YuzeJ21 merged commit c0e39ed into main Aug 19, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant