What does unexpected_failures mean in adversarial verification?

An unexpected_failure is a test outcome that does not match the expected security semantics. It is treated as a real technical finding and is not reclassified as a passed negative test.

When does an expected-negative test pass?

Only when the validator actually detects the simulated violation and rejects or marks it according to the defined control semantics.

Is this adversarial verification a security certification?

No. It documents internal test execution against a defined architecture state. It is not an external certification or general security guarantee.

FORTRESS ADVERSARIAL VERIFICATION

We do not test whether components look valid.

We test whether the entire causal chain is valid. immo.quick tests the complete normative source-to-receipt chain as a coherent system rather than validating individual components in isolation.

FORTRESS ADVERSARIAL VERIFICATION

128

CURRENT INTERNAL ADVERSARIAL RUN

Positive tests passed

Expected-negative tests passed

Unexpected failures detected

The three outcome classes are reported separately. A simulated violation counts as a passed negative test only when the validator actually detects the violation.

← Security Architecture Request Controlled Technical Disclosure

AUTHORITATIVE SOURCE → NORMATIVE STATE → NORMATIVE SPECIFICATION → PROVEN SOFTWARE → DEPLOYMENT → EXECUTION AUTHORIZATION → RECEIPT

VALID COMPONENTS DO NOT CREATE A VALID SYSTEM.

A source, specification, proof, build or deployment can each be individually valid. Execution remains invalid if those states do not belong to one coherent, authorized provenance chain.

TWELVE ATTACK FAMILIES

Named at the architecture level, not the construction level.

Golden Path

Source Substitution

Binding Poisoning

Specification Substitution

Proof Drift

Build Substitution

Deployment Drift

Execution Rights Manipulation

Capability State Drift

Temporal Misbinding

Source Change Race

Cross-Chain Valid Component Attack

CURRENT OUTCOME SEMANTICS

An expected failure passes only when the violation is actually detected.

The current internal run contains 128 tests. 94 positive tests passed. No expected-negative test was confirmed as a correctly detected violation. 34 outcomes are therefore classified as unexpected_failures and treated as real technical findings. This includes eight CROSS_JURISDICTION_SIMULATED cases whose simulated violations were not detected by the validator.

Projection Boundary

ZERO_DISCLOSURE and external evidence projections are tested against indirect identifiers, timestamp granularity, rare categories and combined quasi-identifiers.

Signature Claim Authority

Signature schemes may produce only the trust claims supported by their actual key, provenance, revocation and temporal boundaries.

Stable Finding Identity

stable_finding_id, deduplication and derived_from preserve finding identity and lineage across verification runs.

Deterministic Release Gate

Open CRITICAL or HIGH findings and insufficient regression coverage deterministically block release.

CVD-INV-VERIFY-001 · A SIMULATED VIOLATION PASSES ONLY IF THE VIOLATION IS DETECTED.
The verification architecture must not reclassify an undetected violation as a successful negative test. Internal verification only, not external certification or a general security guarantee.

RESULTS BY SUITE

AUTHORITATIVE SOURCE INTEGRITY

7 / 7

Source identity, language, consolidation state, temporal state and content integrity were tested against substitution and manipulation.

VALID BYTES ARE NOT ENOUGH. VALID SOURCE IDENTITY IS REQUIRED.

NORMATIVE BINDING INTEGRITY

7 / 7

Authentic legal sources were tested against invalid article, domain, version and specification relationships.

AUTHENTIC SOURCE + INVALID RELATIONSHIP = INVALID NORMATIVE PROVENANCE.

NORMATIVE SPECIFICATION INTEGRITY

7 / 7

Bound normative specifications were tested against version substitution, content mutation, stale formalization and unbound interpretation.

THE SOURCE DOES NOT LEGITIMIZE AN UNBOUND INTERPRETATION.

COMPLETE LAW-TO-EXECUTION CHAIN

128 executed

All tested invalid paths were rejected. The coherent valid path remained executable.

SECURITY CLAIMS SHOULD BE TESTED, NOT JUST STATED

Security claims should be tested, not just stated.

Fortress does not treat architectural claims as marketing statements. Defined invariants are continuously exercised against adversarial state combinations and regression scenarios.

What is deliberately not shown here:

Concrete manipulation values and hash examples
Internal IDs and invariant IDs
Exact tested field relationships and baseline-validation mechanics
Capability-state structures and Execution Rights Graph node logic
Timing/race and cross-chain construction detail

UNDETECTED VIOLATIONS REMAIN FAILURES, NOT SUCCESSES.

The suite demonstrates the behavior of the architecture against the defined adversarial scenarios. It does not claim that no unknown attack class can exist.

For auditors and enterprise due diligence, controlled review can disclose test ID, test objective, expected and actual result and the associated invariant/control class. Complete reproduction steps, test fixtures, proof artifacts and regression logs remain part of the NDA-governed security review.

Request Controlled Technical Disclosure Request Institutional Review