CI claim boundary console

Claim Firewall

Unsupported security claims should fail before they reach the public page. Public wording stays below the evidence ceiling until evidence linkage and explicit promotion clear a stronger claim.

RENDERING_ONLYCONTROLLED_TEST_VALIDATEDNOT_PUBLIC_SAFE

PUBLIC WORDING ROUTEBLOCKED

01WORDING

Copy, metadata, proof cards, reviewer summaries.

02SCANNER

Blocked terms, unsafe context, proof drift.

fail closed

03CEILING

Evidence-linked claims only.

sourcevalidationruntime candidateevidence reviewhuman approvalpublic proof blocked

Website rendering is not proof.Public proof requires evidence linkage and explicit promotion.

Evidence ceiling gauge

Claim levels stay separated

PUBLIC-SAFE BLOCKED UNLESS PROMOTED

01Source truthreviewable
Source-controlled wording can be inspected, but source presence does not prove runtime.
02Validation truthcontrolled
Deterministic validation can support controlled-test wording at the current ceiling.
03Runtime candidatecandidate only
Runtime candidates remain below public proof until separately evidenced and promoted.
04Signal / evidence reviewgated
Signal and evidence claims require separate review before public wording can move.
05Human approvalauthority
Human review authorizes promotion; AI and green checks do not.
06Public proofblocked until promoted
Public-safe status remains blocked unless explicit evidence linkage and promotion clear.

Blocked / not claimed

CONTROLLED RISK CHIPS

runtime-activesignal-observedpublic-safe runtime proofproduction-readyproduction/customer/SOCaaS deploymentSOCaaS-readyFortiSIEM integration provenfleet-widelive Splunk firedSplunk-proven Runtime Signal 001Cribl-routedWazuh-routedAWS-liveautonomous SOCAI-approved dispositionanalyst-approved dispositionpublic-safe

Allowed wording examples

HO-DET-001 is presented at CONTROLLED_TEST_VALIDATED.
Website pages route reviewers to proof records; they do not replace proof records.
Controlled-test validation supports the validation surface only.
Runtime, signal, evidence, and public proof require separate promotion gates.

Unsafe wording examples

HO-DET-001 is deployed across live systems.
The website proves public signal observation.
Source presence proves operational coverage.
AI has approved the final disposition.

Promotion requirements

EVIDENCE LINKAGE REQUIRED

01Current source artifact remains reviewable in the owning repository.
02Validation output is deterministic and linked to the proof record.
03Runtime state is independently evidenced before runtime claims move forward.
04Signal state is independently evidenced before signal claims move forward.
05Evidence linkage is explicit before public proof status changes.
06Public wording is scanned against the blocked-claim list before release.

Promotion gate timeline

Evidence moves before wording moves

FAIL CLOSED

01Source truth
02Validation truth
03Runtime candidate
04Signal / evidence review
05Human approval
06Public proof

Outcome panel

What the firewall prevents

AI LABOR / HUMAN AUTHORITY

validationruntime proofblocked
website renderingproofblocked
green CIapprovalblocked
AI supportdisposition authorityblocked
runtime candidatepublic-safe proofblocked

AI-assisted security work can move fast, but public wording stays governed: the scanner constrains unsupported language, then human review decides whether evidence is sufficient for any explicit promotion.

Allowed claim basis

BELOW CEILING

HawkinsOperations is a public rendering layer.
HawkinsOperations separates source truth, runtime truth, signal truth, evidence truth, and public proof.
HO-DET-001 is CONTROLLED_TEST_VALIDATED.
HO-DET-001 has controlled-test validation status.
HO-DET-001 may be rendered as a SOCaaS Pilot Receipt when the receipt keeps source, validation, case packet, AI support, human review, and proof authority separate.
Source presence does not prove runtime.
Validation does not prove public signal.
Public proof requires evidence linkage and explicit promotion.