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.

CIE Expression
OSINT Parsed
ind.hog <[mt]>
	- rus.hos, rus.min.dfns.exc.01 @ ind.hps
		- <{sp}> $ eng.hyc, eng.nuc
	- rus.hos > @ *.loc  04122025:05122025
ind.hog
India / Head of Government — subject of the senior clause
<[mt]>
Bilateral action: meet. Angle brackets encode bilaterality — both parties are principal actors.
rus.hos, rus.min.dfns.exc.01
Russia / Head of State and Russia / Ministry of Defence / Executive Position 01 — bilateral counterparties attending
@ ind.hps
Location: India / Head of State official residence — where the meeting took place
<{sp}> $ eng.hyc, eng.nuc
Bilateral discussion of domains: Energy / Hydrocarbon and Energy / Nuclear — the defined subject matter of the meeting
04122025:05122025
Temporal span: 4–5 December 2025. The ∫ operator encodes a bounded duration rather than a single date.

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.

CIE Expression
OSINT Parsed
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.+
tha.min.dfns.ary.spx
Thailand / Ministry of Defence / Army / Spokesperson — the acting subject issuing the statement
[st.ds]
Action: Statement / Describe. Encodes the statement act itself — not the incidents described within it. The distinction is deliberate and analytically significant.
tha.ary {ak} khm.loc.3+
Thai Army engaged by three or more Cambodian local forces — the event the statement describes
@ ∫ ~ (13.9.no, 103.2.es)
Approximate coordinate location spanning an area: ~13.9°N, 103.2°E. The ∫ marks a locative span; ~ marks approximation.
# *.ary, *.arf
Force identifiers: Army and Air Force — participating units resolved anaphorically from previously established actors
[cl.uv] khm.ary [nu] tha.ary.unk.1+ [ij] *.8.+
Subsidiary clause: Cambodian Army neutralized one or more unknown Thai personnel; eight or more additional casualties injured

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.

CIE Expression
OSINT Parsed
jpn.min.infr.mteo.spx [st.wr]

	- $ natx.smsc ~ @ (40.8.no, 143.2.es)

	- {st.wr} natx.tsun @ jpn.sbs.amr, *.hkk, *.iwt
jpn.min.infr.mteo.spx
Japan / Ministry of Infrastructure / Meteorological Agency / Spokesperson
[st.wr]
Action: Statement / Warn. The formal warning issuance is the encodable event.
natx.smsc ~ @ (40.8.no, 143.2.es)
Natural event: seismic. Approximate location ~40.8°N, 143.2°E — the epicentre warned about in the first clause
{st.wr} natx.tsun
Anaphoric reference to the prior warning action; object: natural event / tsunami — the secondary warning derived from the seismic event
jpn.sbs.amr, *.hkk, *.iwt
Three affected prefectures: Aomori, Hokkaido, Iwate. Second and third resolved anaphorically — avoiding repetition of the country code.

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.

CIE Expression
RUMINT Parsed
Source:6512.2983
Rel / Cred:C4
Conf:Med
Func:Atm / Elite-Weak
- tur.min.dfns.exc.01 [ag] lbn.hog / {st.pr}
	->> [ak] @ syr.sbs.rqq.hps
		-  *.dt : 02.wk
Source: 6512.2983  /  Rel/Cred: C4
Registry source identifier with credibility rating — sourcing metadata that travels with the encoding and does not touch the event body
Func: Atm / Elite-Weak
Source functional classification: access through atmospheric channels to elite-level actors, assessed as weak reliability
tur.min.dfns.exc.01 [ag] lbn.hog
Turkey / Ministry of Defence / Executive Position 01 engaged Lebanon / Head of Government — the claimed bilateral contact
/ {st.pr}
Conditionality marker: what follows is contingent on the prior statement/proposal — explicitly encoding the conditional character of the claim
>> [ak] @ syr.sbs.rqq.hps
Proposed future action: armed engagement at Syria / Raqqa Governorate / specified location — claimed forward intent, not confirmed event
∫ *.dt : 02.wk
Temporal span: from event date, two weeks forward — the claimed window for the proposed action
What this makes possible

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