The Geneva Charter | Integrity Layer Compliance Checklist

Charter Framework Components

Integrity Layer Compliance Checklist

This checklist translates the Integrity Layer Specification for Synthetic Crisis Systems into a usable review instrument. It is designed for institutions that need a disciplined, repeatable way to assess whether a synthetic briefing, dashboard, narrative engine, or crisis synthesis product is procedurally reliable enough to inform interpretation or action. The checklist does not measure rhetorical polish. It measures structural integrity.

Go to checklist Decision guide

Purpose

A practical review tool for high consequence synthetic output

The checklist is intended to be used before a synthetic system output informs official interpretation, media framing, crisis coordination, diplomatic positioning, or operational choice. It can be completed during review meetings, attached to briefing packs, or used as a standing control instrument by analytical teams. Its purpose is simple: make failure visible before synthetic coherence becomes institutional momentum.

Review profile

Review object Synthetic crisis briefing, dashboard, summary, or narrative product

Review outcome Compliant, partially compliant, or non compliant

Review focus Evidence, separation, legal discipline, traceability, and decision readiness

Operational effect Determines whether the output may inform action, caution, or further review only

0 to 5

Fail

Non compliant. Do not use for decision support.

6 to 11

Weak

Major structural deficiencies remain visible.

12 to 17

Partial

Usable only with explicit caution and review.

18 to 22

Strong

Procedurally reliable, subject to human judgment.

Checklist rule

A synthetic output is not trustworthy because it sounds coherent. It becomes procedurally usable only when its evidentiary status, interpretive boundaries, legal condition, and decision readiness are visible enough to be challenged.

Compliance checklist format

Score each item using one of three ratings. Mark compliant where the condition is clearly satisfied, partial where the condition is present but incomplete, and non compliant where the condition is absent, hidden, or contradicted by the output design. A reviewer may also add notes where the nature of the failure matters operationally.

Compliant = 1 point

Partial = 0.5 point

Non compliant = 0 points

Section 1

Evidence status and claim classification

#	Review item	Score	Reviewer note
1.1	Does every material claim carry a visible status label such as verified, partially verified, disputed, inferred, or speculative?	Compliant Partial Non compliant	Note where unlabeled claims remain.
1.2	Are factual claims clearly separated from inferred or speculative claims?	Compliant Partial Non compliant	Identify any blended sentences or sections.
1.3	Does the output avoid presenting inferred claims as established facts?	Compliant Partial Non compliant	Record any language that overstates certainty.
1.4	Is uncertainty visible rather than buried in footnotes, drill downs, or secondary views?	Compliant Partial Non compliant	State whether uncertainty is operationally legible.

Section 2

Separation of analytical layers

#	Review item	Score	Reviewer note
2.1	Are evidence status, assessment, interpretation, and decision readiness presented as distinct layers?	Compliant Partial Non compliant	Describe where layers remain fused.
2.2	Can the user easily identify where assessment ends and interpretation begins?	Compliant Partial Non compliant	Flag any ambiguous transitions.
2.3	Does the output avoid implying action before showing decision readiness status?	Compliant Partial Non compliant	Record any implicit calls to action.
2.4	Is summary language structurally consistent with the underlying layers, rather than compressing them into one narrative block?	Compliant Partial Non compliant	Note any narrative compression risks.

Section 3

Legal discipline and interpretive control

#	Review item	Score	Reviewer note
3.1	Does the output identify whether legal basis is present, contested, absent, or not yet assessable?	Compliant Partial Non compliant	State whether legal status is explicit.
3.2	Are competing interpretations visible where the evidentiary record supports more than one reading?	Compliant Partial Non compliant	Record missing alternatives.
3.3	Does the system avoid inevitability language when the evidence supports only possibility or probability?	Compliant Partial Non compliant	Quote any problematic wording.
3.4	Is decision readiness described as a classification rather than implied through urgency, confidence, or tone?	Compliant Partial Non compliant	Explain any mismatch between tone and readiness.

Section 4

Traceability and temporal integrity

#	Review item	Score	Reviewer note
4.1	Can each material claim be traced to a source basis, verification status, and last review timestamp?	Compliant Partial Non compliant	List any untraceable claims.
4.2	Does the output state whether the record is stable, evolving, or volatile?	Compliant Partial Non compliant	Note whether temporal condition is visible.
4.3	Does the system increase caution when urgency rises faster than certainty?	Compliant Partial Non compliant	Record whether caution scales with uncertainty.
4.4	Does the system avoid stronger narrative confidence when the underlying evidentiary condition is deteriorating?	Compliant Partial Non compliant	Identify any escalation distortion.

Section 5

Human review and override

#	Review item	Score	Reviewer note
5.1	Has accountable human review confirmed understanding of evidentiary status and legal condition?	Compliant Partial Non compliant	State who reviewed and when.
5.2	Can human reviewers halt synthetic escalation or require further verification before the output is used?	Compliant Partial Non compliant	Describe override authority if present.
5.3	Does the final output carry a visible integrity status such as compliant, partially compliant, or non compliant?	Compliant Partial Non compliant	Note where certification is absent or unclear.
5.4	Is the output fit for the intended use environment without concealing material structural weaknesses?	Compliant Partial Non compliant	State intended use and remaining limitations.

Scoring summary

Reviewer totals

Area	Possible score	Recorded score	Comment
Evidence status and claim classification	4	_____	Core reliability of claim presentation
Separation of analytical layers	4	_____	Visibility of procedural sequence
Legal discipline and interpretive control	4	_____	Constraint on narrative overreach
Traceability and temporal integrity	4	_____	Auditability and maturity of record
Human review and override	4	_____	Institutional control condition
Total	20	_____	Use the decision guide below

Decision guide

The final score should not replace judgment, but it should discipline it. Low scores indicate structural weakness at the point where synthetic outputs become most dangerous, namely when they appear coherent enough to drive interpretation despite poor evidentiary or procedural foundations.

18 to 20

Compliant

May inform interpretation and structured review
Still requires accountable human judgment
Suitable for cautious operational use where lawful basis is separately assessed

12 to 17.5

Partially compliant

May inform internal review only with explicit caution
Requires remedial clarification before high consequence use
Must not be treated as decisive or action guiding on its own

0 to 11.5

Non compliant

Must not be used for decision support
Requires reconstruction of claim status, separation, and traceability
Should be treated as structurally unsafe regardless of rhetorical quality

Operational meaning

A low score is not a technical inconvenience. It is a warning that the institution may be at risk of acting on compressed narrative coherence rather than verified, lawfully qualified understanding.

Suggested use procedure

The checklist works best when applied as part of a repeatable institutional review sequence. It should be attached to the output under review, completed by an accountable reviewer, and retained as part of the audit trail for any briefing that informs consequential interpretation or action.

Step 1

Attach the checklist to the output

Treat review as part of the product, not as an optional add on performed after momentum has formed.

Step 2

Score before operational discussion

The score should precede action discussion so that structural weakness is visible before conclusions harden.

Step 3

Record final integrity status

Every reviewed output should carry a visible status of compliant, partially compliant, or non compliant.

Continue through the framework

This checklist is designed to sit beside the specification page and the broader synthetic systems analysis pages inside The Geneva Charter.