docs: publish enterprise readiness and admin capability guidance#5372
docs: publish enterprise readiness and admin capability guidance#5372miyoungc wants to merge 1 commit into
Conversation
Add docs/reference/enterprise-readiness.mdx classifying NemoClaw support boundaries and admin/control-plane capabilities by current support state, with workarounds, field-conversation wording, and links to tracked issues. Wire the page into the Reference section of both the OpenClaw and Hermes guide variants. Closes #4631 Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
PR Review AdvisorFindings: 0 needs attention, 1 worth checking, 0 nice ideas Review findings🛠️ Needs attention
🔎 Worth checking
🌱 Nice ideas
This is an automated advisory review. A human maintainer must make the final merge decision. |
E2E Advisor RecommendationRequired E2E: None Full advisor summaryE2E Recommendation AdvisorFailed: Could not parse JSON from advisor output; see /home/runner/work/NemoClaw/NemoClaw/artifacts/e2e-advisor/e2e-advisor-raw-output.txt |
Vitest E2E Scenario RecommendationRequired Vitest E2E scenarios: None Full Vitest E2E advisor summaryVitest E2E Scenario AdvisorFailed: Could not parse JSON from advisor output; see /home/runner/work/NemoClaw/NemoClaw/artifacts/e2e-advisor/e2e-scenario-advisor-raw-output.txt |
|
🌿 Preview your docs: https://nvidia-preview-pr-5372.docs.buildwithfern.com/nemoclaw |
2 participants
Summary
Adds an enterprise readiness and admin capability reference for NemoClaw so field teams and enterprise evaluators get a consistent answer for what is supported today, what is manual or admin-only, what is platform or partner-owned, and what is roadmap-only. This replaces inferring readiness from individual bug fixes with a single classified reference, and wires the page into the Reference section of both guide variants.
Related Issue
Closes #4631
Changes
docs/reference/enterprise-readiness.mdxwith a status vocabulary, a support-boundaries ownership table, an enterprise readiness matrix by capability area, an admin/control-plane capability classification table, known limitations and workarounds, field/customer conversation wording, and an ownership/maintenance section.nemoclaw <name> rebuildafter upgrading nemoclaw version #5202, OpenClaw version upgrade/attachment flexibility #2217, Brev GPU E2E fails at OpenShell Docker bridge gateway reachability #3959, [Brev][nemoclaw-image] Expose non-CPU Launchable variants for one-click GPU deploys #3365) and cross-reference the platform support matrix issue docs(platform): publish launch claims and platform support matrix #4630.docs/index.yml.$$nemoclawand<AgentOnly>blocks so the shared page renders correctly per variant; generated variant pages underdocs/_build/remain gitignored.Type of Change
Verification
npx prek run --all-filespassesnpm testpassesnpm run docsbuilds without warnings (doc changes only)Signed-off-by: Miyoung Choi miyoungc@nvidia.com