Repository navigation
feat(front): position the site as the live rules engine for AI agents - #242
Merged
Merged
Conversation
Home hero, Replaces/Keeps, Where it sits, the annotated agent-loop code, capability statements and the scope line follow the approved positioning. The loop is labelled as the upcoming SDK (subscribe/claim); the declarations block runs on today's Python SDK. Meta, OG text, nav, CTA banners, compare pages and the benchmark post say the same category; the benchmark numbers are unchanged and labelled as a recursive-query result.
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.
Intent
Rework the site so every page says the approved category: The live rules engine for AI agents, with the h1 "Take the rules out of your prompts." and the bold line "Your agents act on what's true now." Source: the gtm-tagline report, sections 2, 3, 4.2, 4.4, 4.6 and 9, with the challenger's factual fixes applied.
What changed
Home (
front/app/page.tsx)subscribe(),claim(),.any()) is labelled upcoming Python SDK. The declarations are labelled runs on today's Python SDK, using today's negation form~t.tool.in_(KillSwitch.tool).Shared pieces: site title, meta and OG description; the nav adds "What it replaces" and "Compare"; footer links and tagline; all six CTA banners; compare index metadata and subtitle; compare detail descriptions.
Content: the category sentence in the three compare pages, the docs index, the LangGraph and voice-article intros and the LangChain sample. The benchmark post gets a framing note. The vector comparison cell now reads "6.83ms in the recursive benchmark". All benchmark numbers are unchanged (6.83 ms, 11.3 s, 1,652x).
Challenger fixes applied
claimed_bycolumns; TTL locks follow with leases in a later release.kg.whyis not shown as working today.Not in this PR, because it is outside the site: the category string in
Cargo.toml,docs/README.md, the server's--helpbanner and the repository README.Verification
cd front && npm ci && npm run build: passes, and all pages are exported.dist/: quickstart, websocket-api, ingestion, persistence, deployment, python-sdk, langgraph, langchain, verified-completions, the benchmark and voice posts, compare, commercial, docs, and the anchors#replaces,#where,#howand#start. feat(protocol): share evaluations across standing queries that differ only in bound constants, and cache their plans #232 returns 200.[]; late ETA[['ORD-4821','SHP-9']]; kill switch[]; switch lifted[['ORD-4821','SHP-9']].scrollWidth == clientWidth(375) on the home page, so nothing scrolls the page sideways. Code scrolls inside its own block. Screenshots were taken at 375 px and 1280 px.