The current sweep supports a refresh queue, not a wholesale rewrite of every assessment. The active control lane is now cyber/APT and nation-state actor coverage. The PRC APT/Typhoon label crosswalk is complete as a source-classed label-control packet, and the Iran MOU implementation watch remains parked until primary records appear or the lane is explicitly reopened. Near-term priority should stay on Iran and DPRK cyber source packets after the completed Russia state-cyber source packet, then NATO and allied force-posture follow-up, homeland and official threat-source refresh, Indo-Pacific PRC/Taiwan/South China Sea official-source updates, Africa official-source depth, space posture refresh, defense industrial-base budget and oversight updates, and map/maritime source routing.
Allied and multilateral source routing for defense-industrial capacity, AUKUS submarine industrial implementation, EU Readiness 2030, SAFE/EDIP/EDIS lanes, ICE Pact icebreaker and Arctic-warning industry, NATO industrial cooperation, allied DIB country crosswalks, UK defense investment/readiness implementation, Japan defense buildup implementation, allied workforce, shipbuilding, munitions, air and missile defense, drone/counter-UAS, critical materials, and implementation cross-checks.
Each gap should be closed only by adding a dated source note, source packet, tracker update, or matrix row. Do not silently remove a gap because it is inconvenient or stale.
When a row feeds another product, carry forward the source class, caveat tag, and freshness status. Do not carry over technical details that would reproduce exploitation or offensive procedure.
the corpus should treat defensive cyber as a standing source lane rather than a one-off topic. The highest-value structure is a recurring watch that links official advisories, vulnerability metadata, vendor mitigations, sector context, and caveats into a searchable corpus.
The weekly sweep supports a focused documentation update rather than a whole-corpus rewrite. The live queue already identified cyber/APT/state actors as the active control lane. The current source pass found a fresh FBI/CISA Russia source update dated June 26, 2026 and enough official/allied source coverage to packetize the Russia state-cyber lane.
The Russia cyber lane should not be treated as one undifferentiated APT list. Public records mix GRU military-intelligence cases, FSB-linked political interference and espionage warnings, possible SVR lanes that require separate source capture, Ukraine-war disruptive activity, legal actions, sanctions, reward notices, and allied cyber-center warnings.
Collections hold the supporting infrastructure of the the corpus corpus. They organize reusable evidence (source packets), collection workflow tools (trackers), explanatory context (explainers), synthesis products (matrices and crosswalks), dated event sequences (timelines), actor framing (profiles), and provenance records (source notes).
This taxonomy gives analysts a compact way to tag uncertainty, source limitations, and refresh needs across all topics. It supplements analytic confidence by making the reason for caution searchable.
These standards govern product structure, source handling, style, timestamps, metadata, confidence labeling, and explainer content across the the corpus corpus.
This standard makes the corpus products easier to use in analytic systems by giving each product a stable set of machine-readable fields. The static generator now exports the documentation corpus as browser JavaScript, JSON, and CSV.
Explainers are reader-facing documentation products. They should answer the basic question a careful reader brings to the corpus: what is this topic, why does it matter, how does the system work, what claims are strong or weak, and what should be watched next?
Source Registers provide the vetted, classified lists of source families used across the corpus. They record publisher, access patterns, source class, known limitations, and recommended use for each family or lane.
Templates provide the canonical starting structure for new products. Always begin from the template that matches the product type and then adapt content while preserving required header fields and sections.
Africa map work needs a dedicated lane because continent-level orientation can hide major subregional differences. Products should separate command-area framing, AU/UN multilateral context, national issuer perspectives, geographic-name questions, and historical/archival maps.
Middle East maritime map work should support static chokepoint orientation and source routing, not live maritime analysis. Hormuz, Bab el-Mandeb, the Red Sea, Suez, and Eastern Mediterranean lanes require strong separation between map orientation, nautical chart source provenance, legal/diplomatic source claims, and commercial AIS leads.
Arctic map use should stay split into five lanes: static orientation, command-area framing, nautical/ocean source routing, issuer-perspective national maps, and multilateral or research context. No single public map should be treated as proof of access, mobility, infrastructure vulnerability, military readiness, or operational feasibility.
MarineTraffic and similar public AIS tools can help discover a maritime question, but they should not become a the corpus map layer or operational product. Use AIS sources to cue follow-on research into official maritime notices, port authorities, NOAA chart families, IMO records, shipping/insurance reporting, and dated source packets.
If a map lane is used in an assessment, source packet, or tracker, carry forward its caveat tag: map-reference-only, commercial-data-limit, source-lag, or current-watch.
Use this guide when a product needs a map source but the right map lane is not obvious. The goal is to choose the least risky public source family that answers the orientation question without drifting into operational use.
The generator now adds source-health fields to each corpus export record. These fields make it easier to find under-described, stale, gap-marked, watchlisted, or refresh-due records without manually reading every product.
The workspace should function as a triage surface for the enriched corpus, not only as a document browser. Metadata-aware routes make it possible to quickly isolate records that need refresh, carry caveats, or belong to defensive cyber source lanes.
The generator adds a sourceHash field to each exported corpus record. The hash is a short SHA-256 digest of the Markdown source text and is intended to help identify whether a product changed between generated exports.
This afternoon check does not change the corpus status. The U.S.-Iran MOU remains a reported signed-and-publicized current-event lane with active implementation-watch requirements. Current reporting continues to describe a signed MOU, Hormuz reopening or traffic-restoration provisions, oil-sanctions waiver claims, frozen-asset conditions, nuclear/IAEA-related language, and a 60-day negotiation window.
the corpus needs a distinct research lane for stratagems and warfare studies because strategic concepts often sit between official doctrine, academic theory, historical case work, professional military journals, and think-tank analysis. Without a separate lane, the corpus can over-rely on official strategy documents for concepts that are debated in scholarly and professional literature.
Stratagems and warfare research belong in the corpus as a conceptual and academic source lane. The purpose is to explain how scholars and professional military writers define strategy, deception, deterrence, coercion, innovation, mobilization, and warfare change, not to turn those concepts into instructions.
PRC cyber labels should be treated as dated source labels, not as a single normalized alias encyclopedia. The accessible official record in this pass supports a controlled crosswalk across several label families:
Track China and PLA source-family collection across official U.S., PRC issuer, Taiwan, allied/regional, cyber, legal, map, industrial, technology, and the corpus derived products.