docs: rename carbide/forge → NICo in documentation and design materials#1974
Open
shayan1995 wants to merge 1 commit into
Open
docs: rename carbide/forge → NICo in documentation and design materials#1974shayan1995 wants to merge 1 commit into
shayan1995 wants to merge 1 commit into
Conversation
Collaborator
|
This looks OK from a docs perspective. I assume that in most of these places the docs don't match the code or the artifact names, so this will be updated in subsequent PRs? |
shayan1995
force-pushed
the
feat/rename-docs
branch
2 times, most recently
from
25e8ed1 to
08bf313
Compare
Contributor
Author
|
@ajf yes the name changes is coming in a subsequent PR. |
Contributor
I assume that "name changes" means code here (or manifests, or both)? The above was a little ambiguous to me, just want to be certain. |
shayan1995
force-pushed
the
feat/rename-docs
branch
from
08bf313 to
173de2a
Compare
Apply the carbide/forge → NICo rename across documentation only: top-level markdown (AGENTS, CONTRIBUTING, README, STYLE_GUIDE), per-crate README.md / DEVELOPMENT.md, and the full docs/ tree (architecture, design, playbooks, manuals, getting-started, static assets). File-name renames for carbide-* / forge_* static assets are included. Substitutions applied (regex, ordered so PascalCase wins before brand-casing): CARBIDE -> NICO FORGE -> NICO Carbide(?=[A-Z]) -> Nico (PascalCase identifier prefix) Forge(?=[A-Z]) -> Nico Carbide -> NICo (brand-casing standalone) Forge -> NICo carbide -> nico forge -> nico Scope intentionally excludes test metric fixtures (crates/**/tests/**/*.txt and crates/**/fixtures/**/*.txt). Those are pinned-output comparisons against live metrics emitted by production code, so they must be renamed together with the agent/api source rename — they ride along with the code branch instead of docs. Out of scope (covered by other rename branches): helm/, lints/, rest-api/, .github/, Cargo.toml, crates/**/*.rs.
shayan1995
force-pushed
the
feat/rename-docs
branch
from
173de2a to
e9792d2
Compare
ajf
approved these changes
May 28, 2026
Coco-Ben
reviewed
May 28, 2026
| - `nicocli` installed (`make nico-cli` from the infra-controller-rest repo) and reachable on `$PATH`. | ||
|
|
||
| > **Note on CLI naming**: Older docs reference `carbidecli` (built via `make carbide-cli`). It's the same source under a previous name. This guide uses `nicocli` (built via `make nico-cli`) consistently. | ||
| > **Note on CLI naming**: Older docs reference `nicocli` (built via `make nico-cli`). It's the same source under a previous name. This guide uses `nicocli` (built via `make nico-cli`) consistently. |
Contributor
There was a problem hiding this comment.
This doesn't make sense with the rename :-) We could probably remove this note as part of the PR.
Coco-Ben
reviewed
May 28, 2026
| ### NICo Metadata Service | ||
|
|
||
| The Forge Metadata Service (FMDS) exposes instance metadata to tenants from the DPU. Tenants can use FMDS to retrieve information such as the Machine ID and boot or operating system metadata for their instance. FMDS runs on the DPU rather than on the host, so its responses are trusted independently of the host OS. | ||
| The NICo Metadata Service (FMDS) exposes instance metadata to tenants from the DPU. Tenants can use FMDS to retrieve information such as the Machine ID and boot or operating system metadata for their instance. FMDS runs on the DPU rather than on the host, so its responses are trusted independently of the host OS. |
Contributor
There was a problem hiding this comment.
Probably change "FDMS" acronym to "MDS".
Coco-Ben
reviewed
May 28, 2026
| This glossary focuses on NICo-specific concepts: terms that only make sense in the context of the NICo platform. Where a term has a general industry definition but carries additional NICo-specific meaning, this glossary explains the NICo-specific part. | ||
|
|
||
| <Note> You will encounter references to Forge, Carbide, and BMM in source code, CLI tool names, protobuf definitions, OpenAPI text, Helm charts, and image names. These were internal NVIDIA project names that preceded the current NICo branding. The documentation should use NICo names for product concepts, but many implementation artifacts still use legacy names such as `carbide-*`, `forge-*`, and `FORGE_*`. When this glossary references an artifact, role string, metric namespace, or configuration key, it preserves the name used by that interface.</Note> | ||
| <Note> You will encounter references to NICo, NICo, and BMM in source code, CLI tool names, protobuf definitions, OpenAPI text, Helm charts, and image names. These were internal NVIDIA project names that preceded the current NICo branding. The documentation should use NICo names for product concepts, but many implementation artifacts still use legacy names such as `nico-*`, `nico-*`, and `NICO_*`. When this glossary references an artifact, role string, metric namespace, or configuration key, it preserves the name used by that interface.</Note> |
Contributor
There was a problem hiding this comment.
Similar comment to above. You could probably remove this note.
Coco-Ben
reviewed
May 28, 2026
| NVIDIA Cloud Partner. In NICo docs, NCP usually refers to an infrastructure provider operating NICo-managed environments for tenant workloads. | ||
|
|
||
| ### Carbide | ||
| ### NICo |
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
4 participants
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.
Description
Apply the carbide/forge → NICo rename across documentation files: top-level markdown (AGENTS, CONTRIBUTING, README, STYLE_GUIDE), crate-level READMEs and DEVELOPMENT.md, metrics fixture files, and docs/ (architecture, design, playbooks, manuals, getting-started, static assets). File-name renames for carbide-* / forge_* static assets are included.
Type of Change
Related Issues (Optional)
Breaking Changes
Testing
Additional Notes
Scope: docs/, root .md, crates//README.md, crates//DEVELOPMENT.md, crates//tests//*.txt metrics fixtures. Out of scope (covered by other rename branches): helm/, lints/, rest-api/, .github/, Cargo.toml, crates//*.rs.