CAPTURE
Operational context, inputs, authority, expectations, constraints, and relevant omissions.
CONSTITUTIONAL ENGINEERING KERNEL
WORKING LOCAL ASSURANCE CORE
CONSEQUENTIAL SYSTEMS NEED
A GOVERNING CORE
THAT CAN BE INDEPENDENTLY VERIFIED.
Hackett Meta OS (HMOS) is the reference constitutional runtime. Phase Anchored Consensus Protocol (PACP) is the portable evidence grammar for consequential authority, effects, evidence, lineage, and uncertainty. The current reference deployment runs the PACP API and Assurance Gateway together and enforces a bounded, lineage-scoped public-write boundary. Decision Evidence Infrastructure enables consequential decisions to leave evidence that can be independently replayed, challenged, and verified.
KERNELACTIVE IMPLEMENTATION
LOCAL ASSURANCE CORERUNNING
MISSION PROFILESDEFENSE + AEROSPACE + HEALTHCARE + INFRASTRUCTURE
CRITICAL SYSTEMS GENERATE
LOGS AND EVENT HISTORY.
CONSEQUENTIAL DECISIONS REQUIRE
VERIFIABLE DECISION EVIDENCE.
WHY THIS LAYER IS NEEDED
THE MISSING CAPABILITY
LOGS SHOW THAT SOMETHING HAPPENED. HMOS PRESERVES WHY.
DECISION EVIDENCE EXPLAINS
- Why a decision occurred
- Under what authority
- What information was available
- Which policies and constraints applied
IT ALSO PRESERVES
- What changed afterward
- What remained unknown
- What was expected but missing
- Whether the context can be replayed
THE HMOS KERNEL
KERNEL → PROFILES → APPLICATIONS.
The kernel governs how consequential claims are created, evidenced, verified, challenged, promoted, amended, and preserved.
Mission profiles adapt that invariant constitutional core to specific domains without redefining it. Applications consume those profiles while leaving the governing kernel unchanged.
EVALUATE
Apply declared policy, governance, validation rules, and bounded claim controls.
SEAL
Canonicalize, sign, hash-chain, and package evidence without rewriting history.
REPLAY
Reconstruct what was known, unknown, expected, missing, and amended over time.
THE EVIDENCE MODEL
THE RECORD PRESERVES MORE THAN THE ACTION.
HMOS keeps actions, omissions, authority, amendments, repair evidence, and verification results together as portable decision evidence.
OBSERVED
The action, context, authority, policy state, and outcome remain linked.
NOT OBSERVED
Expected-but-missing events remain visible rather than disappearing from the record.
AMENDED
Corrections attach transparently while the original history remains intact.
REPLAY
Portable evidence supports challenge, reconstruction, and independent review.
HMOS × GOD'S EYE VIEW · CAPABILITY PREVIEW
SEE HMOS CONSTRAIN UNSUPPORTED CONFIDENCE.
GEV can show a layer. HMOS decides whether that layer may still be claimed.
SYNTHETIC REPLAY · NOT LIVE POSITION TRUTH · NO ACTION AUTHORITY
Replay the bounded case
A read-only boundary preserves upstream ownership and semantics.
A failed refresh cannot silently remain a current-state claim.
Follow observation → policy → bounded claim through a synthetic case.
Capability preview only. Not live GEV integration, certification, production readiness, real-world vessel truth, or Neptune integration.
WHY EXISTING APPROACHES FALL SHORT
OBSERVATION IS NOT ACCOUNTABILITY.
HMOS complements existing systems by preserving the evidence they typically do not retain.
HMOS adds replayable decision evidence.
HMOS adds cryptographic provenance and integrity.
HMOS adds reconstruction of the full decision context.
HMOS adds durable, portable accountability.
THE DIFFERENCE IS NOT MORE DATA.
IT IS EVIDENCE THAT SURVIVES SCRUTINY.
Do not ask only what the system says now. Reconstruct what it knew at the moment the consequential decision was made.
DIFFERENT MISSIONS. SAME BURDEN OF PROOF.
THE ARCHITECTURE REPEATS.
THE CORE DOES NOT CHANGE.
The same architecture has been mapped to distinct mission profiles across NASA, Army, Air Force, and Navy solicitations. The foundation also extends to aerospace, healthcare, critical infrastructure, logistics, industrial operations, and research workflows.
DEFENSE
Autonomy, Zero Trust, command systems, disconnected operations, authority state, and mission replay.
AEROSPACE
Flight and space systems, remote operations, configuration state, telemetry context, anomaly response, and mission replay.
HEALTHCARE
Clinical decisions, imaging workflows, device interventions, model-assisted recommendations, handoffs, and evidence continuity.
CRITICAL INFRASTRUCTURE
Control actions, alarms, outages, maintenance, synchronization, intervention, and recovery sequencing.
LOGISTICS
Custody, release, routing, exceptions, inspection, synchronization, and corrective action.
RESEARCH WORKFLOWS
Reproducible provenance for complex computational, experimental, and model-assisted decisions.
ENGINEERING PRINCIPLES
ACCOUNTABILITY IS ARCHITECTURAL.
HMOS is built around a small set of principles that remain stable as implementations, algorithms, and mission contexts evolve.
Claims rest on replayable artifacts rather than narrative alone.
Corrections add transparent layers without erasing origin.
Every consequential action names its governing basis.
Absence of evidence is never presented as evidence of absence.
Independent verification does not depend on institutional memory.
WHEN SYSTEMS SHAPE REALITY, THEY MUST LEAVE ENOUGH EVIDENCE TO BE CHALLENGED.
HMOS was founded on that requirement from the beginning.
CURRENT OPERATIONAL STATE
WORKING SOFTWARE. BOUNDED CLAIMS.
The local reference deployment is operational today. Its current boundary is explicit so implementation evidence is never confused with certification or full production maturity.
PACP API + GATEWAY
One Docker workflow starts both services with authenticated health checks on loopback interfaces.
IMPLEMENTEDFIVE FAIL-CLOSED GATES
Storage integrity, anchor match, witness, authority binding, and declared information-flow policy must pass before the supplied write callback can execute.
IMPLEMENTEDLINEAGE RETAINS EXPOSURE
For the declared Objective 1 public-write path, delegation cannot discard inherited confidential exposure.
BOUNDED IMPLEMENTATIONNOT YET FULL PRODUCTION
Not independently audited, certified, highly available, or cloud-operated. Local runtime state is temporary unless an operator configures durable storage.
LIMITS DECLAREDBUILT FROM FIRST PRINCIPLES
THE FOUNDING QUESTION
IF SOFTWARE SHAPES CONSEQUENTIAL OUTCOMES, WHY CAN'T ITS DECISIONS BE INDEPENDENTLY RECONSTRUCTED?
CURRENT PROGRESS
- Working local PACP API and Assurance Gateway deployment
- Bounded constitutional enforcement for the Objective 1 public-write path
- Reusable kernel → profile → application architecture
- Adversarial security and governance validation maintained in CI
- Federation and cross-domain composition implemented within declared boundaries
- Patent-pending architecture; filed applications do not establish validity or scope
FEDERAL ADAPTATION
The same core architecture has been adapted and proposed across NASA, U.S. Army, U.S. Air Force, and U.S. Navy mission areas during its first funding cycle.
Claims remain bounded, measurable, and transparent about present maturity.
FEDERAL R&D PORTFOLIO
SEVEN PHASE I PROPOSAL LANES.
Company records identify the following proposal or proposal-package lanes as prepared or submitted. This portfolio record does not claim that every package was submitted, selected, awarded, funded, adopted, or endorsed.
- NASAAERO.7.S26B-0067AI/ML assurance and mission-safety evidence
- DAFF26BZ-NV006-0460PACP-ITA² · intelligent threat-aware autonomy
- DAFF26BZ-NV008-0034PACP-RTAA · runtime evidence for assured autonomy
- ARMYA26BX-NV001-0397PACP-ITV · logistics chain-of-custody evidence
- DLAL26BZ-NV006-0139PACP-RMF · evidence for AI-assisted RMF review
- NSFPHASE IPACP/HMOS proposal package
- NAVYPHASE IPACP-ZTE technical and cost proposal package
CONSTITUTIONAL ENGINEERING KERNEL
CAPTURE → EVALUATE → SEAL → REPLAY → CHALLENGE → VERIFY
This evidence lifecycle operates inside the larger HMOS constitutional architecture. The kernel is designed to preserve bounded claims, explicit authority, cryptographic provenance, omission evidence, transparent amendment, challenge, and independent verification across domains. HMOS does not independently confer certification, compliance, authorization, safety, factual truth, or operational approval.
ONE ARCHITECTURE. MULTIPLE MISSION CONTEXTS.
ACCOUNTABILITY MUST SURVIVE THE ENVIRONMENT.
Across defense, autonomy, Zero Trust, critical infrastructure, aerospace, and logistics, HMOS preserves evidence where consequential systems cannot depend on memory alone.
WHY THIS EXISTS
THE SYSTEMS BECAME FASTER.
THE CONSEQUENCES BECAME LARGER.
THE EVIDENCE BECAME SMALLER.
Hackett Meta OS did not begin as a software project.
It began with a simple observation.
As digital systems became more capable, they became increasingly able to shape real-world outcomes while leaving behind incomplete evidence of how those outcomes occurred.
Across healthcare, critical infrastructure, aerospace, finance, and defense, one question continued to surface:
When a consequential digital decision changes reality, who can later reconstruct exactly what happened?
Not approximately. Not from memory. Not from logs assembled after the fact. Exactly.
Hackett Meta OS was created to answer that question.
The architecture was developed by Andrew Hackett after years working across clinical imaging, interventional cardiology, medical technology, and other high-consequence operational environments where incomplete records and unexplained decisions carried real operational consequences.
The objective was never to replace existing systems. It was to ensure those systems could leave behind durable, replayable evidence of their decisions.
That work now extends into defense, autonomous systems, and Zero Trust architectures, where the same evidentiary discipline determines whether consequential decisions can be reconstructed after the fact.
Reality is primary.
Evidence outranks narrative.
History may be amended, never rewritten.
Repair becomes part of the record.
Authority leaves evidence.
Trust never depends on memory.
PUBLIC VERIFY
Start with the guided Decision Evidence Lab, then switch to the bounded verifier to inspect your own proof bundle.
HACKETT META OS
When systems shape reality, the record must be able to survive the systems.