Repository navigation
fix(site): scope anomaly detection to what shipped and finish the pricing metadata - #598
Merged
Merged
Conversation
…cing metadata The 2026-10 sweep stripped "Forensic anomaly detection" from /pricing on the ruling that the roadmaps are authoritative. The site's own /changelog records a shipped deny-cluster anomaly alert (0.3.0: "one-click deny-cluster drill-down from the anomaly alert"), so the capability was real and the strip was the outlier. Restored at the scope that shipped: - "Deny-cluster anomaly alerting" on Business+ and Enterprise, plus a matching comparison-grid row and a mention in the Business+ FAQ - the JSON-LD feature list in landing-page/src/lib/schemas.ts - both roadmaps now defer only "Advanced anomaly detection beyond deny-cluster alerting and shadow-agent heuristics" Also from the same audit: - the pricing JSON-LD offers carried three of five tiers; Business+ ($599) and Enterprise (custom pricing, priceSpecification minPrice $1,500 from the minimum the FAQ already publishes) are added - landing-page/src/components/Pricing.tsx deleted: dead code that nothing imported, and it still sold SSO/SCIM and On-premise/VPC deployment - AGENTS.md records that Current Stage and pricing claims describe the platform repo, with the two drift patterns to check when editing them Verified: tsc --noEmit clean, next build compiled successfully, test:local-services 4 pass 0 fail, test:local-site 1 pass 0 fail, ruff check and ruff format --check clean, 233 passed, pillar check clean. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.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
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
The four follow-ups from the #597 audit.
Anomaly detection scoped to what actually shipped
#597 stripped
Forensic anomaly detectionfrom/pricingon the ruling that the roadmaps are authoritative. But the site's own/changelogrecords a shipped deny-cluster anomaly alert (0.3.0: "one-click deny-cluster drill-down from the anomaly alert"), so the capability was real and the strip was the outlier. Restored at the scope that shipped:Deny-cluster anomaly alertingon Business+ and Enterprise, a matching comparison-grid row, and a mention in the Business+ FAQlib/schemas.tsAdvanced anomaly detection beyond deny-cluster alerting and shadow-agent heuristicsThe four sitewide spots that already described anomaly detection (
home-content.tsx:32,about/page.tsx:255,forensics/page.tsx:115,industries/healthcare/page.tsx:72) are left as written, since the capability does ship.Pricing JSON-LD offers completed
offerscarried three of five tiers. Added Business+ at $599 and Enterprise as custom pricing (priceSpecificationwithminPriceof $1,500, the figure the FAQ already publishes). If you would rather not publish a starting number for Enterprise, drop thepriceSpecificationand leave that offer unpriced.Dead pricing component deleted
landing-page/src/components/Pricing.tsx, 643 lines, had zero references anywhere underlanding-page, and still soldBasic SSO,SAML / SCIMandOn-premise / VPC deploymentplus the SSO comparison row. Removing it takes a stale copy of the pricing page out of the tree.Claims provenance recorded
AGENTS.mdgains a section: the Current Stage lists and the pricing table assert what the private platform repo ships; this repo can verify only the CLI, the SDKs, the CPEX plugin, the published docs and the workflows; reconcile against the platform repo before editing rather than inferring from silence here. It names the two drift patterns this sweep found.The per-claim reconciliation table lives in
private/claims-reconciliation.md, which is gitignored so it is not in this PR: every live claim with whether this repo can verify it and where to check, every roadmap item with its state and evidence, and a four-step re-sweep procedure.Verification
npx tsc --noEmit: exit 0npx next build:Compiled successfully in 8.9s, exit 0npm run test:local-services: 4 pass, 0 failnpm run test:local-site: 1 pass, 0 failruff check .:All checks passed!ruff format --check .:55 files already formattedpytest -v:233 passed in 1.24sscripts/check-pillar-consistency.sh: exit 0Notes
Public-facing copy, so per
AGENTS.mdthis hands back for your read before merge. Enterprise pricing in structured data is the one judgment call worth a second look. The CHANGELOG entry carries no PR number yet; a follow-up commit adds it.