Restore #12/#13 content that merged into feature branches, not main - #16
Merged
Conversation
Deploying www with
|
| Latest commit: |
2288ee1
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://cf0b7f6c.www-4rw.pages.dev |
| Branch Preview URL: | https://copy-restore-pricing-and-wed.www-4rw.pages.dev |
… line Business-model work order §2, authority business-model-and-marketing.md §4/§4a. Free drops 'Forever free' and states what free includes (every patch, the -fips image, all release evidence); Team retires 'metrics UI' (the status page is free) and gains SSO (OIDC), per-project analytics and the 1-business-day email target; Business says 'CVE-response target', never SLA; Compliance is $499/month billed annually with the checklist nouns loud and the Sep 5 honesty line: the evidence underneath is public and free, what is paid is the authored analysis, the vendor signature, and the hours. Never 'FedRAMP compliant'/'CMMC compliant'. 'No sales call. No per-seat tax. No enterprise pricing mystery.' under the table; self-serve sentence updated (monthly tiers cancel anytime; Compliance is an annual term); roadmap-honesty lists all the tiers it describes. llms.txt tier list matches. Stacked on the phase3/www-claims branch — both touch the self-serve paragraph.
Owner correction (Sep 11, business-model work order): 'an npm remote cache — a third protocol' misled — it read as a package-registry cache or a new wire protocol and it is neither. Replaced with the approved sentence: the same server caching node_modules, test caches, and build outputs by lockfile key, so Jenkins and GitLab jobs stop reinstalling the world on every run. 'Node cache', never 'npm cache', from now on. No timelines.
The Sep 12 product definition supersedes the Node-cache wording: the feature is the dependency cache - the same server restoring node_modules, ~/.m2, and ~/.gradle/caches by lockfile key, so ephemeral CI agents stop re-downloading the world - npm first. Public vocabulary from now on: 'build cache' (Gradle, Maven) and 'dependency cache' (Gradle, Maven, npm); never 'npm cache', never 'Node cache'.
The whole $57k parenthetical is deleted, not softened - the owner's hard rule is that no competitor price appears on any customer-visible surface. 'Priced so an engineering manager can expense it without a procurement cycle.' stands on its own. Because this PR's stack rewrites the same paragraph, the older '$57k/year' clause on main is replaced by this text when the stack merges.
Business-model work order §3, in the ordered shape: the situation (one customer, the pile), the mission sentence - the cost of compliance shouldn't determine who gets to compete - what our piece does and does not do (evidence and validated crypto FOR your program; never makes you compliant), the Compliance tier and its nouns, and verify-everything- free-first ending on the test we invite. No claims beyond what the cache does today; the evidence links point at RELEASING, SECURITY (including its not-yet-proven statements) and the requirements matrix. Linked from the Compliance column and the footer; added to the sitemap. Co-authored-by: FosterStack Admin <317177128+fosterstack-admin@users.noreply.github.com>
fosterstack-admin
force-pushed
the
copy/restore-pricing-and-wedge
branch
from
September 12, 2026 18:01
75dd917 to
2288ee1
Compare
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.
What happened: the stack merged out of order on Sep 12 — #10 squash-merged to main at 16:32, then #12 merged at 16:54 into the already-merged
phase3/www-claimsbranch and #13 at 17:01 intobm/pricing. Their content never reached main.This PR rebases that already-cold-read, already-approved content onto main:
/regulated/wedge page + sitemap entry — Wedge page: for teams entering regulated markets #13.Verified: no $57k, dependency-cache sentence present, Compliance column present, no "npm cache"/"Node cache" vocabulary, both pages parse, allowlist passes.
Merge order suggestion: #15 first (minimal register fix), then this.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Jahm7QG8cVw7zcGeZV6Vet