Assurance matrix
RS-Key is not formally verified. This page is generated from the registry and reports what evidence exists, not that a whole-system theorem does. The Definition of done keeps this sentence a requirement until one exists, and scripts/claims_gate.py holds every page naming three or more registered properties to it. What is out of scope and what is accepted: limitations and the threat model.
Which security property is claimed about which buildable image. The rows are the P0-family properties of assurance/properties.toml; the columns are derived from nix/firmware.nix, firmware/Cargo.toml and firmware/boards/, so a new package, feature or board arrives as a column of gap cells rather than as silence. scripts/matrix_gate.py regenerates this page and scripts/check.sh diffs it.
The point of the page is the thing a single-build claim hides: the firmware is not one thing. Four of the nineteen images remove the physical-consent gate the authorization properties are about, one swaps the CTAP large-blob surface with no flake package at all, and the board axis changes the flash geometry on which a whole KV store once survived a “successful” wipe.
These are the committed configurations, not the buildable ones. Every mkFirmware knob falls back to a like-named environment variable and lib.mkFirmware is exported, so FLASH_SIZE=2M nix build --impure .#firmware is an image no column below describes — including under a disposition whose reason says “no cargo feature and no build knob”. What this page disposes of is what the flake ships and what CI builds; a one-off --impure combination is outside it by construction.
| Disposition | Code | Means |
|---|---|---|
covered | cov | the evidence the registry records was produced on this configuration; outside the legacy evidence baseline the cell names the check.sh rows, and the gate re-derives both that they build THIS image and that they ran evidence the registry actually derives for the property — a Kani harness, a fuzz target or a tests/*.py, never a crate’s unit tests |
equivalent | equ | this configuration enables exactly the cargo features another does; same_as names it, the gate re-derives both closures, and the cell must write down the build knobs that still differ |
conditional | cnd | claimed only under a stated condition |
out-of-scope | oos | the claim is not made here — the code it is about is absent, or the gate it is about is compiled out |
gap | gap | nobody has decided yet; the column’s settling question is below |
The retained default-build basis refers to the featureless legacy evidence
baseline. It has no current buildable column; dated bundles retain its scope.
TrustZone is mandatory. Its independently built Non-secure closure is
compared separately (NS: below), including the OTP strict-config policy.
Changing the default does not promote earlier legacy evidence to TrustZone.
The direct-Cargo evidence reader cannot establish a composed TrustZone run.
The axes
- 20 flake packages (
nix/firmware.nix), of which 14 are published by.github/workflows/release-build.yml— the published set is a named subset of the matrix, never the matrix. - 7 orthogonal cargo features (
firmware/Cargo.toml) that no flake package expresses. - 6 board presets (
firmware/boards/*.toml):BOARD=<name>sets the same knobs the flake arguments do, and no cargo feature.
Columns
The last cell is DERIVED, not declared: the per-crate cargo-feature closure this column resolves to, against the featureless TrustZone comparison baseline’s. It is the same derivation the equivalent rule refuses a cell on, so a column reading — there compiles the workspace exactly as that comparison baseline does and its whole delta is knobs — and a column that names a crate has that crate’s code moving under every row of its column, which is the fact a gap there is about.
| # | Configuration | Kind | Published | Cargo features | Build mode / knobs | Compiles unlike the comparison baseline |
|---|---|---|---|---|---|---|
| 01 | firmware | package | yes | — | trustzone=true | — |
| 02 | firmware-no-touch | package | no | no-touch | trustzone=true | firmware +no-touch |
| 03 | firmware-fips | package | yes | fips-profile | trustzone=true | firmware +fips-profile, rsk-fido +fips-profile, rsk-piv +fips-profile |
| 04 | firmware-pqc | package | yes | advertise-pqc | trustzone=true | firmware +advertise-pqc, rsk-fido +advertise-pqc |
| 05 | firmware-fips-pqc | package | yes | advertise-pqc, fips-profile | trustzone=true | firmware +advertise-pqc +fips-profile, rsk-fido +advertise-pqc +fips-profile, rsk-piv +fips-profile |
| 06 | firmware-no-touch-pqc | package | no | advertise-pqc, no-touch | trustzone=true | firmware +advertise-pqc +no-touch, rsk-fido +advertise-pqc |
| 07 | firmware-no-touch-fips | package | no | fips-profile, no-touch | trustzone=true | firmware +fips-profile +no-touch, rsk-fido +fips-profile, rsk-piv +fips-profile |
| 08 | firmware-no-touch-fips-pqc | package | no | advertise-pqc, fips-profile, no-touch | trustzone=true | firmware +advertise-pqc +fips-profile +no-touch, rsk-fido +advertise-pqc +fips-profile, rsk-piv +fips-profile |
| 09 | firmware-strong-pin | package | yes | strong-pin | trustzone=true | firmware +strong-pin, rsk-fido +strong-pin |
| 10 | firmware-strong-pin-pqc | package | yes | advertise-pqc, strong-pin | trustzone=true | firmware +advertise-pqc +strong-pin, rsk-fido +advertise-pqc +strong-pin |
| 11 | firmware-always-uv | package | yes | always-uv | trustzone=true | firmware +always-uv, rsk-fido +always-uv |
| 12 | firmware-always-uv-pqc | package | yes | advertise-pqc, always-uv | trustzone=true | firmware +advertise-pqc +always-uv, rsk-fido +advertise-pqc +always-uv |
| 13 | firmware-strict-up | package | yes | strict-up | trustzone=true | firmware +strict-up, rsk-fido +strict-up |
| 14 | firmware-strict-up-pqc | package | yes | advertise-pqc, strict-up | trustzone=true | firmware +advertise-pqc +strict-up, rsk-fido +advertise-pqc +strict-up |
| 15 | firmware-pico | package | no | — | trustzone=true, vidpid=Pico | — |
| 16 | firmware-display | package | yes | display | trustzone=true, flashSize=16M, ledKind=none | firmware +display, rsk-bip39 (added), rsk-device +display, rsk-display (added), rsk-slip39 (added), rsk-ui (added) |
| 17 | firmware-display-v2 | package | no | display | trustzone=true, flashSize=16M, ledKind=none, tpChip=cst3530 | firmware +display, rsk-bip39 (added), rsk-device +display, rsk-display (added), rsk-slip39 (added), rsk-ui (added) |
| 18 | firmware-2mb | package | yes | — | trustzone=true, flashSize=2M, kvmain=896K | — |
| 19 | firmware-16mb | package | yes | — | trustzone=true, flashSize=16M | — |
| 20 | firmware-strict-config | package | yes | strict-config | trustzone=true | firmware +strict-config, rsk-device +strict-config, rsk-fido +strict-config, rsk-mgmt +strict-config, rsk-otp +strict-config, rsk-vendor +strict-config, NS:firmware-ns +strict-config, NS:rsk-otp +strict-config |
| 21 | keygen-bench | feature | n/a | keygen-bench | trustzone=true | firmware +keygen-bench |
| 22 | core1-stats | feature | n/a | core1-stats | trustzone=true | firmware +core1-stats |
| 23 | bench | feature | n/a | bench | trustzone=true | firmware +bench, rsk-bench (added), rsk-fido +bench |
| 24 | fido-conformance | feature | n/a | fido-conformance | trustzone=true | firmware +fido-conformance, rsk-fido +fido-conformance +strict-up |
| 25 | ea-conformance-rpid | feature | n/a | ea-conformance-rpid | trustzone=true | firmware +ea-conformance-rpid, rsk-fido +ea-conformance-rpid +fido-conformance +strict-up |
| 26 | largeblob-ext | feature | n/a | largeblob-ext | trustzone=true | firmware +largeblob-ext, rsk-fido +largeblob-ext |
| 27 | preview-sign | feature | n/a | preview-sign | trustzone=true | firmware +preview-sign, rsk-fido +preview-sign |
| 28 | abrobot-16m | board | n/a | — | trustzone=true, flash.kvmain_kb=1408, flash.size_mb=16, led.kind=ws2812, led.max_leds=4, led.order=grb, led.pin=16, presence.active_high=False, presence.pin=23, presence.source=gpio, usb.vidpid=RSKey | — |
| 29 | abrobot-4m | board | n/a | — | trustzone=true, flash.kvmain_kb=1408, flash.size_mb=4, led.kind=ws2812, led.max_leds=4, led.order=grb, led.pin=16, presence.active_high=False, presence.pin=23, presence.source=gpio, usb.vidpid=RSKey | — |
| 30 | seeed-xiao | board | n/a | — | trustzone=true, flash.kvmain_kb=896, flash.size_mb=2, led.kind=ws2812, led.order=grb, led.pin=22, led.power_pin=23, presence.source=bootsel, usb.vidpid=RSKey, usr_led.active_high=False, usr_led.pin=25 | — |
| 31 | tenstar-usb | board | n/a | — | trustzone=true, flash.kvmain_kb=1408, flash.size_mb=16, led.kind=ws2812, led.order=grb, led.pin=22, presence.source=bootsel, usb.vidpid=RSKey | — |
| 32 | waveshare-one | board | n/a | — | trustzone=true, flash.kvmain_kb=1408, flash.size_mb=4, led.kind=ws2812, led.order=rgb, led.pin=16, presence.source=bootsel, usb.vidpid=RSKey | — |
| 33 | waveshare-touch-lcd | board | n/a | — | trustzone=true, display.bl_pin=16, display.bl_pwm_channel=A, display.bl_pwm_slice=0, display.cs=13, display.dc=14, display.rst=15, display.spi_freq_hz=80000000, display.tp_chip=cst328, display.tp_rst=17, display.wake_active_high=False, display.wake_pin=25, flash.kvmain_kb=1408, flash.size_mb=16, led.kind=none, presence.source=bootsel, usb.vidpid=RSKey | — |
The matrix
41 rows × 33 columns = 1353 cells. Column numbers are the table above.
| Property | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SEC-FIDO-001 | gap | oos | gap | gap | gap | oos | oos | oos | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-FIDO-002 | gap | oos | gap | gap | gap | oos | oos | oos | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-FIDO-003 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-FIDO-004 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-FIDO-005 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-FIDO-006 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-FIDO-006A | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-FIDO-006B | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-FIDO-006C | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-FIDO-007 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-FIDO-008 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-SEAM-001 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-SEAM-002 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-SEAM-003 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-SEAM-006 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-STORE-001 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-STORE-002 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-STORE-003 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-STORE-004 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-STORE-005 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-STORE-006 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-LAT-001 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-LAT-002 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-LAT-003 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-LAT-004 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-POL-001 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-POL-002 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-POL-003 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-POL-004 | gap | oos | gap | gap | gap | oos | oos | oos | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-POL-005 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-POL-006 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-ADM-002 | gap | oos | gap | gap | gap | oos | oos | oos | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-ADM-004 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-DISP-001 | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | gap | gap | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos |
SEC-DISP-002 | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | gap | gap | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos |
SEC-DISP-003 | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | gap | gap | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos | oos |
SEC-BOOT-001 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-BOOT-002 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-TRANS-001 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-TRANS-002 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
SEC-TRANS-003 | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap | gap |
Dispositions
out-of-scope — basis crate-absent
- columns:
firmware,firmware-no-touch,firmware-fips,firmware-pqc,firmware-fips-pqc,firmware-no-touch-pqc,firmware-no-touch-fips,firmware-no-touch-fips-pqc,firmware-strong-pin,firmware-strong-pin-pqc,firmware-always-uv,firmware-always-uv-pqc,firmware-strict-up,firmware-strict-up-pqc,firmware-pico,firmware-2mb,firmware-16mb,firmware-strict-config,keygen-bench,core1-stats,bench,fido-conformance,ea-conformance-rpid,largeblob-ext,preview-sign,abrobot-16m,abrobot-4m,seeed-xiao,tenstar-usb,waveshare-one,waveshare-touch-lcd - properties:
SEC-DISP-001,SEC-DISP-002,SEC-DISP-003 rsk-displayowns the ceremony andrsk-uithe screen model, and both aredep:-gated behind--features display. The feature resolution the gate re-runs puts neither crate in any of these builds, so there is no ceremony to make a claim about. Note what this does NOT say:waveshare-touch-lcdis the trusted-display BOARD and still lands here, because a board preset sets knobs and never a cargo feature — the panel pins are compiled as inert constants.
out-of-scope — basis gate-compiled-out (feature = no-touch; gate: firmware/src/presence.rs; hook: rsk_sdk::UserPresence)
- columns:
firmware-no-touch,firmware-no-touch-pqc,firmware-no-touch-fips,firmware-no-touch-fips-pqc - properties:
SEC-FIDO-001,SEC-FIDO-002,SEC-POL-004,SEC-ADM-002 no-touchreplaces the button watcher with an instant auto-confirm (firmware/src/presence.rs), so the physical-consent gate these four statements are ABOUT is not in the image: “the live authorization its own gate requires”, “a presence decision produced for one transport”, “a confirmed physical press”, “a Confirmed operator presence”. The claim is not weakened here, it is not made — and the tree already treats these builds that way. None of the four is published,firmware/Cargo.tomlsays “Never ship a no-touch build”, andrelease-build.ymlrefuses to create a release carrying one. “No-touch image” in the singular is the phrasing that hid four packages.
Open gaps
The middle column is derived, and it is what a gap here costs: the open rows whose OWNING crates — the ones whose production Rust carries the property’s tag — are among the crates the column compiles unlike the comparison baseline, above. Outside it, the code the statement is about did not move and the question is whether the rest of the image reaches it; inside it, the statement is about a different compilation. Every P0-family row carries a production tag, so the one direction this number could be wrong in — an untagged row counting as not moving — is empty here.
The two after it are the ledger’s, and they are Stage 0’s last exit bullet: who owes the answer, and what would end the deferral. Settled by is typed rather than dated — evidence is a check.sh row built at this column, absence an out-of-scope argument, sameness an equivalent one, and ruling a decision no derivation can produce, which is the maintainer’s. The gate refuses sameness where the closure delta is non-empty and absence where neither of its bases can reach a row, so two of the four are claims the tree can already disagree with.
| Configuration | gap rows | of which the owner crate moves | Owed by | Settled by | The question that would settle them |
|---|---|---|---|---|---|
firmware | 38 | 0 | contributor | evidence | Which applet and authorization properties retain scoped evidence in the default combined TrustZone image? Earlier monolithic evidence stays in dated bundles. The Secure IRQ worker, hardware-owned USB epochs, CMSE packet gateways, fatal admission fencing and banked FP policy need evidence from this build. Crypto, presence and reset image tests cover specific behavior. Resolve each property against its current implementation and evidence before claiming coverage. |
firmware-no-touch | 34 | 1 | contributor | absence | Beyond the four presence statements: which rows depend on a presence decision only INDIRECTLY — a reset is reached through a touch, so does SEC-FIDO-006’s torn-reset argument still describe an image where the touch is instant? |
firmware-fips | 38 | 17 | contributor | evidence | fips-profile changes rsk-fido and rsk-piv — the PIN policy and the permitted algorithm set. check.sh runs the rsk-fido and rsk-piv test suites under it, so the question is narrow: does any P0-family invariant’s model take the PIN floor or the algorithm set as a parameter, and if so, was it re-checked at the profile’s values? |
firmware-pqc | 38 | 11 | contributor | evidence | advertise-pqc only adds ML-DSA-44 to the getInfo algorithm list — is that the whole delta for every P0-family row, or does the larger credential/attestation path move with it? |
firmware-fips-pqc | 38 | 17 | contributor | evidence | As firmware-fips, on the combination with advertise-pqc; the pair is published and nothing measures the two features together. |
firmware-no-touch-pqc | 34 | 10 | contributor | absence | As firmware-no-touch, plus: does advertising ML-DSA-44 in getInfo change any authorization path, or only the algorithm list? |
firmware-no-touch-fips | 34 | 16 | contributor | absence | As firmware-no-touch, plus the fips-profile question: the locked algorithm policy also raises the PIN floor, so which retry/gate properties are re-measured under it? |
firmware-no-touch-fips-pqc | 34 | 16 | contributor | absence | The union of the firmware-no-touch, firmware-fips and firmware-pqc questions; no evidence is measured on the three-feature combination at all. |
firmware-strong-pin | 38 | 11 | contributor | evidence | A six-code-point floor and a trivially-guessable-PIN refusal. Does any P0-family statement quantify over PIN values, or do they all treat the PIN as an opaque secret whose policy is someone else’s row? |
firmware-strong-pin-pqc | 38 | 11 | contributor | evidence | As firmware-strong-pin, on the combination with advertise-pqc. |
firmware-always-uv | 38 | 11 | contributor | evidence | always-uv ships alwaysUv ON, which changes what SEC-FIDO-001’s gate DEMANDS rather than whether it is enforced — and SEC-FIDO-006B is about the alwaysUv gate surviving a reset, with a compiled-in default this column moves. Do the model’s gate constants cover the alwaysUv-on arm? THE MODEL HALF IS ANSWERED: AlwaysUvShipped is AS-AUTH-2 in assurance/assumptions.toml, and formal/AlwaysUv.cfg runs TypeOK plus the eight P0-launch invariants with it TRUE — GREEN over 31 451 172 distinct states at depth 51, per formal/runs.toml. Read the cfg for that count, never this sentence: it said “all six invariants”, and the file has carried nine entries in every commit it has ever had, so the number was wrong when it was written rather than gone stale — a count restated beside a file is a count that disagrees with it. THE CODE HALF IS NOT, and its cost is a number rather than an omission: cargo test -p rsk-fido --features always-uv --target "$HOST" came back 496 passed, 176 failed and 1 ignored — the harness’s own running 673 tests, rc 101 — run at commit 709cb52, because alwaysUv with no PIN answers PUAT_REQUIRED and the suite is written against the default door. The run is NAMED here because the sentence it replaces was not: is 493 passed and 176 FAILED, present tense, no commit, no date, over a suite that grows most weeks — a measurement written as a property of the column. The commit IS the date and is deliberately the only half written here: git dates a sha exactly, and scripts/run_count_gate.py refuses a second copy of a day its generated regions already print — the tier-run table of assurance/reports/assurance-vector.md prints this one, and typing it again here reddens that row (driven, EXIT=1). Write the target the way scripts/check.sh does: this said aarch64-apple-darwin, which is one maintainer’s host triple pinned into a shared register, and CI runs the same row at x86_64-unknown-linux-gnu. And say which convention the denominator uses, because this tree has two and they differ by exactly the one ignored test: 673 is passed + failed + IGNORED, which is the number the harness prints and the number every count below is in. The pair 446/172 is NOT a superseded version of this one and must not be reconciled with it: it is what assurance/bundle/logs/cargo-test-always-uv.log holds, over 619 tests, and 619 counts the same way — two true measurements of a growing suite, which is why the bundle’s own framing of that log is the thing to fix and not this number. The 669 that stood here was the third convention, passed + failed with the ignored test dropped; under the log’s it was 670, and no reader could have told the two apart. So no check.sh row exercises this column, and covered may rest only on the default build or on such a row — the matrix has no basis for “the model half is checked at this column’s own constant”, which is evidence-schema work and not a cell anybody can fill here. |
firmware-always-uv-pqc | 38 | 11 | contributor | evidence | As firmware-always-uv, on the combination with advertise-pqc. |
firmware-strict-up | 38 | 11 | contributor | evidence | strict-up demands a touch on EVERY assertion, dropping the silent up:false pre-flight. That strengthens the gate — but SEC-FIDO-002 is about presence decisions not crossing transports, and this column produces strictly more of them. Is the model’s transport arity still the right one? |
firmware-strict-up-pqc | 38 | 11 | contributor | evidence | As firmware-strict-up, on the combination with advertise-pqc. |
firmware-pico | 38 | 0 | contributor | evidence | Which properties hold for the combined TrustZone image with the Pico USB identity? Its former legacy closure equivalence does not establish the new execution mode or its Non-secure composition. |
firmware-display | 41 | 6 | contributor | evidence | This column is NOT default + display: it also sets flashSize = 16M and ledKind = none, and it re-routes user presence through the panel’s Approve/Deny instead of the button. Each non-display row therefore has to answer three questions, not one — and the flash-geometry half is the same 16 MB question the board axis carries. It reaches the three SEC-DISP-* rows too, which is why they are gap here and not covered: the ceremony’s evidence — formal/Display.cfg, the rsk-ui/rsk-display host tests and the check.sh rows that compile the feature — was every bit of it produced at the DEFAULT 4 MB geometry. The BUILD half is answered now: build firmware (display) sets FLASH_SIZE=16M too, so the gate compiles the image this column IS rather than a combination no package ships. The EVIDENCE half is not, and that is what keeps these three at gap — Display.cfg, the rsk-ui/rsk-display host tests and the three co-mutants all run at the default geometry, and BugPadSubstitutesForCard runs in rsk-fido with no display feature at all. Closing it takes evidence produced at this configuration, or a conditional saying what the ceremony claim is conditional on. |
firmware-display-v2 | 41 | 6 | contributor | evidence | The V2 package selects the CST3530 driver with DISPLAY_TP_CHIP=cst3530. The gate builds it and checks the stack floor. The image harness can exercise its I2C transactions and report handling. Touch alignment, timing and the electrical behavior still need evidence from a physical V2 board. |
firmware-2mb | 38 | 0 | contributor | evidence | 2 MB with KVMAIN shrunk to 896 K. Do the store properties’ models take the partition size as a parameter, and were they checked at the shrunk one? The scope floors in formal/floors.txt are about model constants, not about the device’s own capacity. |
firmware-16mb | 38 | 0 | contributor | evidence | 16 MB with the default 1408 K KVMAIN. This is the geometry on which a whole KV store survived a wipe the device reported as successful — so for every store and boot row the question is not “does the code differ” (it does not) but “was the evidence ever produced against this partition map”. |
firmware-strict-config | 38 | 15 | contributor | evidence | The largest feature delta in the tree: five crates, and it re-imposes the presence/PIN gates on device-config writes that the DEFAULT build leaves ungated. SEC-ADM-002 and SEC-ADM-004 are about exactly that surface, so this column is the one where their disposition may be STRONGER than the default’s — which the matrix has no way to say until someone measures it. |
keygen-bench | 38 | 1 | contributor | evidence | A debug vendor command (INS 0x13) that firmware/Cargo.toml says never to ship, and it exposes a timing oracle over the primality primitives. Its never-shipped half is settled above; its sameness half is settled by measurement, and against the hoped-for answer — the closure is NOT the default build’s, so same-cargo-features is refused here by derivation rather than by opinion. No cargo-feature column can ever earn that basis, because the feature NAMING the column is in that column’s own closure by construction, which makes “is it equivalent” a question the derivation answers before it is asked. What the derivation does say is how narrow the delta is, and the page counts it: the crate set is the default build’s exactly and firmware is the only crate whose features move, so all but one of the open rows here own code that resolves identically. What is left is not derivable — does a vendor INS answering on this image, gated by nothing, reach a statement whose own crate did not move? SEC-BOOT-002 is the row where that is not even the question, because firmware is its owner. |
core1-stats | 38 | 1 | contributor | evidence | As keygen-bench: INS 0x12 exposes per-core candidate/find rates, which time the RSA keygen prime search. The measurement lands in the same place and for the same reason — the crate set is the default build’s, firmware alone moves — so this column’s narrowness is not inherited from that one’s, it is re-derived on every run and printed beside this row. |
bench | 38 | 11 | contributor | evidence | As keygen-bench, and the one of the three the measurement separates rather than groups: bench is not a firmware-only delta. It turns on rsk-fido/bench and pulls rsk-bench into the image, so the rsk-fido-owned rows and SEC-BOOT-002 are open on a column where the code they are ABOUT is a different compilation, and the rest are not. It is also the only one of the three with check.sh rows — and none of them is evidence for a P0-family statement: clippy (bench fw) and clippy (bench host) are lints, and test (bench) selects rsk-fido under the name FILTER bench, which --list answers with the harness’s own four selector tests and one #[ignore]d timing loop — no invariant among them. So covered has nothing to rest on here either, and the open question is the keygen-bench one plus whichever rsk-fido statements a second timing entrypoint can reach. |
fido-conformance | 38 | 11 | contributor | evidence | Built only for the FIDO Conformance Tool run: it suppresses the EdDSA advertisement. Its “is a conformance-only build in the supported set” half was the same parked ruling the three measurement columns carried and is settled above with them. What is left is narrower AND wider than the sentence used to say, because the closure the page derives names a second feature: fido-conformance implies strict-up, so this column also demands a touch on EVERY assertion. Two questions then, not one — does any P0-family row depend on the advertised algorithm list, and does firmware-strict-up’s transport-arity question apply here too? |
ea-conformance-rpid | 38 | 11 | contributor | evidence | Adds the conformance tool’s RPID to the vendor-facilitated enterprise-attestation list, which is an authorization-relevant allowlist. SEC-FIDO-001 is about gates; is an EA RPID list one of them? |
largeblob-ext | 38 | 11 | contributor | evidence | The sharpest orthogonal feature: it serves the CTAP 2.3 largeBlob extension INSTEAD OF the 2.1 largeBlobKey + authenticatorLargeBlobs pair (the spec forbids both), it carries four check.sh rows, and it has zero flake packages — so nothing in the release axis would ever have given it a cell. Does the swapped surface move any credential-management or authorization transition the P0-launch models name? |
preview-sign | 38 | 11 | contributor | evidence | Yubico’s draft previewSign extension, off by default: a registration that asks for it gains an ARKG seed and a second attestation object, and an assertion signs the site’s digest behind the same UP and UV gates, storing nothing. Does either path move a gate, a counter or a record a P0-launch model names? |
abrobot-16m | 38 | 0 | contributor | evidence | The 16 MB geometry question of firmware-16mb, plus a GPIO presence source instead of BOOTSEL. |
abrobot-4m | 38 | 0 | maintainer | evidence | The narrowest column with anything open, and it is now one group and one question: does a GPIO button on 23 (active-low) deliver the Confirmed/Cancelled semantics the presence model assumes of BOOTSEL — same debounce, same cancellation, same per-transport arbitration? Only the four rows that quantify over a presence decision are still open on it. The four reset clauses used to be held here as reached-through-a-touch; that is a reachability argument and it is withdrawn in the cell above, where applied evenly it would have taken SEC-FIDO-003 out with them. What is left is genuinely about the button: crates/rsk-device/src/presence.rs arbitrates the scope and firmware/src/presence.rs holds the latch, and both compile identically here — the one arm that moves is the raw sample. |
seeed-xiao | 38 | 0 | contributor | evidence | 2 MB with KVMAIN at 896 K — the firmware-2mb question on a board that also gates the LED behind a power pin. |
tenstar-usb | 38 | 0 | contributor | evidence | The 16 MB geometry question of firmware-16mb; presence is BOOTSEL, as on the default image (issue #125). |
waveshare-one | 38 | 0 | contributor | evidence | Which properties have evidence under the default TrustZone build on the reference board? The board geometry remains known, but it does not transfer legacy execution evidence to the combined image. |
waveshare-touch-lcd | 38 | 0 | maintainer | ruling | The trusted-display BOARD without the display feature: 16 MB geometry, no addressable LED, and panel pins compiled as inert constants. The geometry question is firmware-16mb’s. The sharper half is now measured rather than asked: this preset IS buildable without --features display — build.rs parses the [display] keys with no CARGO_FEATURE_DISPLAY gate — and nothing in check.sh builds firmware on it at all. The board loop builds rsk-wipe, and both BOARD= firmware rows pin waveshare-one. So the column is real and WHOLLY UNEXERCISED, and what is left to decide is whether the tree should build it, or whether it should be a knob of firmware-display instead. |
Property names
| ID | Invariant | Tranche |
|---|---|---|
SEC-FIDO-001 | NoAuthorizationBypass | p0-launch |
SEC-FIDO-002 | NoCrossTransportTouchConsumption | p0-launch |
SEC-FIDO-003 | NoTokenAfterInvalidation | p0-launch |
SEC-FIDO-004 | NoAccessibleSecretWithoutGate | p0-launch |
SEC-FIDO-005 | NoUnmanageableCredential | p0-launch |
SEC-FIDO-006 | ResetNeverWeakensSurvivingState | p0-launch |
SEC-FIDO-006A | ResetKeepsThePinGate | p0-launch |
SEC-FIDO-006B | ResetKeepsTheAlwaysUvGate | p0-launch |
SEC-FIDO-006C | ResetKeepsTheBackupSeal | p0-launch |
SEC-FIDO-007 | RamNeverOutlivesFlashSeed | p0-launch |
SEC-FIDO-008 | NoLiveTokenWithoutPinRecord | p0-launch |
SEC-SEAM-001 | NoStatusOutsideItsSelection | p0b |
SEC-SEAM-002 | NoStatusAfterARefusedAuth | p0b |
SEC-SEAM-003 | NoKeyOpOnTheAdminStatus | p0b |
SEC-SEAM-006 | AccessCodeRemovalNeedsTheCode | p0b |
SEC-STORE-001 | NoOrphanedMetadata | p0-launch |
SEC-STORE-002 | NoFalseAbsent | p0-launch |
SEC-STORE-003 | NoRecordLostToMetaWrite | p0-launch |
SEC-STORE-004 | NoFalseMetaAbsent | p0-launch |
SEC-STORE-005 | CacheHonest | p0-launch |
SEC-STORE-006 | NoSilentOrphan | p0-launch |
SEC-LAT-001 | NoAuthWhenBlocked | p0b |
SEC-LAT-002 | WrongAttemptIsCharged | p0b |
SEC-LAT-003 | BudgetRisesOnlyWithItsSecret | p0b |
SEC-LAT-004 | CountWithinMaximum | p0b |
SEC-POL-001 | PivOperationNeedsSlotPolicy | p0b |
SEC-POL-002 | PivAlwaysSpendsFreshness | p0b |
SEC-POL-003 | AttributeChangeInvalidatesTheKey | p0b |
SEC-POL-004 | OathCredentialNeedsItsGates | p0b |
SEC-POL-005 | OtpSlotMutationNeedsItsCode | p0b |
SEC-POL-006 | OtpCounterNeverRepeats | p0b |
SEC-ADM-002 | PrivilegedOpNeedsPresence | p0b |
SEC-ADM-004 | DisabledAppletNeverDispatches | p0b |
SEC-DISP-001 | ConfirmNamesTheOperation | p0b |
SEC-DISP-002 | StaleTouchApprovesNothing | p0b |
SEC-DISP-003 | OnlyAllowConfirms | p0b |
SEC-BOOT-001 | MarkerNeverLies | p0b |
SEC-BOOT-002 | TheWholeLockRides | p0b |
SEC-TRANS-001 | NoCrossChannelSplice | p0b |
SEC-TRANS-002 | NoSequenceGap | p0b |
SEC-TRANS-003 | NoBufferOverrun | p0b |