chore(landing): describe the Analyst Operator, not text-to-Cypher - #346
Merged
Conversation
The console's agent answers from curated statements, documents, memory, and the Cypher it writes when nothing curated fits; the API renamed it analyst (robosystems #1308). The pricing FAQ and the platform overview still introduced it as Text-to-Cypher.
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.
Summary
Two places on the marketing site still introduced the console's agent as "Text-to-Cypher" / "AI generates Cypher queries". The agent answers from curated financial statements, documents, memory, and the Cypher it writes when nothing curated fits, and the API now registers it as
analyst(robosystems #1308). This names it the Analyst Operator where the old framing appeared.Changes
src/app/(landing)/pricing/content.tsx— "What are credits used for?" FAQ: the first of the two agents is now "the Analyst Operator, which answers a plain-English question from your graph — live statements, documents, memory, and the Cypher it writes when nothing curated fits — and shows the query behind it". The account-mapping half and the credits mechanics are unchanged.src/components/platform/FinancialServices.tsx— "Research via AI" step: "AI generates Cypher queries against 8,000+ public company SEC filings" → "the Analyst Operator answers from 8,000+ public company SEC filings".Left alone on purpose: the lines describing the console's output ("answers backed by the data and the generated Cypher", the Generated Cypher panel in
ConsoleDemo,platform/content.tsx's "it generates the Cypher, runs it, and answers with a narrative") — those describe what the console shows, which is still true. Copy only; no logic, routes, or data changes.Deploy Notes
None — static copy, no environment or infrastructure changes. Safe to deploy independently of the API release; the name is accurate today (the console auto-selects the operator and never sent the old name).
Testing
npm run test:all(test → format → lint:fix → typecheck → cf-lint): 389 tests passed across 47 files, all checks clean. Pre-commit hook ran the same set.