Domain Paths Now Separate Teaching, Resources, Films, and Release History

Release at a glance

Grid FYI’s seven domain pages now present a maintained path rather than one mixed wall of cards. Use cases, Insights, unique resources, related films, and release history have distinct lanes. Publications whose first domain matches the page appear as domain-first material; explicitly tagged cross-domain connections remain available in a secondary collection. Empty lanes stay visible instead of borrowing release metadata to imply coverage that does not exist.

The release also adds two research-grounded, field-specific use cases:

• Authorize and Correct a Public Warning Across Evidence, Channels, and Jurisdictions follows incident evidence, geographic scope, protective-action authority, exact-message approval, channel-specific receipts, accessibility and language checks, correction, cancellation, and replay through a wholly synthetic county exercise.
• Coordinate Coalition Decision Logic Without Centralizing Sovereign Data or Authority follows a narrow decision contract, nationally controlled facts, permitted aggregate claims, source, model, release and action authority, degraded connectivity, provenance-based reconciliation, and correction through a fictional humanitarian-logistics exercise.

From Common Operating Picture to Common Operating Model is no longer a short conceptual essay carrying a white-paper label. It is now a research-grounded deep dive with an explicit six-object architecture, a reproducible synthetic capacity fixture, a worked state table, public-source context, failure injections, acceptance evidence, and implementation-specific Grid Developers links.

Why the collection structure changed

The previous domain renderer treated every matching item alike. A consequential release record could sit beside a use case as if both taught the subject. The same downloadable file could appear several times because multiple related publications referenced it. Films named by broad release updates could leak into domains where they had no direct educational relationship. A reader could encounter plenty of cards but still struggle to identify the starting use case, canonical paper, portable artifact, film, or release record.

The new structure uses the editorial catalog’s ordered domain list as an explicit relevance contract. The first domain identifies the publication’s primary home; later values create discoverable cross-domain relationships. This is a presentation and metadata rule, not a claim that a topic belongs to only one field.

Downloads are now deduplicated by stable route, with the most directly relevant maintained companion supplying the label and context. Films are deduplicated by stable film identity and are derived only from educational publications, not What’s New records. Release notes remain present in a small chronological ledger but no longer inflate the teaching collection or appear in “continue exploring” recommendations.

What the public-warning use case teaches

The fictional Harborline-27 exercise separates facts from authority and technical transport from public outcome. A pressure event is corroborated, a pre-event sample is rejected as proof of later conditions, a two-county draft is blocked because one originator lacks cross-jurisdiction scope, and a language variant is stopped because it names the wrong zone. Separate officials authorize exact message revisions. Channel results include acceptance, one observed receiver, a web success, and a timeout; the overall state is therefore partial handoff, not “delivered.”

A later geographic correction produces a referenced update and new exact-message authorization while preserving the earlier active state for replay. The fixture also distinguishes a CAP Cancel from a separately authorized public ending message. Its purpose is to make the evaluation oracle concrete, not to provide emergency instructions or claim alerting-system compliance.

What the coalition use case teaches

The fictional Harbor Lantern exercise asks whether three sovereign participants can satisfy an abstract relief-capacity requirement while keeping private facts and national authorities local. The shared package defines units, claim states, validity, recipient policy, versioning, calculation, and correction semantics. Participants publish only authorized aggregate commitments and constraints.

The exercise deliberately includes a proposed commitment, a disconnected authorization, a route bottleneck, separate national rerouting decisions, a delayed correction, duplicate delivery, and a final reserve release. The arithmetic is simple so the hard questions remain visible: which claim is eligible, which route is allocated, which message supersedes another, which result is stale, and which institution can actually act.

Exact boundaries

The new pages synthesize public FEMA, FCC, CISA, NIST, OASIS, NATO, and U.S. Defense Department sources. Those organizations do not endorse Grid. The fictional exercises are not customer deployments, operational plans, validated doctrine, approved warning copy, public-health guidance, system certification, interoperability conformance, security accreditation, or evidence of performance or outcome.

The common-operating-model paper similarly describes an architecture to evaluate. Provenance, explicit dependencies, versioning, access controls, audit records, and human authority are necessary properties for many consequential systems; their presence does not make a source correct, a rule valid, a system secure, or an action authorized.

How to verify this release

Open a domain page and confirm the five lanes remain distinct. Cross-domain connections should be disclosed behind their own control, resources and films should not repeat, and release history should be visually and semantically separate. Open each new use case and inspect the external sources, synthetic fixture, calculation tables, failure states, authority boundaries, and evaluation criteria. Open the common-operating-model paper and confirm the six-part exhibit, two worked tables, primary-source links, and exact developer handoffs.

Public means these Grid FYI pages ship in the current static build at their permanent routes. It does not describe Grid runtime, customer, accreditation, or operational availability.