Skip to content

row 159: audit ledger records the secret-file declares reading (stacked on #845) - #915

Open
MattJackson wants to merge 1 commit into
lane-audit-159-readings-2from
lane-audit-159-secret-file-declares
Open

MattJackson wants to merge 1 commit into
lane-audit-159-readings-2from
lane-audit-159-secret-file-declares

Conversation

@MattJackson

Copy link
Copy Markdown
Collaborator

This PR changes only the ledger (qa/audit-ledger.json). It is stacked on #845, which carries #835 and #820, so it holds their commits.

What. One new round for crates/busbar-secret-file/declares.json, round 1 at 00555bd (an ancestor of predev), result zero. #820 recorded the other declares documents, and this one was still unaudited after #845.

What the reading found:

  • The document is {"contract_abi": {"min": 2, "max": 2}}, the pin is busbar-secret-file 479c833a10, and the pin is the same on predev 1d37d86.
  • The range is superseded. The shipping loader parses it but no longer reads it at admission (crates/plugin-loader/src/sign.rs:300-305, :990).
  • The range names the secret kind's one version, 2, at both hosts: the shipping host (crates/busbar-contract/src/abi/secret/mod.rs:40) and the plugin's own pinned host c4d7254. The pinned host's pack check (sign.rs:886-905 there) admits it. This differs from secret-env's document, which declares 1 and carries a MEDIUM.
  • The Statement (secret-file/src/door.rs:41-44) names no transport need, and the plugin declares no metric or diagnostic, so nothing is missing.

The tree_hash was recomputed at 00555bd with the pinned plugin mounted from Cargo.lock, the same way xtask/src/audit.rs / audit_pinned.rs do it. As a check, the same tool reproduces the recorded hashes of the sibling secret-env and transport-tcp declares scopes.

Why. /status row 159 needs 0 unaudited production scopes. After #820, #835, #845 and this PR, three scopes remain unaudited: crates/busbar-a2a/src, crates/busbar-llm/src and crates/busbar-voice/src. Per the ARCHITECT ruling, each leaves with its deletion PR (#787, row 155, #503).

RED-able. No code changes. On ModernCI, cargo xtask ledger --check checks the new round: stamped if the hash is not the tree at audited_at, unreachable if the commit is not an ancestor.

…ited pinned scope (row 159)

crates/busbar-secret-file/declares.json, round 1 at 00555bd: zero. The document states only the
superseded contract range {2,2}. That is the secret kind's one version at the shipping host
(busbar-contract abi/secret/mod.rs:40) and at the plugin's pinned host c4d7254, whose
sign.rs:886 range check admits it. The shipping loader no longer reads the range
(plugin-loader sign.rs:300-305). The source's Statement (secret-file/src/door.rs:41-44) names no
need, and the plugin declares no metric or diagnostic. The tree_hash was recomputed with the
pinned plugin mounted from Cargo.lock (secret-file 479c833a10, the same pin on predev).

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant