Skip to content

docs(decide): name Laya as the second decide provider - #1807

Merged
murdore merged 1 commit into
releasefrom
docs/laya-launch-messaging
Sep 26, 2026
Merged

murdore merged 1 commit into
releasefrom
docs/laya-launch-messaging

Conversation

@murdore

@murdore murdore commented Sep 26, 2026

Copy link
Copy Markdown
Contributor

Pull Request

Description

What does this PR do?

Names Laya as the second decide provider everywhere the README and docs describe decide, and adds a README highlight for it next to the TypeSafe one: what it is (Convai Innovations' Apache-2.0 open-weights model), how to use it (LAYA_API_KEY + LAYA_BASE_URL, or credentials.laya in the SDK config or per call; no built-in endpoint), when it fits (short states — about 768 tokens on the default checkpoint), and where NeuroLink uses it (the same built-in decide consumers, TypeSafe first when both are configured).

Related Issues

Relates to #1789 (Laya merged as the second decision provider, shipped in 12.26.0).

Type of Change

  • Documentation update

Motivation and Context

Since 12.26.0 the README and several docs pages were wrong: they said TypeSafe Jev is the only (or sole, or first-and-only) decide provider — "TypeSafe Jev alone serves decide", "the only provider serving decide", "the single provider of the 40 that does". Nothing outside docs/getting-started/providers/laya.md mentioned Laya.

  • Fixed in: README.md, docs/index.md, docs/features/index.md, docs/getting-started/provider-setup.md, docs/getting-started/providers/index.md, docs/getting-started/providers/typesafe.md, docs/reference/faq.md, docs/skills/neurolink-guide/providers.md, docs/about/nervous-system-model.md, and the docs-site FAQ in docs-site/src/pages/index.tsx.
  • The README's tool-support tally was recounted from PROVIDER_DESCRIPTORS (30 native, 3 model-dependent, 9 none).
  • The README's ~400ms / ~$0.00002 figures are now attributed to Jev, since they are Jev measurements.
  • Sentences this diff touches no longer carry a total provider count: with Laya added, their "40" no longer matched the enumeration in the same sentence. Totals in sentences this PR does not touch are left alone.

How Has This Been Tested?

  • pnpm run format:check — clean.
  • pnpm --dir docs-site run build twice on the rebased tree — docs-site/static/search-index.json byte-identical across both runs and equal to the committed file.
  • pnpm --dir docs-site run test:search-index-reproducibility — PASS.
  • Pre-commit hook (check, validate:all, lint, commit-message validation) and pre-push hook — pass.
  • An independent review pass checked every added claim against src/lib/providers/laya.ts, systemOneDecision.ts and providerDescriptors.ts, recounted the tally, and grepped for remaining "only decide provider" claims.

No code changes.

The README and docs still described TypeSafe Jev as the only decide
provider. Laya merged as the second one in #1789 (9ded25d,
v12.26.0), but nothing outside docs/getting-started/providers/laya.md
said so.

Updates every "only"/"first"/"sole" decide-provider claim across
README.md, docs/index.md, docs/features/index.md,
docs/getting-started/provider-setup.md,
docs/getting-started/providers/index.md,
docs/getting-started/providers/typesafe.md, docs/reference/faq.md,
docs/skills/neurolink-guide/providers.md, docs/about/nervous-system-model.md
and the docs-site FAQ and provider list in docs-site/src/pages/index.tsx,
and adds a README highlight for Laya (Apache-2.0, open-weights,
self-hosted via LAYA_API_KEY/LAYA_BASE_URL, TypeSafe first when both
are configured) alongside the existing TypeSafe one. The README's
latency and cost figures are now attributed to Jev.

Sentences this diff touches no longer carry a total provider count:
with Laya added, their "40" no longer matched their own enumeration.
Totals in sentences it does not touch are left for a separate pass.

docs-site/static/search-index.json is regenerated from the changes
above and was byte-identical across two docs-site builds.
@coderabbitai

coderabbitai Bot commented Sep 26, 2026

Copy link
Copy Markdown

Warning

Review limit reached

Next included review available in 44 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 2 included reviews currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Repository: juspay/neurolink/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 6a1c58e2-df18-4fed-9bee-b9bd6d9f6f59

📥 Commits

Reviewing files that changed from the base of the PR and between 8fc9088 and f2387f4.

📒 Files selected for processing (11)
  • README.md
  • docs-site/src/pages/index.tsx
  • docs-site/static/search-index.json
  • docs/about/nervous-system-model.md
  • docs/features/index.md
  • docs/getting-started/provider-setup.md
  • docs/getting-started/providers/index.md
  • docs/getting-started/providers/typesafe.md
  • docs/index.md
  • docs/reference/faq.md
  • docs/skills/neurolink-guide/providers.md

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

Copy link
Copy Markdown
Contributor

✅ Single Commit Policy - COMPLIANT

Status: Policy requirements met • 1 commit • Valid format • Ready for merge

📊 View validation details

📝 Commit Details

  • Hash: f2387f414185404856cda5ce4fc396798d5c67a6
  • Message: docs(decide): name Laya as the second decide provider
  • Author: Sachin Sharma

✅ Validation Results

  • Single commit requirement met
  • No merge commits in branch
  • Semantic commit message format verified
  • Ready for squash merge to release branch

🤖 Automated validation by NeuroLink Single Commit Enforcement

@github-actions

Copy link
Copy Markdown
Contributor

Documentation Validation Results

🚀 Documentation validation passed!

Check Status Result
Frontmatter Validation ✅ Passed
TypeScript Check ✅ Passed
Build ✅ Passed
Link Validation ✅ Passed

📦 Build artifact uploaded successfully. Ready for deployment preview.

Commit: 347f80f73ce63edb94db7e989f612b067a849ea2 | Workflow: View logs

@Tara-ag Tara-ag left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving this docs pass: Laya provider messaging is consistent across the sections this diff touches, and the author transparently documented the deferred count updates. Non-blocking note on remaining "40 providers" strings on lines outside the diff (see inline).

"Azure Speech",
"OpenAI TTS",
"TypeSafe",
"Laya",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MINOR — intended as a non-blocking note; the author's rationale is accepted.

Adding the Laya chip here makes the inconsistency on this same rendered page one click easier to hit: the provider grid now enumerates 23 names, while the byte-identical (unmodified) copy elsewhere in this file still says 40:

  • QUICK_LINKS SDK Guide description — "Unified API for 40 providers"
  • routing card — "Unified API for 40 AI providers"
  • <Layout description="...from 40 providers...">

The commit message transparently documents that only sentences the diff touches must drop their counts, and sentences it does not touch are deferred — I accept that scoping. But docs/features/index.md's "Platform Capabilities" / "AI Provider Integration" tables (both un-touched) also still assert 40.

Suggested change
"Laya",
"Laya",

No code change required; if you want to fold the remaining count out before merge, the three index.tsx strings and the two features/index.md table rows above are the complete set (verified against base 8fc9088 → head f2387f4). Leaving them for the stated follow-up pass is fine.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in bae3755: the hardcoded provider counts are gone. index.tsx (SDK Guide card, routing card, Layout description) and docs/features/index.md now say supported providers or many AI providers instead of 40.

@Tara-ag

Tara-ag commented Sep 26, 2026

Copy link
Copy Markdown
Contributor

APPROVE — A disciplined, well-scoped docs pass: the commit message transparently scopes count updates to only the sentences the diff touches and defers the rest, and Laya messaging is consistent across every section that this diff actually edits.

Findings

Severity Location Description
MINOR docs-site/src/pages/index.tsx:30 Provider grid now enumerates 23 names while byte-identical un-touched strings elsewhere on the same page (QUICK_LINKS, routing card, <Layout>) and the docs/features/index.md tables still assert "40 providers". Non-blocking; leaving for the author's stated follow-up pass is fine.

What was checked and found clean

  • Consistency of the new Laya messaging — README.md, docs/getting-started/provider-setup.md, docs/getting-started/providers/index.md, docs/getting-started/providers/typesafe.md, docs/reference/faq.md, docs/skills/neurolink-guide/providers.md, docs/about/nervous-system-model.md, and the docs/features/index.md sections this diff touches all name Laya coherently as the second decide provider.
  • No code churn — the change is docs-only (11 files, all .md / docs-site source / search index); no src/lib/**, types, providers, or SDK surface touched, so backward-compat (rule 5) and the provider registry (rule 1) are untouched.
  • Commit conventions — single conventional-commit-message commit with a required scope, no merge commits (CI's single-commit check passed).
  • Docs build — frontmatter, TS check, build, and link validation all green (CI).
  • Count consistency — the author-provided count of 23 enumerated providers in the grid was spot-checked and holds; the diff-scoped count removals are internally consistent with the enumerations they appear alongside.

No CRITICAL or MAJOR findings. No secrets, no provider code, no runtime impact.

@murdore
murdore merged commit a88ca3e into release Sep 26, 2026
30 checks passed
@murdore
murdore deleted the docs/laya-launch-messaging branch September 26, 2026 18:13
@github-actions

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 12.28.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants