Coverage built for the analyst and the database.
CIE expressions are built from two separable layers. The grammar defines how tokens are composed, how clauses are structured, and how meaning derives from their combination. The Registry — a managed, versioned vocabulary — defines what those tokens resolve to: the specific named codes for actors, institutions, positions, actions, domains, and locations that give CIE expressions their semantic content.
An expression is syntactically valid by reference to the grammar alone. It is semantically valid from its resolution by the Registry. This separation is foundational: it allows the grammar to be stable while the vocabulary can grow, and it ensures persistent consistency of exact meaning, independent of the time, place, or circumstances of the encoding.
CIE is not an 'adaptation' or 'translation' of a separate source article, which is necessarily informationally lossy. It is instead an authoritative and formal encoding on its own.
The examples below are drawn from real events across different action types and information environments. They are not edge cases chosen to show the system's range — they are representative of what a working analyst encodes on any given day. The complexity varies; the underlying logic is the same throughout.
Head of government bilateral with domain scope and temporal span
A bilateral meeting between heads of state with senior ministerial participation, covering multiple defined domains, at a specified location, over a bounded time period. This is among the most common event types in political encoding — and the one where prose reporting most reliably loses the structurally important detail.
ind.hog <[mt]> - rus.hos, rus.min.dfns.exc.01 @ ind.hps - <{sp}> $ eng.hyc, eng.nuc - rus.hos > @ *.loc ∫ 04122025:05122025
Official military statement describing cross-border incidents with coordinates and casualties
A defense ministry spokesperson issues a public description of armed incidents at an international border, including approximate coordinates, unit-level force identifications, and casualty data. This encoding illustrates how CIE handles geographic precision, the separation of the statement act from the events being described within it, and quantified casualty reporting in a subsidiary clause.
tha.min.dfns.ary.spx [st.ds] - tha.ary {ak} khm.loc.3+ - {ak} @ ∫ ~ (13.9.no, 103.2.es).loc # *.ary, *.arf -[cl.uv] khm.ary [nu] tha.ary.unk.1+ [ij] *.8.+
Meteorological authority issues seismic and tsunami warnings at coordinate and prefecture level
A government meteorological agency issues a seismic event warning and a derived tsunami warning for named coastal prefectures. This example shows CIE at its most compressed — a high-information, time-critical event encoded in two subsidiary clauses. The brevity is not a limitation. When the event is discrete, the encoding needs nothing more.
jpn.min.infr.mteo.spx [st.wr] - $ natx.smsc ~ @ (40.8.no, 143.2.es) - {st.wr} natx.tsun @ jpn.sbs.amr, *.hkk, *.iwt
Source claim on nonpublic military coordination, with full credibility metadata
Not all political information arrives publicly confirmed. A substantial share of what matters in intelligence and risk analysis comes through channels that require explicit sourcing and credibility assessment before the underlying claim can be used analytically. CIE encodes RUMINT as a first-class information type — with its own metadata header, its own credibility vocabulary, and its own rules for how source claims interact with the confirmed event record. The structure below is not a workaround. It is a designed capability.
- tur.min.dfns.exc.01 [ag] lbn.hog / {st.pr} ->> [ak] @ syr.sbs.rqq.hps - ∫ *.dt : 02.wk
Four events. Four action types. A bilateral meeting, a military statement, an emergency warning, a source claim — all encoded in the same grammar, against the same Registry, producing records that can be queried, compared, and aggregated without any further normalization.
This is the analytical gain CIE is designed to produce. Not through automation, not through AI summarization, but through the prior discipline of encoding: the commitment to record what happened, once, in a form that a machine can traverse and an analyst can audit. The encoding is the work. Everything downstream becomes easier.
Examples & Applications →