Intelligence briefs and analysis
World Monitor turns live news and domain data into short intelligence products. These products help a reader see what changed, why it matters, and what to watch next. The system combines model-written summaries with source checks, signal measures, durable history, and reader and agent views.
Product scope
This page covers the brief and analysis layer below Intelligence products. It covers global, country, regional, market, historical, and research views. Company monitoring intelligence covers company-focused monitoring. Forecasting, scenarios, and resilience covers related scenario and resilience views.
The products use different time scales and answer different questions:
| Product | Main question | Main evidence |
|---|---|---|
| Global brief | What matters now? | Accepted news insight snapshot |
| Country brief | What is happening in one country? | Country news, risk, market, energy, and infrastructure context |
| Country coverage | Which country-linked incidents and sources are visible? | News coverage and structured incident records |
| Regional brief | How is a region changing? | Regional snapshots and regime history |
| Signal analysis | Which changes align across domains? | News, markets, forecasts, and operational feeds |
| Historical intelligence | What happened before? | Durable event history |
| Research output | What does a fixed data set show? | Versioned snapshot with metrics and sources |
The same event can support several products. Each product keeps a different purpose so a short alert does not replace a deeper analysis.
Brief generation
The brief pipeline selects useful evidence, creates a bounded narrative, checks its claims, and exposes the accepted result with its source trail. A brief is therefore a summary of an accepted input set, not an open-ended answer.
This diagram shows how source data becomes a reader-facing brief.
flowchart LR
A[News and domain data] --> B[Cluster and rank]
B --> C[Select evidence]
C --> D[Create narrative]
D --> E[Check claims and citations]
E --> F[Store accepted result]
F --> G[Dashboard, API, agents, and delivery]
Global brief
The global brief gives a compact view of important current stories. It groups related headlines, limits the story set, and prefers distinct publisher families so repeated copies of one report do not look like independent support. The accepted snapshot includes the story list, source coverage, freshness, and credibility signals. (scripts/seed-insights.mjs, scripts/_insights-brief.mjs)
The narrative has a cited lead and cited story lines. The producer checks response shape, citation indexes, names, facts, and claim grounding. If a fresh synthesis fails, the system can keep the last known-good snapshot and mark the run as degraded. Readers use the accepted snapshot instead of starting a new model call for each visit. (scripts/_insights-brief.mjs, src/…/insights-loader.ts, src/…/InsightsPanel.ts)
References: scripts/seed-insights.mjs• L904-1088 scripts/_insights-brief.mjs• L436-668 src/…/insights-loader.ts• L37-89 src/…/InsightsPanel.ts• L314-429
Country brief
The country brief explains the current situation for an assigned ISO country code. It joins country-matched news with risk signals and available economic, energy, market, infrastructure, maritime, and trade context. The generated view is organized around the current situation, country impact, risks, near-term outlook, and watch items. (server/…/get-country-intel-brief.ts)
Anonymous readers use one server-grounded result for each country and language. Premium requests can add caller context and an analysis framework. The cache identity includes language, energy and import-dependency data years, monitored airport status, and premium context where relevant, so changed evidence can produce changed prose without allowing anonymous caller text to shape a shared result. (server/…/_country-brief-context.ts, server/…/get-country-intel-brief.ts)
Shared country grounding starts with relevant country headlines from the digest. It applies source revocations, country aliases, and relevance filters before the model sees the material. If the suppression set cannot be read, or no usable relevant headline remains, the system returns no grounded English brief instead of filling the gap with global or unsupported context. Headline text is treated as data and is kept to one prompt line. (server/…/_country-brief-context.ts, server/…/get-country-intel-brief.ts)
Country claims use two evidence types: numbered headlines and typed World Monitor data points. The evidence pack uses public-safe values from risk, advisories, airport notices, sanctions, resilience, energy, chokepoints, markets, and forecasts. Each item has a type, value, time, and fact sentence. Missing, malformed, unreadable, or old sources drop their own items rather than invalidating the full pack. (server/…/_country-brief-evidence.ts)
Section rules limit which evidence can support situation, implications, risk, outlook, and watch claims. Situation claims need a headline. Implications need a headline and a data point. Risk claims need a data point. Outlook claims use only a market or forecast. The publisher drops claims with invalid citations, unsupported names, numbers, dates, roles, or status words. It also requires a surviving grounded situation claim before it publishes an English brief. Other languages keep the analyst path but do not yet use the English claim validators. (server/…/get-country-intel-brief.ts)
The country view loads its sections in parallel. The controller separates loading, ready, locked, unavailable, and partial coverage states. It also cancels old work and accepts a result only when it still belongs to the active country and panel. This lets a reader see available evidence without waiting for every source. The market section carries the source snapshot time through the panel contract, so the display can state when its list was fetched without implying that individual quote times are known. (src/…/CountryBriefController.ts, src/…/CountryBriefPanel.ts, src/…/index.ts, src/…/CountryDeepDivePanel.ts)
One country source contract serves both the main website and approved host views. It routes the same broad country needs through intelligence, market, risk, resilience, scorecard, prediction, and supply-chain services while applying the country boundary to host and raw-signal reads. This keeps embedded analysis aligned with the website without allowing a host request to read another country. (src/…/country-brief-source.ts)
The same country source can use direct website services or approved host readers. The host path validates the reader, request arguments, returned section, and country identity. It shares identical reads for a short time, limits active reads, and cancels work when no panel still needs it. (src/…/country-brief-source.ts, src/…/country-brief-host-transport.ts)
References: server/…/get-country-intel-brief.ts• L321-433 server/…/get-country-intel-brief.ts• L476-513 server/…/get-country-intel-brief.ts• L514-633 src/…/CountryBriefController.ts• L38-104 src/…/CountryBriefPanel.ts• L215-230 src/…/CountryDeepDivePanel.ts• L294-339 src/…/CountryDeepDivePanel.ts• L2972-3026 src/…/index.ts• L357-371 src/…/country-brief-source.ts• L11-78 src/…/country-brief-host-transport.ts• L12-99
Country context
Country context supplies stable facts and maritime activity that help a brief explain a place without treating background data as a live event. Facts come from public country knowledge sources and include items such as leadership, population, capital, languages, currencies, area, and a short reference summary. Port activity adds recent tanker calls, import and export volume, trend change, and anomaly state for supported countries. (server/…/get-country-facts.ts, server/…/get-country-port-activity.ts)
The energy profile combines a seeded national energy record with direct gas-storage and electricity reads and regional provider feeds. Direct reads keep sub-daily fields separate from the slower energy spine. The profile also exposes fuel demand and imports, gas dependence, storage cover, power mix, import dependency, strategic reserves, source periods, and observed-measurement coverage. (server/…/get-country-energy-profile.ts, server/…/_regional-energy-feeds.ts)
These reads fail closed when the country is not assigned, the public fact lookup is ambiguous, or a cache read fails. Missing seed data can produce partial coverage, but a failed read is not published as a successful zero-valued profile. Energy feed records similarly distinguish available, partial, stale, error, and unavailable coverage. (server/…/get-country-energy-profile.ts, server/…/_regional-energy-feeds.ts)
References: server/…/get-country-facts.ts• L43-73 server/…/get-country-facts.ts• L87-105 server/…/get-country-port-activity.ts• L34-70 server/…/get-country-port-activity.ts• L73-126 server/…/get-country-energy-profile.ts• L312-394 server/…/get-country-energy-profile.ts• L396-449 server/…/get-country-energy-profile.ts• L451-514 server/…/_regional-energy-feeds.ts• L18-68
Regional brief
The regional brief gives a weekly narrative for a defined region. It reads the latest regional snapshot and recent regime history, then summarizes the situation, trajectory, key developments, and risk outlook. The regional board places that narrative beside structured regimes, actors, scenarios, transmission paths, and watch items. (scripts/seed-regional-briefs.mjs, scripts/…/weekly-brief.mjs, src/…/RegionalIntelligenceBoard.ts)
References: scripts/seed-regional-briefs.mjs• L139-179 scripts/…/weekly-brief.mjs• L1-30 src/…/RegionalIntelligenceBoard.ts• L21-40
Personal brief synthesis
The personal brief is a frozen editorial edition built from an accepted story set and the reader's eligible alert rules. It adds context about why a story matters and creates a digest that can be shown in the dashboard or delivered through supported channels. Validated fallback content keeps the edition usable when enrichment fails. (api/…/brief-why-matters.ts, scripts/…/brief-llm.mjs)
Each edition has a resolved brief language. The composer uses the reader's selected language only when localization is enabled and that language is deliverable; otherwise it keeps the canonical English edition. A localized sibling is optional, so failure to store it does not remove the readable English brief. (scripts/seed-digest-notifications.mjs, scripts/…/brief-l10n.mjs, shared/ui-languages.js)
References: api/…/brief-why-matters.ts• L162-228 api/…/brief-why-matters.ts• L425-576 scripts/…/brief-llm.mjs• L976-1102 scripts/seed-digest-notifications.mjs• L1726-1759 scripts/…/brief-l10n.mjs• L222-243 shared/ui-languages.js• L90-104
Brief language selection
Brief language selection lets a reader choose a delivery language separately from the dashboard language. The effective language uses the saved brief override first, then the explicit application language, and finally English. The Settings view exposes only languages that the current delivery service can produce. (src/…/brief-language.ts, convex/users.ts, shared/ui-languages.js)
The browser binds each read and write to the Clerk account that started it. An account change or failed service call returns a safe failure instead of applying a preference to another user. The server validates the language against the shared list and accepts null to remove the override. (src/…/brief-language.ts, convex/users.ts)
References: src/…/brief-language.ts• L11-49 convex/users.ts• L307-375 shared/ui-languages.js• L46-61 shared/ui-languages.js• L90-104
Signal analysis
Signal analysis looks for relationships that one headline cannot show. It compares news with markets, prediction changes, topic activity, source types, and operational feeds. The result is a typed signal with evidence, confidence, time, and a bounded description.
Event classification
Event classification assigns each headline a threat level and a broad event category. The levels describe the real-world event rather than the tone of the headline, with the highest level reserved for events that can affect international order or global systems. Valid classifications are cached for shared use and map to the service severity levels used by downstream views. (server/…/classify-event.ts)
The classifier accepts only known level and category values. It bounds and sanitizes the headline input, keeps cache entries separate when the allowed AI route changes, and validates cache data in the same way as a fresh model result. When the model or cache cannot provide a valid result, the service marks the classification as unavailable. (server/…/classify-event.ts)
References: server/…/classify-event.ts• L18-37 server/…/classify-event.ts• L44-60 server/…/classify-event.ts• L62-94 server/…/classify-event.ts• L96-185
Correlation signals
The analysis layer detects patterns such as topic spikes, market moves with related news, prediction changes with low news coverage, source convergence, and divergence between flows and prices. It compares activity with a recent baseline and removes duplicate or weak results. Heavy work can run outside the main browser view; if that path is unavailable, the dashboard can show no analysis without blocking other views. (src/…/analysis-core.ts, src/…/analysis-worker.ts)
References: src/…/analysis-core.ts• L86-143 src/…/analysis-core.ts• L286-449 src/…/analysis-worker.ts• L34-86
Dyad tension status
Dyad tension status shows pressure between configured country pairs. It combines a seeded score and change measure with optional GDELT tension data and a short list of notable evidence channels such as strikes, airport changes, military activity, and sanctions. Only configured pairs and valid numeric scores enter the response. (server/…/get-pizzint-status.ts)
The route accepts tension evidence only when its source snapshot is no more than 45 minutes old. A failed evidence read does not erase the score, but the response is marked as a no-store fallback so callers do not treat a partial read as a durable fresh result. GDELT reads are requested only when the caller asks for them.
References: server/…/get-pizzint-status.ts• L12-41 server/…/get-pizzint-status.ts• L43-83
Country coverage
Country coverage gives agents the same country-linked headlines and incidents that the country panel can show. It combines a bounded news window with structured records for protests, earthquakes, conflicts, military activity, vessels, and strikes. News incidents are classified and clustered before they are reconciled with structured records, so repeated reports do not inflate the event list and a first-party record can take precedence. (server/…/_country-coverage-feeds.ts, server/…/_country-coverage-structured.ts, server/…/get-country-coverage.ts)
Each producer reports its own state, contribution count, fetch time, and reason. The response distinguishes observed, empty, unknown, stale, failed, and unavailable coverage. Server-side geographic matching uses a shared country box and reports that approximate containment; browser-only vessel streams remain explicitly unavailable. An empty event list therefore does not by itself mean that the country was quiet. (server/…/_country-coverage-structured.ts, server/…/get-country-coverage.ts)
References: server/…/_country-coverage-feeds.ts• L132-212 server/…/_country-coverage-structured.ts• L39-91 server/…/_country-coverage-structured.ts• L293-330 server/…/_country-coverage-structured.ts• L433-505 server/…/_country-coverage-structured.ts• L552-579 server/…/get-country-coverage.ts• L145-200 server/…/get-country-coverage.ts• L270-371
Country signal observations
Country signal observations provide a common, qualified view of country-linked source data for agents and analysis tools. The service projects families such as outages, unrest, fires, radiation, sanctions, conflict, and military posture into a shared shape with severity, source, time basis, scope, and attribution. Flight activity uses paged geographic windows because it can be larger than the other families. (server/…/get-country-signal-observations.ts, shared/country-signal-observations.ts)
The contract distinguishes an observed family from an unavailable or locked family. It records whether a time is an event time or a source snapshot time, and it marks coordinate-based results as a country activity viewport rather than national territory. Results are bounded and can be partial, so a caller can tell the difference between a short result and complete source coverage. (shared/country-signal-observations.ts)
References: server/…/get-country-signal-observations.ts• L16-72 shared/country-signal-observations.ts• L14-47 shared/country-signal-observations.ts• L101-175 shared/country-activity-query.ts• L1-11
Situation deduction
Situation deduction answers a focused analyst question with a short analysis. It combines the query with geographic context and matched prediction-market odds when those inputs are available. A premium caller can add an analysis framework, while the result remains bounded by a shared cache and a gateway-safe time limit. (server/…/deduct-situation.ts)
Prediction-market titles are treated as data rather than instructions before they enter the analysis context. The service limits the market set and keeps cache identity tied to the query, geographic context, framework, prediction context, and the caller's AI routing policy. If the model or provider does not return before the edge response budget, the service returns an explicit error state instead of publishing partial analysis. (server/…/deduct-situation.ts)
References: server/…/deduct-situation.ts• L11-24 server/…/deduct-situation.ts• L50-88 server/…/deduct-situation.ts• L90-103 server/…/deduct-situation.ts• L123-193
Country risk scores
Country risk scores give briefs and dashboards a common view of instability. The Country Instability Index (CII) combines country-linked conflict, unrest, security, information, climate, displacement, advisory, sanctions, hazard, fire, aviation, earthquake, military, and maritime disruption signals when those inputs are available. The published result carries its methodology version and a global roll-up focused on the highest country scores. (server/…/get-risk-scores.ts, server/…/_risk-config.ts)
The current editorial method is version 14. It uses foreign military activity for security and excludes cyber infrastructure because that data identifies attacker hosting locations rather than victims. GDELT can provide escalation and sustained-level context when the primary conflict source is unavailable. Strike pressure can raise a score and then decay after the event when that source is enabled. Trend labels use a valid earlier snapshot; without one, direction is unspecified. Advisory level and provenance show whether the input is live, a built-in fallback, or absent. (server/…/get-risk-scores.ts, server/…/_risk-config.ts)
The score method is editorial rather than an external academic index. Its versioned coefficients and strategic-risk roll-up define how current values and movement semantics should be read. The global roll-up uses a weighted top-five country set and keeps a baseline floor so a calm set of countries does not appear to mean that all risk is absent.
Fresh builds write the current result, stale fallback, trend history, daily history, and input coverage metadata. A failed input read rejects the new build and leaves the prior result intact. A stale response is marked degraded, so readers and health checks can distinguish old data from a fresh score.
References: server/…/_risk-config.ts• L24-45 server/…/_risk-config.ts• L123-185 server/…/_risk-config.ts• L187-223 server/…/get-risk-scores.ts• L308-340 server/…/get-risk-scores.ts• L1427-1579 server/…/get-risk-scores.ts• L1800-1810 server/…/get-risk-scores.ts• L1867-1902 server/…/get-risk-scores.ts• L1918-1959 server/…/get-risk-scores.ts• L2222-2244 server/…/get-risk-scores.ts• L2247-2275 server/…/get-risk-scores.ts• L2281-2363
Cross-source signals
The cross-source aggregator joins many security, unrest, cyber, market, shipping, sanctions, hazard, forecast, weather, and risk feeds. It groups events by geographic theater and raises a composite escalation when several signal types fire together. The published result is a short ranked list with type, theater, severity, time, summary, and contributing types. (scripts/seed-cross-source-signals.mjs, server/…/list-cross-source-signals.ts)
The dashboard separates composite escalation from single-domain signals. A missing cached result means that the aggregator is starting or the data is unavailable. It does not mean that no risk exists. (src/…/CrossSourceSignalsPanel.ts)
References: scripts/seed-cross-source-signals.mjs• L11-41 scripts/seed-cross-source-signals.mjs• L137-190 server/…/list-cross-source-signals.ts• L12-109 src/…/CrossSourceSignalsPanel.ts• L85-116
Market analysis
The daily market brief turns tracked instruments and related headlines into a summary, action plan, risk watch, and item-level stance. A rule-based summary remains available when model analysis fails, so the reader still sees price direction and breadth. Premium stock research adds a deeper view for one symbol by combining current market series with available ratings, fundamentals, analyst views, and insider activity. (src/…/daily-market-brief.ts, src/…/stock-research-overlay.ts, src/…/StockAnalysisPanel.ts)
References: src/…/daily-market-brief.ts• L19-44 src/…/daily-market-brief.ts• L317-369 src/…/stock-research-overlay.ts• L47-59 src/…/StockAnalysisPanel.ts• L71-140
Energy shock scenarios
Energy shock scenarios estimate how a disruption at a major chokepoint could affect a country’s oil or gas supply. They turn observed import flows, supplier origin, refinery output, demand, stocks, and route data into a bounded scenario result rather than a forecast of an actual shortage. (server/…/compute-energy-shock.ts, server/…/_shock-compute.ts)
The oil result requires both a crude import measure and a measured Gulf-origin share. It can then account for refinery product yields, product trade, stock cover, and whether a country is a net exporter. Hormuz scenarios also model the limited recovery available through the Saudi, UAE, and northern Iraqi bypass routes. Missing origin or flow data does not become a proxy value; the result reports unsupported or partial coverage instead. (server/…/compute-energy-shock.ts, server/…/_hormuz-bypass.ts)
Gas results use measured Qatar and UAE LNG origin for Hormuz when available. Other gas route sensitivities use stated route assumptions. The result keeps pre-crisis baselines separate from current flows, labels data limits, and exposes live chokepoint flow as context rather than silently changing the scenario severity. (server/…/compute-energy-shock.ts, server/…/_shock-compute.ts)
This diagram shows how the scenario distinguishes measured exposure from route assumptions before producing an assessment.
flowchart LR
A[Country and chokepoint request] --> B[Oil and gas observations]
B --> C[Origin and route exposure]
C --> D[Disruption and bypass scenario]
D --> E[Product loss and stock cover]
E --> F[Assessment, limits, and coverage state]
References: server/…/_hormuz-bypass.ts• L3-20 server/…/_hormuz-bypass.ts• L23-76 server/…/_hormuz-bypass.ts• L86-107 server/…/_shock-compute.ts• L142-172 server/…/_shock-compute.ts• L527-582 server/…/_shock-compute.ts• L808-878 server/…/compute-energy-shock.ts• L239-323 server/…/compute-energy-shock.ts• L354-520 server/…/compute-energy-shock.ts• L547-645 server/…/compute-energy-shock.ts• L647-745 server/…/compute-energy-shock.ts• L748-907
Attribution and evidence
Attribution is part of the product contract. It tells the reader which article or provider supports a claim and separates source reliability from event importance. The system favors a visible link, citation, or provenance note over an unsupported model statement.
Source grounding
Global and country prose carries source markers when grounding articles exist. Producers check markers against real source records and remove invalid markers. Source-bound country claims must remain supported by the cited article title and any cited World Monitor evidence. Claim checks bind numbers, names, dates, and status qualifiers to the cited material. Unsupported sections are withheld, and an English country brief is rejected when no grounded situation claim survives. (server/…/get-country-intel-brief.ts, scripts/_insights-brief.mjs)
The country page keeps source title, publisher, URL, and publication time together. It links citations to matching news and can include an evidence footer. This preserves the difference between a claim, its source, and the age of that source. (src/…/brief-sources.ts, src/…/format-intel-brief.ts, src/…/CountryBriefPage.ts)
Country coverage and signal observations extend this rule beyond prose. Each incident or observation carries its source identity, time basis, scope, and coverage state. A caller can therefore avoid treating a coordinate match, a source snapshot, or an unavailable family as a direct claim about national conditions. (server/…/get-country-coverage.ts, shared/country-signal-observations.ts)
References: server/…/get-country-intel-brief.ts• L130-209 server/…/get-country-intel-brief.ts• L378-475 server/…/get-country-intel-brief.ts• L514-631 scripts/_insights-brief.mjs• L489-647 src/…/brief-sources.ts• L8-94 src/…/format-intel-brief.ts• L22-73 src/…/CountryBriefPage.ts• L523-549 server/…/get-country-coverage.ts• L203-216 shared/country-signal-observations.ts• L101-125
Source attribution inventory
The source attribution inventory records which external providers the product uses. It maps observed hosts to provider identities and license posture. It keeps transport hosts separate from the publisher or provider that readers should recognize. Dynamic hosts need explicit coverage, and provider identity changes need review. (scripts/source-attribution.mjs)
References: scripts/source-attribution.mjs• L951-996 scripts/source-attribution.mjs• L1143-1234 scripts/source-attribution.mjs• L1434-1557 scripts/source-attribution.mjs• L1742-1782
Historical intelligence
Historical intelligence preserves event records after short-lived live snapshots change. Readers can request a time-ordered timeline, search by meaning, or find similar past events. Event time stays separate from storage time, and weak similarity matches are withheld so a poor match does not look like a useful precedent. (convex/intelHistory.ts, convex/schema.ts, server/…/get-intel-timeline.ts, server/…/search-intel-history.ts, server/…/get-similar-events.ts)
The timeline requires a domain or country scope and supports bounded cursor reads. Semantic search embeds a normalized query and applies bounded scope and result limits. Similar-event search uses a shorter precedent list with a minimum similarity score, unlike broad search which does not impose that precedent threshold. Both semantic reads cache successful results only and return upstreamUnavailable when the embedding provider or history store cannot answer. The archive accepts repeated seed runs without duplicating an event by its identity. Operators can retract a named poisoned record and keep its identity suppressed until the upstream item stops returning. (convex/intelHistory.ts, server/…/search-intel-history.ts, server/…/get-similar-events.ts, server/…/get-country-history.ts)
Country history is a separate daily country view for score and resilience points, key signals, and top events. It limits the requested window by access level, validates each point and its capture time, and marks gaps or methodology changes so a reader does not compare incompatible values as one continuous series. A missing or unreadable Redis history is reported as unavailable rather than as an empty history. (server/…/get-country-history.ts)
References: convex/intelHistory.ts• L12-31 convex/intelHistory.ts• L41-69 convex/intelHistory.ts• L199-325 convex/intelHistory.ts• L434-608 convex/intelHistory.ts• L647-850 server/…/get-intel-timeline.ts• L20-64 server/…/search-intel-history.ts• L24-78 server/…/get-similar-events.ts• L20-76 server/…/get-country-history.ts• L10-64
Research outputs
Research outputs answer a defined question over a fixed observation window. Unlike live briefs, the data set, metric method, source record, and edition version are part of the published result.
Published research reports
The report builder creates a report page, a research hub, and CSV and JSON downloads from committed snapshots and report definitions. Each value has a source, period, transformation, and raw value. The build stops when coverage is incomplete or prose names a metric that does not exist. Published editions use an append-only index, so a correction creates a new version instead of silently changing an old report. (scripts/build-research-reports.mjs, shared/…/index.mjs)
References: scripts/build-research-reports.mjs• L61-200 shared/…/index.mjs• L1-8
GDELT document search
GDELT document search gives topic research and country pages a bounded article set. It reads seeded topic data and a rolling country index instead of running a live crawl during a request. Country results require the title to name the country. The service distinguishes missing seed data, failed reads, unreadable suppression data, and a real empty match. (server/…/search-gdelt-documents.ts)
References: server/…/search-gdelt-documents.ts• L12-37 server/…/search-gdelt-documents.ts• L91-209
Analyst context
The analyst combines current briefs with risk, market, forecast, macro, country, headline, article, and energy context. It uses those products as evidence for a broader question rather than replacing their individual views. The context assembler selects data by domain and question, adds named market quotes and relevant energy measures, and records which source blocks are active. (server/…/chat-analyst-context.ts, server/…/chat-analyst-prompt.ts)
The analyst reads materialized GDELT headlines instead of fetching a live document search for each request. It scopes topics by domain, ranks matching headlines, removes repeated titles, adds source and coarse age labels, and keeps keyword article search separate from ambient headline context. Digest results are suppressed when the revocation set cannot be checked. All feed-derived text is sanitized and placed in a delimited user data block, while the system prompt contains instructions only. (server/…/chat-analyst-context.ts, server/…/chat-analyst-prompt.ts)
The analyst uses the question's full instrument vocabulary to put named quotes first. Quote labels, changes, and currencies make values readable across commodities, indices, exchange rates, and non-US listings. If a streamed answer states a price that does not match the live context within a small rounding tolerance, the stream adds a visible unverified caveat before completion rather than presenting the value as current fact. (server/…/chat-analyst-context.ts, server/…/chat-analyst-grounding.ts)
The analyst prompt gives domain-focused questions only the related context sections and requires the answer to state when live context is absent. It tells the model to treat feed text as data rather than instructions and preserves the distinction between current evidence and unsupported inference. (server/…/chat-analyst-prompt.ts)
References: server/…/chat-analyst-context.ts• L92-121 server/…/chat-analyst-context.ts• L294-317 server/…/chat-analyst-context.ts• L762-779 server/…/chat-analyst-context.ts• L782-970 server/…/chat-analyst-context.ts• L1018-1064 server/…/chat-analyst-context.ts• L1094-1237 server/…/chat-analyst-prompt.ts• L10-32 server/…/chat-analyst-prompt.ts• L50-117 server/…/chat-analyst-prompt.ts• L120-160
Analyst price grounding
Analyst price grounding checks numeric price claims in a streamed answer against the live context and the user's question. It recognizes currencies and magnitude suffixes, allows normal rounding, and leaves bare counts, years, and percentages outside this check. Unsupported prices are not rewritten after delivery; the stream adds a separate caveat before its terminal event. (server/…/chat-analyst-grounding.ts)
References: server/…/chat-analyst-grounding.ts• L20-65 server/…/chat-analyst-grounding.ts• L67-119 server/…/chat-analyst-grounding.ts• L121-193
Storage and delivery
The system uses different storage forms for different lifetimes. Rolling snapshots support fast shared reads. Personal envelopes support a frozen edition. Durable history supports comparison across time. Static research pages support a versioned public record. Live country coverage and signal observations also carry source clocks and coverage states so a short-lived read does not look like a durable fact.
Shared snapshots
Global insights, country briefs, regional results, tension status, and cross-source signals use shared or scoped caches suited to their update rate. Country cache identity includes language, premium context, framework, material energy and import-dependency years, and monitored airport status. Reader paths distinguish missing data from an upstream failure when that difference affects trust. (server/…/_country-brief-context.ts, server/…/get-country-intel-brief.ts, server/…/get-pizzint-status.ts)
Risk scores keep a current result, a stale fallback, and time-based trend history. A fresh complete build can update the live and historical records. A failed build leaves the previous result intact and marks the fallback as degraded. Risk payloads carry the published methodology version, while daily history keeps its method version per record so older series remain interpretable. (server/…/get-risk-scores.ts, server/…/_risk-config.ts)
Energy and port context use freshness states rather than treating every successful cache read as current. The energy profile reads sub-daily gas-storage and electricity values separately from the slower national spine, validates regional provider records and observations, and reports whether the latest series are available, partial, stale, or unavailable. (server/…/_regional-energy-feeds.ts, server/…/get-country-energy-profile.ts, server/…/get-country-port-activity.ts)
References: server/…/_country-brief-context.ts• L41-76 server/…/get-country-intel-brief.ts• L382-438 server/…/get-pizzint-status.ts• L47-83 server/…/get-risk-scores.ts• L2222-2275 server/…/get-risk-scores.ts• L2281-2363 server/…/_regional-energy-feeds.ts• L27-54 server/…/get-country-energy-profile.ts• L396-449 server/…/get-country-port-activity.ts• L41-126
Personal brief editions
The personal brief envelope is the shared contract for the dashboard, magazine, email, Telegram, Slack, and other delivery channels. It contains the issue, reader-facing digest, story cards, source links, and explanations. A canonical English envelope can have an optional localized sibling, while the envelope language identifies which edition a reader receives. It is versioned and retained for a limited period. (scripts/seed-digest-notifications.mjs, scripts/…/brief-compose.mjs, shared/brief-envelope.d.ts)
References: scripts/seed-digest-notifications.mjs• L157-206 scripts/…/brief-compose.mjs• L55-71 shared/brief-envelope.d.ts• L5-20 shared/brief-envelope.d.ts• L144-180
Presentation and interfaces
The dashboard, APIs, agent tools, and delivery channels read shared product contracts. They present the same evidence with different controls rather than producing separate interpretations.
Dashboard views
The global insights view prefers a server-precomputed world brief and ranked story snapshot. It can paint cached or prefetched content early, rerank stories with current signal quality, and add sentiment, convergence, and focal-point views. Desktop can fall back to client analysis when the server snapshot is unavailable; mobile does not run that heavy client path. Story badges count distinct publishers rather than repeated articles, while source rosters, provenance, and freshness expose how the view was compiled. (src/…/InsightsPanel.ts)
The country panel puts its brief beside risk, news, markets, infrastructure, energy, maritime, and trade context. Energy context can include regional provider feeds with their coverage state. Maritime context can show the last usable port snapshot and marks it stale when the refresh window has passed. Its market section also shows the source snapshot time when available and states when that time is unavailable; it does not present the snapshot time as the time of each quote. A regional board joins a weekly narrative with its structured snapshot. These views let a reader move from summary to evidence without losing the selected place or time frame. (src/…/CountryBriefPage.ts, src/…/CountryDeepDivePanel.ts, src/…/CountryBriefPanel.ts, src/…/RegionalIntelligenceBoard.ts)
References: src/…/InsightsPanel.ts• L196-234 src/…/InsightsPanel.ts• L309-345 src/…/InsightsPanel.ts• L347-429 src/…/InsightsPanel.ts• L436-600 src/…/InsightsPanel.ts• L644-757 src/…/InsightsPanel.ts• L779-823 src/…/CountryBriefPage.ts• L394-549 src/…/CountryDeepDivePanel.ts• L479-609 src/…/CountryDeepDivePanel.ts• L2972-3026 src/…/CountryBriefPanel.ts• L135-217 src/…/CountryBriefPanel.ts• L220-253 src/…/RegionalIntelligenceBoard.ts• L21-40
Latest brief panel
The latest brief panel is a premium dashboard entry point for a user's daily editorial magazine. It reads a user-scoped latest-brief result and presents a ready issue with its date, greeting, thread count, language, and signed magazine link. The latest-brief endpoint reads the digest pointer and validates the stored envelope before it reports ready; before the issue is ready, it reports composing instead of presenting incomplete content. (src/…/LatestBriefPanel.ts, api/latest-brief.ts)
Access state is part of the panel's product behavior. Sign-in, upgrade, entitlement verification, and service failure use different messages, while account changes and tab visibility can trigger a fresh read. The endpoint retries one timed-out cache read, but a persistent cache failure returns service unavailable rather than pretending that the issue is still composing. The panel cancels or ignores work that no longer belongs to the active user, and it offers referral sharing only after the user's share profile is available. (src/…/LatestBriefPanel.ts, api/latest-brief.ts)
References: src/…/LatestBriefPanel.ts• L39-53 src/…/LatestBriefPanel.ts• L137-207 src/…/LatestBriefPanel.ts• L222-343 src/…/LatestBriefPanel.ts• L366-443 src/…/LatestBriefPanel.ts• L519-659 api/latest-brief.ts• L17-24 api/latest-brief.ts• L76-96 api/latest-brief.ts• L180-340
Country story and report outputs
Country outputs preserve the loaded brief as a dated snapshot. A story presents selected sections as slides. A report groups sections by topic and marks sections that are incomplete, so an export cannot hide gaps in the source view. The output freezes the current content and replaces live controls with readable values, which lets the artifact stand apart from the active panel. (src/…/CountryBriefOutput.ts, src/…/CountryDeepDivePanel.ts)
Decision and commodity outputs are separate evidence captures. A decision brief compares baseline and disruption cases and records modeled impact, assumptions, evidence, constraints, and unknowns. A commodity brief compares recorded origin countries with modeled routes and states when route, production, or supply evidence is unknown. Optional world-production evidence can be unavailable without invalidating the country vulnerability result. (src/…/CountryBriefOutput.ts, src/…/decision-brief.ts)
The page supports print, PDF, image, HTML, JSON, CSV, and evidence Markdown paths. Structured exports and evidence export have entitlement checks. The output records capture time, source dates, selected scope, scenarios, and products so a reader can understand what the artifact represented at capture time. HTML and JSON downloads become available only after the related capture or delivery step succeeds. (src/…/CountryBriefPage.ts, src/…/CountryBriefOutput.ts)
References: src/…/CountryBriefOutput.ts• L31-88 src/…/CountryBriefOutput.ts• L119-186 src/…/CountryBriefOutput.ts• L189-218 src/…/CountryBriefOutput.ts• L354-418 src/…/CountryBriefOutput.ts• L421-478 src/…/CountryDeepDivePanel.ts• L4228-4304 src/…/CountryBriefPanel.ts• L215-262 src/…/CountryDeepDivePanel.ts• L294-339 src/…/CountryBriefPage.ts• L713-815
API and agent access
The intelligence service and MCP tools expose global and country briefs, country history, country coverage, qualified country observations, country facts, port activity, regional briefs, cross-source signals, timelines, historical search, similar events, and related analysis. These callers read accepted snapshots or the same service routes as the dashboard, so source, scope, attribution, and freshness rules remain shared. (server/…/handler.ts, api/…/rpc-tools.ts)
The service validates assigned country codes and bounds windows, cursors, family names, and response size before returning country data. This keeps agent results aligned with the panel while making unavailable or partial source coverage visible to callers. (server/…/handler.ts, server/…/get-country-history.ts, server/…/get-country-coverage.ts, server/…/get-country-signal-observations.ts)
References: server/…/handler.ts• L1-77 server/…/get-country-history.ts• L33-64 server/…/get-country-coverage.ts• L232-371 server/…/get-country-signal-observations.ts• L16-72 api/…/rpc-tools.ts• L909-1076
Sharing and scheduled delivery
The personal magazine reads a signed per-user edition envelope. The latest brief panel opens that signed magazine URL as the private reader entry point. A share link creates a short-lived public pointer that renders non-personalized fields only. The same frozen edition can therefore support a private reader, scheduled delivery, and public sharing without rebuilding the analysis. (src/…/LatestBriefPanel.ts, api/latest-brief.ts, api/…/[issueDate].ts, api/…/share-url.ts, api/…/[hash].ts)
References: src/…/LatestBriefPanel.ts• L557-659 api/latest-brief.ts• L231-340 api/…/[issueDate].ts• L81-299 api/…/share-url.ts• L17-27 api/…/[hash].ts• L1-19 server/…/brief-render.js• L1-18
Change checklist
When these files or sections are changed, remember to consider these:
- Keep the global producer, accepted snapshot validator, dashboard loader, and agent projection aligned when insight shape or source fields change.
- Keep headline classification levels, categories, real-world severity guidance, severity mapping, cache keys, model routing, and downstream labels aligned.
- Keep classification input limits, enum validation, AI-route cache separation, fallback token budget, and unavailable-state behavior aligned across fresh and cached results.
- Keep situation-deduction query, geographic context, prediction-market context, premium framework, sanitization, cache identity, AI routing, and pre-gateway timeout behavior aligned.
- Keep country cache identity aligned with language, premium context, framework, energy years, import-dependency years, airport status, and AI route.
- Keep digest revocation checks, country matching, relevance filtering, prompt-line sanitization, source parsing, and shared-cache behavior aligned.
- Keep evidence kinds, public labels, freshness limits, fact sentences, stable IDs, and claim validators aligned with the country page contracts.
- Keep country section rules aligned with source citations, evidence citations, forward-looking evidence, withheld claims, language behavior, and the requirement for a grounded situation claim.
- Keep country coverage queries, headline matching, event classification, lane mapping, clustering order, structured reconciliation, approximate containment, source states, time windows, and agent output aligned with the country panel.
- Keep country signal family names, source projections, country filtering, coordinate scope, attribution, time basis, flight cursors, partial markers, and byte limits aligned across the shared contract and service handler.
- Keep country history access limits, point validation, date windows, capture clocks, gap markers, and unavailable-state meaning aligned with the history producer and reader.
- Keep country facts and port activity country validation, cache freshness, public-source fallback, availability state, stale marker, and displayed timestamps aligned.
- Keep national and regional energy field names, provider identity, source URLs, period parsing, local time offsets, direct sub-daily reads, observed-measurement flags, series freshness, partial coverage, and no-store behavior aligned across the energy service and country panel.
- Keep the country source contract aligned across website services, host readers, raw-signal identity checks, and supply-chain country scoping.
- Keep country source readers, host validation, request arguments, section identities, and state meanings aligned between website and embedded paths.
- Keep country market fetch time aligned across the website callback, prediction response, controller result, panel contract, and displayed snapshot note.
- Keep source numbering aligned across producer records, claim checks, formatters, footers, and exported evidence.
- Keep section identifiers, topic membership, coverage markers, panel update methods, and story/report snapshots aligned.
- Keep decision and commodity capture inputs, optional evidence, timestamps, HTML output, JSON output, and access checks aligned.
- Keep personal envelope versions aligned with the composer, magazine reader, delivery renderers, localized sibling selection, and public redaction rules.
- Keep brief language precedence, shared language codes, deliverable-language configuration, account binding, and English fallback aligned between Settings, Convex user records, the digest composer, and envelope readers.
- Keep the latest brief response states, signed magazine URL, premium access states, account identity checks, refresh triggers, cache retry behavior, and magazine route aligned.
- Keep composing refresh, account-switch cancellation, entitlement rechecks, and referral-share availability aligned with the user and issue shown by the panel.
- Keep historical timeline scope validation, cursor limits, store indexes, and
upstreamUnavailablemeaning aligned with search and similar-event reads. - Keep historical query normalization, embedding dimensions, similarity thresholds, result limits, cache-success rules, and provider denial behavior aligned across semantic search and precedent lookup.
- Keep historical append dedupe, retraction tombstones, restore behavior, retention clocks, and operator review responses aligned.
- Keep signal type and severity values aligned between aggregators, cached payloads, service adapters, generated contracts, and labels.
- Keep tension pair configuration, score freshness, evidence channel allowlists, evidence timestamps, and no-store fallback behavior aligned.
- Keep CII formula version, coefficients, country attribution, cyber exclusion, ACLED/UCDP/GDELT fallback, strike-pressure policy, advisory provenance, input coverage, and strategic top-five roll-up aligned with the public methodology note.
- Keep risk cache versions, rejected-build behavior, stale fallback, trend snapshots, daily history, input health metadata, and methodology disclosures aligned when score inputs change.
- Keep energy shock chokepoint and fuel contracts, measured origin shares, route assumptions, bypass recovery, baseline windows, coverage states, and limitation text aligned.
- Keep energy shock oil and gas fields, current-flow context, stock-cover labels, cache versions, and assessment wording aligned when scenario inputs change.
- Keep analyst context topic scope, materialized headline freshness, digest revocation checks, prompt sanitization, domain gates, and active-source labels aligned.
- Keep analyst quote selection, instrument aliases, configured labels, currencies, change fields, question context, price parsing, rounding tolerance, and streamed caveats aligned.
- Keep analyst system instructions separate from feed-derived context, delimiter handling, domain section gates, no-context behavior, and question placement aligned.
- Keep research snapshot coverage, metric names, report prose, downloads, and edition versions aligned.
- Keep server insight snapshots, early-paint caches, client fallback rules, publisher-based corroboration counts, source rosters, freshness labels, and provider-setting invalidation aligned in the dashboard.
Important failure modes
| Trigger | Consequence | Guard |
|---|---|---|
| A brief cites a source number that does not exist. | A claim can show a broken or misleading citation. | Producers validate citation indexes before publication. |
| A fresh synthesis fails while the story list is valid. | A good prior brief can be replaced by degraded prose. | The accepted story result and last known-good snapshot are preserved. |
| The digest suppression set cannot be read. | A shared country brief could retain a revoked article for its cache lifetime. | Shared grounding fails closed until suppression data is readable. |
| A country evidence source is stale or malformed. | Old data can look like current country fact. | Each evidence builder drops its own items using type-specific freshness checks. |
| A country energy cache read fails. | Missing energy data can look like measured zero or successful partial coverage. | The profile returns an unavailable error and marks the response no-store. |
| A risk input read errors during a build. | A new score can mix incomplete inputs with current inputs. | The build is rejected and the prior result is served as degraded stale data. |
| A risk build has no usable earlier score. | The reader can mistake unknown movement for no change. | Trend direction is unspecified until a valid prior snapshot exists. |
| A cached event classification contains an unknown level or category. | A downstream view can show an invalid threat label. | Cache hits pass the same enum validation as fresh model results. |
| A prediction-market title contains a line break or prompt instruction. | Untrusted feed text can look like a separate market row or model command. | Situation deduction sanitizes each title as one prompt line before use. |
| Situation deduction runs past the edge gateway budget. | The caller gets a timeout and no reusable analysis. | The reasoning call fails closed before the gateway limit and returns an explicit error state. |
| A situation request changes AI routing but reuses an old shared cache entry. | A caller can receive analysis produced under the wrong provider policy. | The cache key and model call carry the resolved AI routing policy. |
| A premium country claim adds a name or fact not supported by its cited title or evidence. | A source link can appear to support false evidence. | Source-bound validation withholds the claim. |
| A country brief has no relevant grounded headline. | The analyst could invent a current situation or short-term outlook. | The English path returns no brief instead of publishing unsupported prose. |
| A coverage feed returns no recognizable items or all dates are unusable. | A caller can mistake a broken feed for a quiet country. | The source status reports unknown or failed instead of empty. |
| A structured coverage cache is missing or older than its freshness budget. | A caller can treat unavailable or old incidents as a quiet period. | The producer reports failed or stale and keeps stale events visibly marked. |
| A regional energy record has an invalid period, future fetch time, or non-HTTPS data link. | Unsupported or misdated energy context can enter a country view. | Feed decoding rejects the record and reports an error state. |
| All observations for an energy series are beyond their age budget. | Old regional conditions can look current. | The feed marks the series stale and exposes its coverage state. |
| Port activity is older than the seven-day current window but within the serve window. | A reader can treat last month's activity as current. | The response remains available only with an explicit stale marker. |
| Port activity is older than the allowed serve window or has a future write time. | The panel can show a figure for a period that no longer matches the stated window. | The service returns unavailable and rejects future-dated payloads. |
| A latest-brief cache read times out once. | A transient store blip can make a ready issue appear unavailable. | The endpoint retries the timed-out read once within a bounded response budget. |
| The latest-brief store remains unavailable or its envelope is invalid. | The panel can show a false composing state or open a broken magazine link. | Persistent read errors return service unavailable, while envelope assertion failures count as a miss. |
| A latest-brief response resolves after the user signs out or changes accounts. | The previous user's magazine entry can appear in the new session. | The panel aborts in-flight work and checks the active user before rendering. |
| The client entitlement view conflicts with the server's premium decision. | A paying user can see an upgrade prompt or an endless retry state. | The panel classifies the denial, retries transient desyncs for a bounded period, and shows a separate verification state when the budget ends. |
| The daily edition is still being composed. | The panel can appear stuck or force a reader to reload the dashboard. | The panel polls while composing and refreshes when the tab becomes visible. |
| A saved brief language is not in the active delivery allowlist. | Settings can promise a language that the composer cannot produce. | Shared deliverable-language calculation gates the Settings list and composer target. |
| A brief-language read or write finishes after an account switch. | A preference can be shown or written for the wrong user. | The browser binds the operation to the starting Clerk user and the mutation checks the expected user ID. |
Key files
| File | Why to read it |
|---|---|
| scripts/seed-insights.mjs | Global story selection, accepted snapshot lifecycle, and fallback behavior. |
| scripts/_insights-brief.mjs | Global narrative shape, claim checks, and source grounding. |
| server/…/get-country-intel-brief.ts | Country brief contract, source-bound claims, evidence, citations, language behavior, and cache inputs. |
| server/…/_country-brief-context.ts | Shared country grounding, revocation filtering, matching, relevance, and cache context. |
| server/…/_country-brief-evidence.ts | Public-safe evidence kinds, freshness checks, attribution, and fact text. |
| server/…/get-country-coverage.ts | Panel-aligned country headlines, incidents, structured reconciliation, source states, and degradation. |
| server/…/_country-coverage-structured.ts | Structured incident lanes, freshness states, approximate containment, and unavailable browser-only sources. |
| server/…/_country-coverage-feeds.ts | Country feed queries, headline filtering, event classification, and clustering input. |
| shared/country-signal-observations.ts | Common observation shape, attribution, time basis, scope, partial results, and family projection. |
| server/…/get-country-signal-observations.ts | Agent access to country signal families, flight paging, deadlines, and response bounds. |
| server/…/get-country-history.ts | Daily country history access, validation, freshness, and break markers. |
| server/…/classify-event.ts | Headline threat classification, cache validation, severity mapping, AI routing, and unavailable results. |
| server/…/get-pizzint-status.ts | Dyad tension scores, optional GDELT data, evidence validation, and fallback state. |
| server/…/deduct-situation.ts | Focused analysis, prediction-market context, premium framework, sanitization, AI routing, cache identity, and graceful timeout behavior. |
| server/…/search-intel-history.ts | Meaning-based history search, scope and result bounds, embedding use, and unavailable-store signaling. |
| server/…/get-similar-events.ts | Short precedent lookup, similarity floor, and failure behavior. |
| server/…/get-risk-scores.ts | CII inputs, formula disclosure, trend history, rejected builds, stale fallback, and coverage health. |
| server/…/_risk-config.ts | Editorial formula version, strike decay, cyber exclusion, and strategic roll-up policy. |
| server/…/get-country-risk.ts | Country risk projection and fail-closed handling for missing global inputs. |
| server/…/compute-energy-shock.ts | Country energy disruption scenario, evidence selection, coverage states, assessments, and cached results. |
| server/…/_shock-compute.ts | Shared energy scenario rules for origin shares, product balances, gas sensitivity, stock cover, and limitations. |
| server/…/_hormuz-bypass.ts | Hormuz rerouting assumptions and the resulting loss calculation for affected exporters. |
| server/…/get-country-energy-profile.ts | Country energy context, direct sub-daily reads, source coverage, regional feed assembly, and partial-read behavior. |
| server/…/_regional-energy-feeds.ts | Regional energy cache validation, period handling, source attribution, and freshness states. |
| server/…/get-country-facts.ts | Public country facts, identity checks, caching, and unavailable fallback. |
| server/…/get-country-port-activity.ts | Port activity allowlist, current and serve-age boundaries, stale state, and country maritime context. |
| convex/intelHistory.ts | Durable history, append dedupe, retraction, retention, timeline reads, and semantic search. |
| server/…/get-intel-timeline.ts | Scoped historical timeline reads, cursor limits, and unavailable-store signaling. |
| scripts/build-research-reports.mjs | Fixed-window research metrics, coverage checks, and downloads. |
| server/…/chat-analyst-context.ts | Analyst evidence assembly, question-aware quote selection, materialized headline selection, revocation handling, and prompt-safe formatting. |
| server/…/chat-analyst-grounding.ts | Streamed price extraction, live-context comparison, and unverified-price caveats. |
| server/…/chat-analyst-prompt.ts | Domain context gates, data delimiters, analyst instructions, and prompt-injection boundary. |
| src/…/InsightsPanel.ts | Server-first brief presentation, client fallback, signal views, source attribution, freshness, and cache behavior. |
| src/…/LatestBriefPanel.ts | User-scoped daily brief entry point, issue readiness states, premium access handling, signed magazine navigation, and referral sharing. |
| api/latest-brief.ts | Authenticated latest-issue lookup, envelope validation, localized selection, signed magazine URL, and bounded cache retry behavior. |
| src/…/brief-language.ts | Account-bound browser access to the reader's brief-language preference. |
| convex/users.ts | Brief-language preference validation, effective-language resolution, and delivery-language disclosure. |
| shared/ui-languages.js | Shared language list, fallback precedence, and active deliverable-language calculation. |
| scripts/…/brief-l10n.mjs | Localization target selection and safe localized-envelope write semantics. |
| src/…/CountryBriefController.ts | Country section lifecycle, parallel loading, market snapshot metadata, premium reads, and stale-result protection. |
| src/…/country-brief-source.ts | Shared website and host source contract for country intelligence, raw signals, and scenario reads. |
| src/…/country-brief-host-transport.ts | Embedded reader validation, caching, concurrency, and cancellation. |
| src/…/index.ts | Country market selection and the source snapshot time passed to the country brief. |
| src/…/CountryBriefPanel.ts | Shared country section contract, energy and maritime data shapes, market metadata, and state update surface. |
| src/…/CountryDeepDivePanel.ts | Country presentation, market snapshot wording, evidence quality, coverage, access states, and output snapshot assembly. |
| src/…/CountryBriefPage.ts | Country citations, sharing, export formats, and entitlement checks. |
| src/…/CountryBriefOutput.ts | Dated country story/report snapshots, decision captures, commodity evidence, and downloadable artifacts. |
| scripts/source-attribution.mjs | Provider identity, host discovery, review, retirement, and attribution records. |
| shared/brief-envelope.d.ts | Canonical personal edition contract, localized sibling identity, and consumer compatibility. |
| api/…/[issueDate].ts | Signed magazine access and per-user edition reads. |
| server/…/handler.ts | Programmatic intelligence service surface and shared registration of brief, signal, context, country history, risk, and durable history reads. |
| api/…/rpc-tools.ts | Agent-facing brief and analysis projections. |