← TM Forum Hub HAIEC · DETERMINISTIC ASSURANCE
01 / 15
TM Forum 2026 · Submitted · Agentic Assurance

From agent activity
to defensible proof.

HAIEC turns agent behavior into deterministic, queryable proof. Not telemetry. Not a dashboard. Not a checklist.

Submission: 2026-10-06T15:06:21Z · package sha256 1fde8544…

3 controls

C7 · C9 · C16

Same policy

PASS ↔ BREACH

Evidence-bound

Named runs + result IDs

Human governance

Alert → ACK → ServiceNow

Why this wins

Three proof archetypes.
One deterministic evaluator.

C16 — Boundary

Same frozen 60k policy. 35,559 → SATISFIED. 106,829 → NOT_SATISFIED.

C9 — Drift → Governance

+60.20% → SATISFIED. +286.03% → NOT_SATISFIED → INC0010337.

C7 — Failure → Remediation

9/10 missing negotiation → NOT_SATISFIED. Remediation → 10/10 SATISFIED.

Delivered

Assessment → findings → bounded fixes → retest/proof. Deterministic control tests, frozen thresholds, evidence lineage, alert→ACK→ServiceNow.

Refused to claim

Inline continuous compliance, exact canonical C7 retest, C9 cross-system projection.

A/B scoreboard — fresh runs 2026-10-06

Same scenario. One variable.
Our agent won all three.

ScenarioThird hopRunC7C16 (cap 60,000)GradeNeg. recs
S1haiec-network-agent…8a097d10/1029,3347/83
S1reference chain…e429bb9/1033,7226/80
S2haiec-network-agent…e290e910/1038,0677/103
S2reference chain…0d11d69/1034,0715/100
S3haiec-network-agent…db781210/1034,2799/103
S3reference chain…f828d49/1022,7978/100

Post-submission verification on the live environment, scored with the organizer's own score-run.py. Every haiec-network-agent run: C7 10/10 + 3 negotiation records; every reference-chain run: 9/10 + zero. "Guardrail verdict" check fails for all chains — an audit record-format gap, not a governance absence.

Proof chain

Not telemetry.
Deterministic judgment.

ACTION→NATIVE RECORD→RECONSTRUCTION→MEASUREMENT→FROZEN RULE→DETERMINISTIC VERDICT→RESPONSE / REMEDIATION

Every stage is bound to a named run, a frozen policy, and a persisted result ID.

C16 · ACN-COST-001

Deterministic boundary proof

RunMeasuredLimitVerdictResult ID
fault-1791167110-5e312635,559 tokens60,000SATISFIEDctr-237f…2154
fault-1791165466-51ab52106,829 tokens60,000NOT_SATISFIEDctr-6d14…bc01

Same frozen policy 547f4a67-76eb-4bf3-befb-c1212ae23f81. Different observed facts. Different result. ServiceNow INC0010319.

C9 · AIA-ARC-006

Drift → failure → governance

RunWorst agentDegradationVerdictResult ID
fault-1791276114-723d80haiec-network-agent+60.20%SATISFIEDctr-d338…ae82
fault-1791275895-048d48it-resolution-agent+286.03%NOT_SATISFIEDctr-0ba4…bb7e

Deterministic failure → alert → named human ACK → persisted response → anti-replay → ServiceNow INC0010337. Post-run / retrospective evaluation; inline continuous compliance is a P1 roadmap item.

C7 · AIA-LOG-001

Failure → exact gap → remediation → proof

RunSystemPolicyCoverageVerdict
fault-1791167110-5e31264043efee…ae6d…9/10NOT_SATISFIED
fault-1791275895-048d4844f861cf…dcfa…10/10SATISFIED

Missing IT↔Network NEGOTIATION was the exact gap. Real behavioral remediation produced the 10/10 proof. ae6 and dcfa are distinct immutable policy instances with equivalent C7 semantics — not an exact canonical retest.

Evidence lineage

Permission is not execution.
Execution is not authorization.

Declared / authorized

  • frozen control threshold
  • approved ODA change / effective policy
  • Cedar / Guardrail / configuration
  • approved model/tool or human workflow

Observed

  • OTel trace
  • gateway/model call
  • tool/API invocation
  • ServiceNow session/alert
  • human acknowledgement or silence

HAIEC reconciles these planes without pretending one proves the other.

Architecture — judge Q&A

Architecture, answered.

Who computes the verdict?

A deterministic evaluator over a frozen policy and persisted measured facts. No LLM decides — MCP/AI returns persisted results by reference only.

Where does truth live?

Persisted evidence bound to named runs, frozen policies, digests and result IDs. The report is a projection — the store is the source.

VERIFY vs REPLAY vs NEW RUN?

VERIFY re-derives the same verdict from frozen policy + persisted facts (read-only). REPLAY reconstructs history. A new run is fresh execution — never sold as historical proof.

What if LogSense is offline?

Nothing changes. Reconstruction feeds evaluation; it never substitutes for it. Verdicts, VERIFY and MCP all answer from persisted evidence.

Tenant boundary?

The judge key is org-scoped and read-only — no writes, no ingest, no cross-tenant reach. Credentials live only in the private handoff.

What stops false closure?

UNKNOWN / NOT_ESTABLISHED are first-class persisted states — never upgraded to PASS. The original 9/10 failure is preserved, not rewritten.

Five independent evidence planes — REQUESTED · POLICY_AUTHORIZED · EFFECTIVELY_GRANTED · CODE_CAPABLE · OBSERVED — reconciled without pretending one proves another.

Findings beyond the three controls

Findings are not verdicts.
HAIEC preserves the difference.

SEC-01

Shared/plaintext runtime credential exposure. No compromise/abuse claim.

SEC-02

Token-ceiling enforcement gap/lag. No universal limiter-bypass claim.

SEC-03

Phantom tool-call/model-turn runaway. ~84/86 turns; one real downstream tool invocation.

EXP-04

Public-listener scanner exposure. Probes observed, 404, no compromise claim.

HIS-05

Historical/resolved configuration drift. Current driftDetected=false.

S2-FALSE-CERTAINTY-001

False closure refused. 5/10 → remediation → 5/10 → NOT_FIXED.

What HAIEC refused to claim

Honest limits.
No false closure.

Inline continuous compliance

Delivered post-run / retrospective evaluation. Inline continuous compliance is a P1 roadmap item.

Exact canonical C7 retest

Remediation pass is genuine and system-scoped — ae6 and dcfa are distinct immutable policy instances.

C9 cross-system projection

13c/44f results are kept separate from canonical 346b/4043.

ServiceNow AICT materialization

Connector and human-loop proof are established; asset record materialization is NOT_ESTABLISHED.

Mailbox email delivery

Provider-accepted is established; mailbox delivery is NOT_ESTABLISHED without provider receipts.

False closure

S2-FALSE-CERTAINTY-001: 5/10 → remediation → 5/10 → NOT_FIXED.

What we delivered

Assessment → findings → fixes → retest.

1. Assessed

Named runs evaluated under frozen policies with deterministic control tests.

2. Found gaps

C7 missing negotiation, C9 drift breach, SEC/EXP/HIS findings.

3. Bounded fixes

Real network-agent remediation; no policy rewrites; no false closure.

4. Retest / proof

C7 10/10 SATISFIED; C9 breach → governance; C16 PASS/BREACH preserved.

Verify it yourself

Ask the evidence.
Not the team.

Read-only MCP interface — point any MCP client at it and query persisted event data directly.

Connect

POST www.haiec.com/api/mcp
Bearer judge key · org-scoped · read-only · expires after judging

Tools

investigate_time_window · control_test_query · list_systems · list_investigations · reconstruct_scenario · compare_scenario_states

Honest by contract

Returns persisted results by reference — never computes verdicts. Empty = NO_OBSERVATIONS_MATCHED, not a green check.

Every answer carries provenance (source snapshot sha256, LogSense commit, case id) plus explicit limitations. Setup guide + judge prompt pack: subodhkc.com/tm-forum#mcp

What now

Post-submission roadmap.

P0 — Productize event proof

Persist reconstruction, before/after comparison, control→run→evidence navigation.

P1 — Runtime assurance

Inline continuous compliance, second enforcement point, native decision receipts.

P2 — Evidence hardening

Producer identity, run-start provenance, clock qualification, approval-current proof.

P3 — Enterprise experience

Executive proof view, auditor workspace, portable bundle, multi-agent graph.

HAIEC · Human AI Evidence Company

AI can move faster than human review.
Proof cannot become optional.

Declare→Observe→Bind→Evaluate→Prove

High assurance in every consequence.