Phase 0: stop the unsupported claims (Sep 8 audit) - #9
Merged
Conversation
Sep 8 audit §28 applied to the site. The feature cards claimed TTLs, a read/write credential split, entry-size/top-miss visibility, a day-one Gradle/JDK compatibility matrix, and a config translator — none of which exist. Each card now describes what ships. The trust list's "license key unlocks" goes future-tense and labeled; "public compatibility matrix" is replaced by what is real. Maven "drop-in" is qualified in the lede and llms.txt; Gradle keeps the claim because a real acceptance test backs it. The maturity label points at SECURITY.md for exactly what the release evidence proves today.
Deploying www with
|
| Latest commit: |
13a66ed
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://39b624d7.www-4rw.pages.dev |
| Branch Preview URL: | https://phase0-claims.www-4rw.pages.dev |
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.
This PR stays open for your cold read, same as cache#42 — the two halves of Phase 0 should be approved together.
The Sep 8 audit's §28 corrections, applied to the site. Everything here is a present-tense claim the product now backs, or an explicitly labeled intention.
What was false, and what it says now
No timelines added, no email capture, no 800-204D anywhere (checked).