-
Read sections.industry_chain, sections.cross_layer_connections, sections.model_releases, sections.product_updates, sections.application_trends, sections.ai_funding, sections.viral_ai_news, sections.official_social_updates, and sections.editorial_queue. Treat infrastructure, model/platform, product/function, application adoption, capital/commercial events, and potentially viral news as parallel intelligence tracks. Use the current Codex model to select the strongest items, write concrete Chinese explanations, organize sections, and produce varied X drafts. raw_summary contains source material for factual rewriting; do not discard it when the deterministic Chinese hint is generic.
-
When metadata.official_x_monitor.mode is codex_web_search, execute every query in sections.official_x_search_groups for the requested window. The groups are country-aware and put China first. Retain direct https://x.com/<handle>/status/<id> links, and add only posts published by the configured account. Also check sections.official_model_watchlist and sections.official_product_watchlist for vendors and products that do not expose a stable feed.
-
Execute the relevant batches in sections.industry_search_groups, starting with China. Use sections.industry_source_watchlist to return to company newsrooms, customer announcements, investors, exchanges, or regulatory filings. Discovery-only media and community sources may surface a lead, but they cannot confirm funding amounts, adoption figures, revenue, valuation, or infrastructure spending on their own.
-
Before writing, complete a freshness audit: confirm that every relevant X and industry search group was checked or name the failed group, and separately record first-party findings as model release, product/function update, application/adoption, funding/commercial event, ecosystem activity, or potential viral story. An account or page appearing in a watchlist is not evidence that it was searched. Do not finalize a briefing with an empty China official-source result until the CN groups have been checked explicitly.
-
Do not require a model launch for inclusion. Track major product releases, new features, application adoption, customer cases, user growth, pricing, revenue, partnerships, infrastructure, open-source projects, research breakthroughs, financing, policy or safety events, industry disputes, and fast-rising community discussions when they have clear AI relevance and credible links. Treat popularity as a distribution signal, not proof of truth.
-
Classify each item on two separate axes: industry_layer is only upstream, midstream, or downstream; event_types describes what happened, such as model_release, product_update, adoption, funding, acquisition, earnings, or policy. Capital is a cross-cutting event, never a fourth industry layer. A downstream application company remains downstream after raising money.
-
Save the final document as outputs/briefing_YYYY-MM-DD.md in the project directory. Then run the bundled validator and return a clickable local file link only after it passes:
