Framework overview
AIH-12 · Usabilityv0.1 · Draft for public comment

The Horizon Card: one system, one page, honestly described.

A Horizon Card records where a single deployed system sits on the AIH-12 horizons — and, more importantly, the gap between the authority it was given on paper and the authority it actually has. Fill it in for a system you run, review or procure. It is an indicative self-assessment, not certification.

Template

Fields and guidance

Identity
SystemName and version of the system or agent being described.
Developer · OperatorWho built it, and who runs it in this deployment. They are often different.
Accountable personThe named human or role answerable for this deployment.
Deployment contextWhere it runs, for whom, and on whose behalf it acts.
Authority
Declared authorityWhat it is permitted to access, spend or change, as written down.
Effective authorityWhat it can actually reach in practice. Any gap from the declared authority is the first finding.
Delegation stepObserve · Recommend · Draft · Act with approval · Act within limits · Coordinate within a domain · Expanded authority after reassessment.
The seven dimensions
CapabilityWhat it can demonstrably do. Cite the evidence class.
AutonomyHow far it proceeds without a person in the loop.
AuthoritySummary of the authority findings above.
ConnectivityOther systems and agents it can reach or rely on.
Action scaleHow many actions, people or assets it can affect at once.
External impactWhat happens outside the system when it acts.
Reversibility & revocabilityCan effects be undone, and authority withdrawn — and how fast?
Placement
Indicative horizonH1–H12, with a one-line rationale. Indicative self-assessment — not certification.
EvidenceFor each claim: Assertion · Demonstration · Documented case · Reproducible test · Controlled pilot · Independent review (proposed classes).
Open questionsWhat you could not establish. An honest blank is better than a confident guess.
Reassessment dateAnd the triggers: model change, new tool, new data, expanded authority, new environment, incident, failed control, changed use.
Use it

Copy the blank card

Offered under CC BY 4.0. Keep the “indicative — not certification” line if you republish it.

# AIH-12 Horizon Card (v0.1 · Draft for public comment)

> Indicative self-assessment — not certification. Template by the Open Conformance Coalition (OCC), openconformance.org/occ/horizon-card. CC BY 4.0.

## Identity

| Field | Entry | Guidance |
| --- | --- | --- |
| System |  | Name and version of the system or agent being described. |
| Developer · Operator |  | Who built it, and who runs it in this deployment. They are often different. |
| Accountable person |  | The named human or role answerable for this deployment. |
| Deployment context |  | Where it runs, for whom, and on whose behalf it acts. |

## Authority

| Field | Entry | Guidance |
| --- | --- | --- |
| Declared authority |  | What it is permitted to access, spend or change, as written down. |
| Effective authority |  | What it can actually reach in practice. Any gap from the declared authority is the first finding. |
| Delegation step |  | Observe · Recommend · Draft · Act with approval · Act within limits · Coordinate within a domain · Expanded authority after reassessment. |

## The seven dimensions

| Field | Entry | Guidance |
| --- | --- | --- |
| Capability |  | What it can demonstrably do. Cite the evidence class. |
| Autonomy |  | How far it proceeds without a person in the loop. |
| Authority |  | Summary of the authority findings above. |
| Connectivity |  | Other systems and agents it can reach or rely on. |
| Action scale |  | How many actions, people or assets it can affect at once. |
| External impact |  | What happens outside the system when it acts. |
| Reversibility & revocability |  | Can effects be undone, and authority withdrawn — and how fast? |

## Placement

| Field | Entry | Guidance |
| --- | --- | --- |
| Indicative horizon |  | H1–H12, with a one-line rationale. Indicative self-assessment — not certification. |
| Evidence |  | For each claim: Assertion · Demonstration · Documented case · Reproducible test · Controlled pilot · Independent review (proposed classes). |
| Open questions |  | What you could not establish. An honest blank is better than a confident guess. |
| Reassessment date |  | And the triggers: model change, new tool, new data, expanded authority, new environment, incident, failed control, changed use. |

Completed by: ____  ·  Date: ____  ·  Evidence register attached: yes / no
Why declared vs effective authority comes first
Most agent failures on the public record are not capability surprises; they are authority surprises — a system that could reach more than anyone wrote down. See how this reads on a real case in the Assurance Observatory.