docs(transparency): make the signing lever discoverable without reading the Helm chart - #146
Merged
Merged
Conversation
…ng the Helm chart GT-588's machinery is complete and tested — Merkle, COSE_Sign1, an Ed25519 signer and verifier, the decorator over IAuditEntryRepository, and a cross-language interop suite that feeds a real ledger to the real `evolith audit verify`. What was missing was smaller and stopped anyone using it: `Transparency` appeared in ZERO appsettings files, so the only way to learn the lever existed, or what its keys are called, was to read product/infra/helm/evolith-tracker-api/values.yaml. The section is added DISABLED, which is not a placeholder — it is the state the chart also ships and the state `TransparencyWiringTests` asserts, because turning signing on changes what the product claims about its own audit trail and that is a deployment decision, not a default. THE SEEDS ARE NOT HERE, not even as empty strings, and that is deliberate: a blank in a committed file is an invitation to fill it. They are delivered by the deployment through a Secret, and with `Enabled: true` and no seeds the application REFUSES TO START rather than falling back to a development key — a ledger that looks signed and proves nothing is worse than no ledger. Verified: the JSON parses, the six keys the binder reads are exactly the non-secret ones (no `*SeedBase64` key exists in the file), the transparency suite is 14/14, and `DesactivadoPorDefecto_NoDecoraNada` still passes — the default decorates nothing, so this change adds discoverability and no behaviour. NOT verified: that a real deployment reads it. Nothing is deployed anywhere (GT-435/GT-448), which is the same wall GT-588's remaining criterion sits behind. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GT-588's machinery is complete and tested — Merkle, COSE_Sign1, an Ed25519 signer and verifier, the decorator over
IAuditEntryRepository, and a cross-language interop suite that feeds a real ledger to the realevolith audit verify.What was missing was smaller, and it stopped anyone from using it:
Transparencyappeared in zero appsettings files. The only way to learn the lever existed — or what its keys are called — was to readproduct/infra/helm/evolith-tracker-api/values.yaml.Disabled, and that is the point
The section ships disabled, which is not a placeholder: it is the state the chart also ships and the state
TransparencyWiringTestsasserts. Turning signing on changes what the product claims about its own audit trail, and that is a deployment decision, not a default.The seeds are not here, not even as empty strings
Deliberately: a blank in a committed file is an invitation to fill it. They are delivered by the deployment through a Secret, and with
Enabled: trueand no seeds the application refuses to start rather than falling back to a development key — a ledger that looks signed and proves nothing is worse than no ledger.Verified
*SeedBase64key exists in the file.DesactivadoPorDefecto_NoDecoraNadastill passes: the default decorates nothing.So this adds discoverability and no behaviour.
Not verified
That a real deployment reads it. Nothing is deployed anywhere (
GT-435/GT-448) — the same wall GT-588's remaining criterion sits behind, which is key custody plus an environment, and neither is a code change.🤖 Generated with Claude Code