ANSWER
Required targets are supported by the available evidence.
HX-Fusion
Deterministic data fusion and mission-answer runtime. Reconcile supported evidence and structured questions into answers, explicit requests for missing information or abstention.
An explicit outcome for each question
ACQUIRE
Missing evidence requirements are identified. The outcome does not itself task a source.
ABSTAIN
No complete answer or supported acquisition path is available.
Operational refusals and failures remain separate from these decision outcomes.
From evidence to a reproducible decision
- Evidence
- State
- Intent
- Plan and execute
- Reassess
- Packet
- Recover
Evidence and time integrity
Retain event, validity and arrival time, source lineage, uncertainty, correlated support, contradictions and retractions. Windows, watermarks and duplicate handling make changing inputs traceable.
Qualified execution
Assess scope, freshness, uncertainty and policy. Select declared operator graphs and explicit representation transitions under error and resource bounds. Reassess whether the requested answer is supported.
Packets that preserve required disclosures
Produce minimal, standard or diagnostic HX-binary packets within exact encoded-byte budgets. Preserve uncertainty, freshness, provenance and contradictions; refuse when no valid packet fits.
Durable decision history
Journal-first commits, immutable histories, content-addressed artifacts and idempotent retries retain state, resolution and packet issuance separately. Checkpoint recovery reproduces canonical results and packet bytes.
Recorded qualification
- Runtime validation
- 4,252 assertions across 89 groups, a public two-subject lifecycle, one-/four-thread canonical parity, a release self-test and exact recovery.
- Execution environment
- In-process Julia on a single CPU node. Validated on Ubuntu Linux with Julia 1.12.6.
- Qualified algorithm
- Bounded scalar-interval consensus, IntervalConsensusV0.
- Evidence basis
- v1.0.0-rc1 source and bound validation records at bb9a7590; RWQE-001 qualification report and receipt.
Recorded qualification applies to this release and its stated contracts. Domain algorithms and target environments require scoped integration and qualification. It does not qualify arbitrary sensor exploitation, autonomous collection, transport/delivery, QTT, GPU or distributed execution.
Bat Cave public-data exercise
An unsupported conclusion remained unknown.
The Hurricane Helene exercise used 134 frozen government responses through an offline evidence adapter. HX-Fusion retained route traversability as UNKNOWN and returned ACQUIRE, identifying the need for additional evidence. Packet and recovery parity were preserved.
The recorded outcome was a bounded PASS for this public-data surrogate exercise. It establishes evidence handling within the exercise, not field deployment, autonomous collection or a determination that a route was safe.
Embedding HX-Fusion
Integration-specific adapters map sensor analytics, model outputs and reports into supported evidence contracts. The host application supplies interfaces, communications and display. The release includes public APIs, deployment instructions, a self-test and frozen qualification evidence.
Subject state is isolated. Conflicting work is serialized while eligible private preparation can overlap. Fixed workers, bounded queues and explicit backpressure control admission. Queue acceptance is distinct from a committed result; packet issuance is distinct from delivery.
Evaluate HX-Fusion for your team
- Who it serves
- Engineering teams embedding evidence reconciliation and decision support in an existing application.
- When to evaluate
- Evidence changes over time, sources disagree, or a receiving system needs an answer with explicit uncertainty and provenance.
- Outcome to establish
- Supported answers, identified evidence requirements or abstention, with retained decision history and reproducible packet bytes.
- Deployment
- Local runtime release candidate · Scoped integration
- Evidence to review
- Runtime validation and a bounded public-data exercise, with canonical result and packet recovery checks
- Commercial starting point
- Evaluate the published v1.0.0-rc1 local runtime through a scoped integration. Agree source adapters, evidence contracts, domain algorithms, endpoint budgets and acceptance criteria.
Integration requirements
Applications that need to reconcile changing evidence, assess whether a question is supported and retain a reproducible decision record.
Inputs
Supported evidence contracts, structured mission questions, domain adapters and endpoint disclosure requirements.
Outputs
ANSWER, ACQUIRE or ABSTAIN outcomes; bounded HX-binary packets; retained decision and recovery records.
Limits
The current qualification covers single-node CPU execution and bounded scalar-interval consensus. Domain algorithms and deployment environments require their own qualification.
Availability: Local runtime release candidate · Scoped integration.