Atlas · MACRO NOTE
Published 2026-06-14

Atlas Research Notebook: Macro Market Structure Notes, Official Source Rails, and 224 Symbol Pages

Atlas runs an AI trading research dashboard where official and government rails carry the evidence and the AI model reviews second, and the 2026-06-14 05:08 UTC rebuild shipped 224 validated symbol pages from a single daily research substrate.

Atlas Research Notebook Build State on 2026-06-14

The Atlas research notebook is a static-plus-API research surface, not a signal feed. The most recent rebuild completed at 05:08 UTC on 2026-06-14 and wrote the daily batch report to /root/Atlas_Backend/cache/daily_batch_reports/atlas_daily_batch_20260614_050003.json, alongside refreshed asset-class hubs at /var/www/atlas/stocks/crypto/index.html, /equities/, /etf/, /forex/, /commodities/, and /indices/.

The canonical static build, recorded across the dated build notes in the source pack, regenerates 224 symbol pages with Atlas Pulse JSON validating 224 of 224, 176 indexable pages, 2 deprecated-symbol redirects, 6 asset-class hubs, and a stocks/sitemap.xml carrying 183 URLs. The full set is browsable at the Atlas symbol coverage hub, which spans US equities such as AAPL, UK names like SHEL, BARC, and LLOY, European listings including SAP and NESN, Asian tickers such as 7203 and 9988, indices like SPX, NDX, UKX, and DAX, and crypto symbols including INJ, JUP, and FIL.

A prior Claude Fable 5-assisted review pass over the writer pipeline reported 171 symbols passing the full QA contract with empty issue_counts and warning_counts, after the free browser report contract replaced the older snapshot teaser. That contract change matters for the research surface: free Atlas users now read the full sourced report in-browser, while PDF and CSV export, email delivery, 10 runs per day, saved history, and watchlists remain Atlas Pro.

Economic Calendar Research on an Official-Schedule Contract

Macro market structure notes start with the calendar, and the Atlas economic calendar is built to a deliberately narrow contract. The backend at /root/Atlas_Backend/economic_calendar.py serves /api/atlas/economic-calendar, which the source pack records returning OFFICIAL_SOURCE_READY with provider_state=official_public_schedule and the scheduled FOMC, PCE, and GDP rows attached to source provenance.

The contract is schedule-only by design. Official events expose their timing and source, but actual, forecast, and previous numbers are not inferred. When a value is missing, the calendar renders not supplied rather than implying a provider feed exists. The 2026-06-13 19:50 BST expansion widened the pre-brief matrix into seven event families: rates, inflation, labour, growth, energy and inventories, sector stress, and earnings timing. The backend adds a Sector and earnings timing planned family covering earnings calendars, guidance windows, sector revisions, and index rebalances as provider-pending checks.

This is the cross asset market intelligence layer. One macro calendar feeds context across equities, forex, commodities, and crypto symbols, and the Atlas notes surface records the methodology so the calendar can be read without a workstation session. Calendar mechanics for live trading sit on the Maverick surface, not here.

Source Authority: Official Rails First, AI Review Second

The defining design rail, shipped 2026-06-13 18:03 BST, is an explicit source-authority band on the homepage and on every generated symbol page. The methodology states that public sources remain the evidence rail while AI can assist drafting and review. The named official and institutional rails written into the symbol-page generator are SEC EDGAR, FRED, the Bank of England, the Office for National Statistics, Nasdaq, TradingView, and CoinGecko.

That ordering is the product claim: filings and macro statistics are cited first, and the model reads them second. The model framing across the security, methodology, privacy, and Pro copy is a Claude Fable 5-assisted review plus publicly re-testable grades, replacing earlier wording that implied an external audit or certification. The OpenBB, DefiLlama, and RSS market spine sits underneath as the data-fetch layer. The OpenBB documentation at docs.openbb.co describes the same fetch primitives Atlas leans on for cross-asset data.

Public Data Catalogue and Symbol Coverage Counts

Symbol coverage is also published as machine-readable data. The authority builder at /root/FreedomCore_Tools/python/atlas_authority_assets.py, on renderer atlas-authority-renderer.v4, published version 20260613-d2053b7d37f1 with row_count_public 176 and row_count_total 226. The catalogue is live at https://atlas.freedomcore.io/datasets/ and the symbol-coverage dataset at https://atlas.freedomcore.io/datasets/atlas-symbol-coverage/, both returning HTTP 200 in the recorded checks.

A 2026-06-13 18:13 BST audit fixed a metadata gap rather than a data gap: /etc/nginx/mime.types now maps text/csv csv;, so coverage CSV serves as text/csv instead of falling back to application/octet-stream. JSON, schema, and manifest endpoints stay application/json and are labelled as machine-readable files browsers may preview inline. The datasets sitemap continues to advertise /datasets/, /datasets/atlas-symbol-coverage/, /datasets/atlas-market-pulse/, and /datasets/atlas-security-posture/.

Homepage and Workstation Route Split

To keep the public research surface crawlable and light, the 2026-06-13 21:10 BST change split the heavy app off the homepage. The homepage at https://atlas.freedomcore.io/ stays index, follow with canonical /, carrying Source Authority, Atlas Pulse, the macro calendar, docs, notes, stocks, Pro, and the public dataset pathways. The full runnable research terminal moved to https://atlas.freedomcore.io/workstation/, served noindex, follow with its own canonical so the app shell does not compete with the indexable homepage. The /workstation path returns 301 to /workstation/. Both FreedomCore and Atlas keep https://freedomcore.io/datasets/ redirecting 301 into the Atlas catalogue.

Caveats and Open Items

Several items recorded in the source pack are not yet proven, not live, or still open.

The destination for the full methodology and the dated build notes is the Atlas notes surface, and the machine-readable provenance is published under Schema.org BlogPosting structured data so the research surface stays legible to crawlers as well as readers.

Browse the Atlas research notebook

FreedomCore Atlas Research →