Ten solutions, one evidence architecture.
Read at a glance, this looks like ten products. Read at the architecture, it is one thing built ten times: every solution operates inside a declared boundary, records what it did, and emits signed evidence an assessor can verify without us. The products differ in what they govern. They do not differ in how they prove it.
Wagoner Enterprises, LLC. Founded May 2023. Bruce Wagoner, Chief Technology Officer. 202-794-3282. Washington, D.C. metro area.
What every product shares.
This is the part that matters to an acquirer, an assessor, and a program office for the same reason: it is the reason a second product costs less to authorize than the first.
A declared boundary
Every product states where its data lives and what, if anything, crosses out. Disconnected operation is the default mode, not a special edition.
An immutable audit record
Every access, inference, and data flow is written in one record shape, hash chained. A write failure fails the operation it describes.
Signed, verifiable evidence
One Evidence Pack format across the portfolio: manifest, content hashes, attestation chain, offline verification. Structure published openly.
One deployment shape
Containerized, Kubernetes-deployable, configuration as code. The same artifacts move across tiers by changing the environment profile.
Classified AI Operations
Running and validating models where the network ends.
AirGap LLMOps
Governs the model lifecycle across an air gap. Releases are built and signed on the connected side, verified on receipt inside the enclave, then promoted through policy gates and watched for drift and tamper.
OpenAegis
Governed AI assurance and adversarial validation: probes AI guardrails and agent permissions under non-destructive campaigns, emits detection content for purple teams, and packages results as signed, OSCAL-ready evidence a disconnected reviewer can verify.
OpenAuthorization & Evidence Automation
Producing the artifacts an assessor asks for, continuously, as a byproduct of the work.
DevSecOps Evidence Builder
Turns a repository or container artifact into SBOMs, normalized findings, least-diff remediation, POA&M drafts, and a signed Evidence Pack.
OpenVigil
Links controls to evidence, runs scheduled continuous monitoring with snapshots and trends, and generates schema-validated OSCAL SSP, SAR, and POA&M packages under an approval lifecycle.
OpenLLM Procurement Compliance Harness
Standardizes vendor transparency intake, memo-aligned evaluation, and risk review into one signed, portable Procurement Pack.
OpenData & Policy Automation
Turning written policy into enforced, auditable configuration.
ClassifyAI
Classifies documents using policy as code, routes every decision to human adjudication, and keeps a hash-chained record throughout. Inference runs inside the boundary; no data leaves it.
OpenPalisade
Turns flow, identity, asset, and Kubernetes telemetry into ranked Zero Trust changes, compiled for four enforcement targets with a blast-radius estimate, a rollback artifact, and signed, offline-verifiable evidence.
OpenMission Platforms
Whole platforms rather than single capabilities. Halo is bought by platform owners and security teams. PursuitIQ and Rostrum sit on either side of the same pursuit and are bought by a contractor or integrator rather than by a government program.
Halo Security Platform
Sits between an AI agent and what it is reaching for, decides whether to allow, sandbox, escalate, or deny, and records every decision in a tamper-evident ledger that produces OSCAL-ready evidence.
OpenPursuitIQ
Governed capture and proposal operations: opportunity discovery and win probability, solicitation parsing, compliance matrix, collaborative authoring with a governed AI copilot, readiness checks, and auditable export.
OpenRostrum
Rehearses a team against the evaluation panel they will face, joining the meeting they already use and scoring the session against the real evaluation criteria.
OpenThe four questions every reviewer asks.
Start with the product closest to your current problem.
The portfolio is designed to be entered at one point. Whichever product a program adopts first, the boundary model, audit record, and evidence format carry into the next one.