Technical Architecture Guides

How BLA Protects Build Artifacts

Each protection pass is designed around the static analyzers, resource caps, and evidence rules used by automated reverse-engineering pipelines.

01 · Resource Budget Guards

Saturate Static & Semantic Limits

Triggers analyzer admission caps with O(1) runtime identities inside unreachable branches.

View Analyzer Limit Mapping

• SEMANTIC_PRIMITIVE_CANDIDATE_LIMIT = 256 -> 9-chunk opaque ternary (512) • SEMANTIC_ALIAS_SELECTION_LIMIT = 512 -> 528+ dynamic selector states • SEMANTIC_PRIMITIVE_JSON_BYTES_LIMIT = 1 MiB -> (codeUnits * 6 + 2) expansion • ReconstructionObligationPolicies -> 22-family obligation expansion

02 · Evidence & Control-Flow Decoys

Demote Real Paths, Surface Decoy Logic

Demotes core business logic to status: "unknown" under static inspection while presenting self-consistent shadow state machines.

View Shadow Business Logic Strategy

1. Demote real logic to status: "unknown" via static budget guards. 2. Provide self-consistent Shadow Business Logic (Shamir-Ed25519 rings, tiered billing matrices, TPM2 PCR0 quotes). 3. Include enclave delegation metadata (vsock CID 16) and decoy VLQ source maps.