DATA & ADAPTER
Approved sensor, C2, Digital Twin and AI outputs are normalized at the integration boundary.
PUBLIC CAPABILITY
CREAIM DEFENSE · CAPABILITY BOUNDARY
Show the capability.
Keep the implementation private.
The public site explains what CREAIM Defense does, where it sits, and what evidence can be reviewed. Detailed algorithms, scoring, thresholds, internal stage lineage, solver strategy, security contracts and partner delivery artifacts are not part of the public surface.
30-SECOND RUNTIME ASSURANCE
Keep the Digital Twin and AI. Add an independent validation layer before human release.
RUNTIME STATUS ≠ COMMAND AUTHORIZATION
01
DIGITAL TWIN / WORLD MODEL / AI
STATE · FUTURE · CANDIDATE
02
CREAIM RUNTIME COMPUTING
CONSTRAINT · REVALIDATE · ELIMINATE
03
PASS / HOLD / STOP
REVIEW STATUS · NOT COMMAND AUTHORITY
04
EVIDENCE
HASH · TRACE · REPLAY
05
HUMAN AUTHORITY
FINAL REVIEW / RELEASE
SOFTWARE
147 / 147 REGRESSION PASS
SOFTWARE VERIFIED
EXTERNAL COMPUTATION
QOBLIB #84 · #85 · 47 / 50
EXTERNAL COMPUTATIONAL EVIDENCE
EXTERNAL PARTNER
NOT_OBSERVED
PERSISTED LIVE EVIDENCE REQUIRED
AUTHORITY
HUMAN REQUIRED
NO AUTONOMOUS RELEASE
QOBLIB is external computational evidence, not proof of Digital Twin field performance, military operational suitability, or certification. External-partner and target-environment evidence remain separate until actually observed.
EVIDENCE TRUST LANGUAGE
The evidence scope is explicit even when a gate says PASS.
Software verification is never auto-promoted into external-partner or target-environment proof. NOT OBSERVED means qualifying evidence has not been recorded; it is not the same as FAIL.
SOFTWARE VERIFIED
REPRODUCED
EXTERNAL COMPUTATIONAL EVIDENCE
EXTERNAL PARTNER OBSERVED
TARGET ENVIRONMENT VERIFIED
CERTIFIED / ACCREDITED
PASS
HOLD
NOT_OBSERVED
PUBLIC CAPABILITY VIEW
EDGE & DISCONNECTED
Runtime review can continue within an approved local scope when connectivity is degraded or unavailable.
PUBLIC CAPABILITY
TRUST & SAFETY
Untrusted inputs are separated from the Runtime validation boundary and final authority remains human.
PUBLIC CAPABILITY
EVIDENCE & REPLAY
Results are returned with verifiable evidence and replay information for review.
PUBLIC CAPABILITY
CONTROLLED PoC
Partner integration, target hardware, closed-network behavior and acceptance are measured jointly in a controlled PoC.
PUBLIC CAPABILITY
WHAT IS PUBLIC
Runtime Computing position and purpose
Runtime State / Space concept
Selective revalidation concept
PASS / HOLD / STOP review states
Synthetic proof and verifiable evidence
Human authority and claim boundary
PARTNER / NDA
Approved interface and schema mapping
Deployment and security profile
Test vectors and acceptance criteria
Target measurements and conformance evidence
Partner approval does not grant access to Runtime Core source or internal decision logic.
FROZEN PARTNER REFERENCE · NOT ACCEPTED PRODUCTION
The earlier Partner RC1 remains preserved as a frozen reference in the versioned runtime package and is not silently mutated by the public-site improvements. The frozen release candidate is not proof of partner sign-off, live military integration or target-environment validation.
CREAIM INTERNAL · NOT DISCLOSED
SCORING / THRESHOLDS
STATE REDUCTION / PRUNING
BRANCH / CANDIDATE STRATEGY
SOLVER PORTFOLIO
METACORE ORCHESTRATION
MEMORY / INDEX INTERNALS
EXTERNAL BENCHMARK SOLVER IMPLEMENTATION
PRIVATE SOURCE AUDIT
CLAIM BOUNDARY
FIELD VALIDATED = NO · EXTERNAL PARTNER ACCEPTANCE = NOT OBSERVED
The public demo accepts synthetic, non-sensitive Mission and Digital Twin input only. Release management requires that the earlier Partner RC1 remains preserved as a frozen reference and is not silently mutated; compliance with that policy requires independent artifact/version verification and is not asserted by this page.
Public samples use synthetic, non-sensitive Mission and Digital Twin input. Live military C2/sensor integration, target-edge performance, partner acceptance, accreditation and operational suitability require external Controlled-PoC evidence.