Boundary Defense Agent (BDA-BOUNDARY-DEFENSE-002) — Public release v2

Abstract

A specification document package, distributed free of charge. It defines BDA-BOUNDARY-DEFENSE-002, a fail-closed boundary-control agent that validates, filters, quarantines, blocks, and conditionally releases artifacts crossing controlled runtime, persistence, or transport boundaries. The authoritative document is Boundary_Defense_Agent_Specification.md. The package also carries its Semantic Index, Coverage Matrix, Ambiguity Register and Conformance Tests, the verification runbook verify.md, the Whitepaper, and an observational, non-normative NNT companion. License. The package is governed by the Boundary Defense Agent License, included as Boundary_Defense_Agent_License.md. In its words: "Where you obtained the package otherwise than at the point of distribution, you accept this license by accepting it at semantichor.com, in the same two confirmations, before any use of the package." and "A copy of the package held without acceptance confers nothing." The acceptance page is https://semantichor.com/agents/bda/license/. Integrity. Boundary_Defense_Agent.zip, 151 files, SHA-256 7e5896806c4fca3348016dcb72d564fb6dc903cdd8a3080b38244250d8917e93. manifest_ref (the SHA-256 of Boundary_Defense_Agent_Manifest.sha256, bound in the License): 76aa2959343a8efd8242b38d306b31952040a6650094d1669f9de7d242aa52f0. agent_manifest_ref (the frozen normative core, 7 files): 20f2a1f655ea5ac55d606019b809e53cfc7180e6b854453cf31618450897617a. The supplementary derivations are archived as a separate record. Use of AI tools. The author constructed the pack's seven canonical files, including the conformance tests, reviewed them manually, and designed and calibrated the NNT harness. Large language models were used openly, as tools to accelerate research and production, with manual review: they assisted the drafting of the pack's documents and, by design, built the five reconstruction baselines in the NNT companion, which are study artifacts, not reference implementations. No tool is an author; the author is accountable for the content. What matters is not which tools touched the documents but whether the pack can be verified: its integrity is anchored by the Manifest and its conformance suite is runnable.