Binary analysis and symbol ownership
The Vulnerabilities service owns binary vulnerability facts, reference generation, fingerprint storage, VEX derivation, symbol metadata and global symbol availability. Scanner consumes the exported offline build-ID index and the hub’s closed symbol client. The BinaryIndex.WebService, BinaryIndex.Worker and Symbols.Server source projects are frozen by BIN-10. They have no publish key or active Compose declaration.
Verified source commit: ed03a9c857f29a4180e7aa50111c4d9860e073b0. Re-verify with tools/scripts/test-targeted-xunit.ps1 -Project src/__Tests/architecture/StellaOps.Architecture.Contracts.Tests/StellaOps.Architecture.Contracts.Tests.csproj -Class '*BinaryPlaneRetirementConformanceTests' and tools/scripts/build-boundary/generate-build-boundary-report.ps1 -Check. The BIN-8 rehearsal records isolated runtime and restart acceptance. Source retirement is distinct from the standing-estate activation and retirement window. Dropping predecessor schemas remains deferred; this document grants no operational authorization.
Ownership and dependency boundaries
| Capability | Current source owner |
|---|---|
| Binary facts, generation runs, raw fingerprint vectors, issuer derivation | src/Vulnerabilities/ |
| Global symbol source/catalog metadata and manifest admission | StellaOps.Vulnerabilities.Symbols |
| Symbol payload bytes | Configured content-addressed object store; hub records digest and metadata |
| Offline DeltaSig format, normalization and local computation | Closed StellaOps.Vulnerabilities.BinaryArtifacts SDK |
| DeltaSig workflow and fingerprint generator implementation | Hub-owned Vulnerabilities.DeltaSig and Vulnerabilities.Fingerprints |
| Offline build-ID artifact consumption, ML inference, reproducible-build verification | src/Scanner/ |
| Corpus KPI regression reports | Dev-only src/Tools/Bench/StellaOps.Bench.Oracle/Regression/ |
D-BIN5-6 retains the physical shared analysis stack under src/BinaryIndex/__Libraries/: Contracts, Disassembly, Disassembly.Abstractions, Semantic, Decompiler and Ghidra. The Iced and B2R2 backend plugins remain with that stack. These projects contain analysis or plugin primitives and may not acquire vulnerability workflow, persistence or hosting. The BCL-only StellaOps.Symbols.Contracts retains its closed SymbolManifest artifact shape for existing DeltaSig consumers. It is not a runtime repository abstraction. The ownership manifest and closure checks enforce these boundaries.
Supported consumer paths
The hub serves binary operations under /api/vulnerabilities/v1/binaries and symbol operations under /api/vulnerabilities/v1/symbols. See the Vulnerabilities API reference for the current schema, routes, authorization and errors. No old BinaryIndex or Symbols route aliases are provided.
The Console manages symbol source configuration and catalog entries through the hub API. Upload admits real manifest metadata and CAS bytes; resolve looks up actual admitted symbols. Catalog activation adds global availability membership only after the referenced manifest and its content pass validation. Deactivation removes availability membership; it does not delete the admitted content. These operations are installation control-plane actions, not tenant-owned corpus rows. They do not claim remote package installation or automatic source synchronization.
Digest integrity uses Stella Ops cryptography. A digest match is not DSSE or trust verification. Signed manifest claims use the exact application/vnd.stellaops.symbols.manifest.v1+json payload type and configured, purpose-bound public trust. Private key custody remains with the configured purpose signer. The CLI’s symbols validate performs structural validation; symbols verify requires an actual valid signed envelope. Upload/read/resolve/health use the authenticated owner client. The always-failing symbols ingest declaration was withdrawn in BIN-8.
Local deltasig extract, author, match, sign, verify, pack and inspect, and the separate binary deltasig surface remain available. They use BinaryArtifacts and configured purpose signing. The old groundtruth plugin is withdrawn: source enable/disable/sync, symbol lookup and pair commands returned hardcoded success or empty data without performing the claimed operation. Its separate core command tree was unregistered. No replacement pretends those operations worked. The hub’s explicit generation and source/catalog APIs are the supported paths described above.
Persistence and retired source
The hub resolves its own STELLAOPS_POSTGRES_VULN_CONNECTION and applies forward-only embedded migrations. Symbol bytes use the configured durable CAS root; no fallback turns missing durable storage into a successful startup. Existing predecessor schemas in the shared database are retained pending the separately authorized retirement window. No frozen migration is applied by a current host, and no hub golden-set tables are introduced by this retirement.
Withdrawn implementation and its implementation-specific tests are preserved under src/__Obsoleted/ with freeze records. A BIN-10 subdirectory distinguishes remaining files from an earlier frozen incarnation where paths overlap. The unregistered GoldenSet-backed Policy predicate/adapter is frozen; the independent live StellaOps.Policy.Gates.FixChainGate remains. Old GoldenSetDiff and binary-lookup benchmarks that tested withdrawn runtime models are frozen. The oracle’s genuinely used KPI engine and its regression tests were moved, with no duplicate implementation.
Acceptance
The retirement guard rejects reintroduced hosts, service keys and unclassified BinaryIndex implementation projects. Obsoleted-isolation checks forbid active references into frozen source. Build-boundary, database-ownership, startup migration, tenant, eager-store and OpenAPI inventories must agree with the remaining hosts. Preserved analysis, artifact, Policy and CLI tests establish that retirement does not remove their supported consumers.
The BIN-10 sprint records exact commands and counts. Its final live criteria remain open until the owner executes the standing-estate window and records the resulting evidence.