[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-nvidia-doca-firefly":3,"mdc-a4qh58-key":31,"related-org-nvidia-doca-firefly":1719,"related-repo-nvidia-doca-firefly":1880},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":20,"repoUrl":21,"updatedAt":22,"license":23,"forks":24,"topics":25,"repo":26,"sourceUrl":29,"mdContent":30},"doca-firefly","operate DOCA Firefly PTP services","Use this skill when the user is operating the DOCA Firefly Service container on BlueField — picking the four PTP configuration axes (role \u002F profile \u002F domain \u002F interface), wiring the BlueField PHC + host follower + consumer workload pairing, deciding whether PTP-grade time is even needed (vs. chrony \u002F NTP), or debugging a Firefly deployment where PTP isn't syncing or the host clock isn't following. Trigger even when the user does not explicitly mention \"DOCA Firefly\" or \"PTP\" — typical implicit phrasings include \"container green but PTP never advances past LISTENING\", \"Firefly says synced but the host clock still drifts\", \"sync acquired but offset is tens of microseconds\", \"my Rivermax SMPTE workload needs PTP\", or \"is chrony good enough\". Refuse and route elsewhere for installing DOCA, host-side chrony \u002F ptp4l config bodies, PTP topology \u002F boundary-clock design, building DOCA apps that read the disciplined PHC, or other DOCA services (DMS, Flow-Inspector, HBN) — those belong to other skills.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},"nvidia","NVIDIA","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fnvidia.png",[12,16,17],{"name":13,"slug":14,"type":15},"Hardware","hardware","tag",{"name":9,"slug":8,"type":15},{"name":18,"slug":19,"type":15},"Engineering","engineering",2473,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fskills","2026-07-30T05:28:29.409761","Apache-2.0",281,[],{"repoUrl":21,"stars":20,"forks":24,"topics":27,"description":28},[],"AI agent skills published by NVIDIA","https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fskills\u002Ftree\u002FHEAD\u002Fskills\u002Fdoca-firefly","---\nlicense: Apache-2.0\nname: doca-firefly\ndescription: >\n  Use this skill when the user is operating the DOCA Firefly Service\n  container on BlueField — picking the four PTP configuration axes\n  (role \u002F profile \u002F domain \u002F interface), wiring the BlueField PHC +\n  host follower + consumer workload pairing, deciding whether\n  PTP-grade time is even needed (vs. chrony \u002F NTP), or debugging a\n  Firefly deployment where PTP isn't syncing or the host clock isn't\n  following. Trigger even when the user does not explicitly mention\n  \"DOCA Firefly\" or \"PTP\" — typical implicit phrasings include\n  \"container green but PTP never advances past LISTENING\", \"Firefly\n  says synced but the host clock still drifts\", \"sync acquired but\n  offset is tens of microseconds\", \"my Rivermax SMPTE workload needs\n  PTP\", or \"is chrony good enough\". Refuse and route elsewhere for\n  installing DOCA, host-side chrony \u002F ptp4l config bodies, PTP\n  topology \u002F boundary-clock design, building DOCA apps that read the\n  disciplined PHC, or other DOCA services (DMS, Flow-Inspector, HBN)\n  — those belong to other skills.\nmetadata:\n  kind: service\ncompatibility: >\n  BlueField-Arm-only DOCA service container; pulled from NVIDIA NGC\n  and started under the BlueField OS container runtime. Host-side\n  install is irrelevant. Requires a reachable PTP master (or runs as\n  the master itself) and a PTP-aware network path; the host-side\n  time follower (chrony \u002F ptp4l \u002F phc2sys reading the BlueField PHC)\n  is also operator-owned.\n---\n\n# DOCA Firefly Service\n\n> **Subsystem inventory (Run-12 correction, verified Run-13).**\n> DOCA Firefly is NOT just \"a PTP daemon.\" The shipped\n> `doca_firefly.yaml` exposes **six** PTP-stack subsystems via\n> environment variables, each with its own `*_STATE`,\n> `*_CONFIG_FILE`, and (where relevant) `*_INTERFACE` \u002F\n> `*_DEVICE` knobs (the count is six because the PTP Monitor\n> subsystem ships an internal `phc2sys` monitor client that is\n> distinct from the standalone PHC2SYS subsystem — both ship in\n> the same container image):\n>\n> 1. **PTP** (`PTP_STATE`, `PTP_INTERFACE`, `PTP_CONFIG_FILE`) —\n>    the `ptp4l` daemon (or master, depending on profile) that\n>    drives the BlueField PHC.\n> 2. **PTP Monitor** (`MONITOR_STATE`, `MONITOR_CONFIG_FILE`,\n>    `MONITOR_CLIENT_TYPE`, `MONITOR_CLIENT_PHC2SYS_INTERFACE`,\n>    `MONITOR_CLIENT_CONNECTION_TIMEOUT`) — the monitor server +\n>    client surface; the **internal `phc2sys` monitor client**\n>    (`MONITOR_CLIENT_TYPE=phc2sys`) is a real subsystem inside\n>    Firefly, not just a host-side concern.\n> 3. **PHC2SYS** (`PHC2SYS_STATE`, `PHC2SYS_ARGS`,\n>    `PHC2SYS_CONFIG_FILE`) — the **container-internal** `phc2sys`\n>    instance; the bundle previously framed `phc2sys` as\n>    host-only, which is wrong.\n> 4. **PPS** (`PPS_STATE`, `PPS_DEVICE`) — the Pulse-Per-Second\n>    output (with the additional `enable_while_running` and\n>    `do_nothing` states beyond plain enable\u002Fdisable).\n> 5. **SyncE** (`SYNCE_STATE`, `SYNCE_INTERFACE`,\n>    `SYNCE_CONFIG_FILE`) — Synchronous Ethernet frequency\n>    distribution; orthogonal to PTP.\n> 6. **Firefly Servo** (`SERVO_STATE`, `SERVO_CONFIG_FILE`) —\n>    the proprietary Firefly servo loop (alternative to the\n>    upstream linuxptp servo).\n>\n> The valid `PROFILE` values are exactly **`default` \u002F `media` \u002F\n> `telco-l2` \u002F `custom`** (per `doca_firefly.yaml` comments) —\n> the agent must not invent additional values. Subsystems configured\n> as `defined_by_profile` are controlled by the active `PROFILE`.\n>\n> Configuration-override env vars follow the pattern\n> `CONF_\u003CSUBSYSTEM>_\u003Csection>_\u003Ckey>` (e.g.\n> `CONF_PTP_global_priority1`, `CONF_SYNCE_global_backend`,\n> `CONF_MONITOR_global_telemetry_export`); these are the\n> documented surface for overriding individual config keys\n> without shipping a full custom config file.\n>\n> **Configuration hierarchy:** the mounted Firefly config file is\n> mandatory and owns the primary PTP axes (role, profile, domain,\n> interface, and transport). `CONF_\u003CSUBSYSTEM>_\u003Csection>_\u003Ckey>`\n> variables are optional, documented per-key overrides of that file;\n> they are not a second standalone configuration model.\n\n**Where to start:** This skill is for *operating* the DOCA Firefly\nService container, not for *linking against* a library. Firefly is\nthe **PTP \u002F PHC2SYS \u002F PPS \u002F SyncE \u002F Servo \u002F Monitor** stack that\ndrives and observes the BlueField PTP Hardware Clock (PHC); it is\n*not* the host-side time follower, *not* the consumer workload, and\n*not* a programming surface. If the user wants to *deploy* the\ncontainer, open [`TASKS.md`](TASKS.md) and start at\n[`## configure`](TASKS.md#configure). If the question is *what shape\nof service is Firefly and what PTP roles \u002F profiles does it speak*,\nstart at [`CAPABILITIES.md`](CAPABILITIES.md). If DOCA is not installed\non the BlueField yet, route to\n[`doca-setup`](..\u002F..\u002Fdoca-setup\u002FSKILL.md) first. If the user's\nreal question is *\"I have a Rivermax SMPTE workload and the docs say I\nneed PTP\"*, the right pairing is this skill **plus**\n[`doca-rmax`](..\u002F..\u002Flibs\u002Fdoca-rmax\u002FSKILL.md) — Firefly disciplines\nthe PHC; Rivermax reads the disciplined time.\n\n## Example questions this skill answers well\n\nThe CLASSES of Firefly questions this skill is built to answer, each\nwith one worked example. The class is the load-bearing piece; the\nworked example is one instance.\n\n- **\"Do I actually need Firefly, or is NTP \u002F chrony good enough?\"** —\n  worked example: *\"my distributed app is fine on chrony today; is\n  there a reason to add PTP?\"*. Answered by the PTP-vs-NTP path-\n  selection rule in\n  [`CAPABILITIES.md ## Safety policy`](CAPABILITIES.md#safety-policy)\n  + the env-prep checklist in\n  [`TASKS.md ## configure`](TASKS.md#configure).\n- **\"What four PTP configuration axes do I have to decide before\n  starting the container?\"** — worked example: *\"a SMPTE ST 2110\n  broadcast plant that wants Firefly in slave role on the wire-side\n  port\"*. Answered by the four-axis configuration table in\n  [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes)\n  + the PTP-config step in\n  [`TASKS.md ## configure`](TASKS.md#configure).\n- **\"Firefly's container is running but the host's time isn't\n  following — what did I miss?\"** — worked example: *\"`ptp4l` \u002F\n  Firefly says it's locked but `chronyc tracking` on the host shows\n  drift\"*. Answered by the END-TO-END time-sync discipline in\n  [`CAPABILITIES.md ## Safety policy`](CAPABILITIES.md#safety-policy)\n  + the host-follower step in\n  [`TASKS.md ## configure`](TASKS.md#configure).\n- **\"PTP locks but the offset \u002F jitter is way past spec — what's\n  wrong with the path?\"** — worked example: *\"sync acquired but offset\n  is in the tens of microseconds\"*. Answered by the PTP-aware-path\n  rule in\n  [`CAPABILITIES.md ## Safety policy`](CAPABILITIES.md#safety-policy)\n  + the layered debug ladder in\n  [`TASKS.md ## debug`](TASKS.md#debug).\n- **\"How does Firefly pair with a Rivermax SMPTE workload?\"** —\n  worked example: *\"SMPTE ST 2110 video sender that needs to be PTP-\n  locked\"*. Answered by the Rivermax-pairing rule in\n  [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes)\n  + the pairing step in\n  [`TASKS.md ## configure`](TASKS.md#configure), which routes the\n  Rivermax side to\n  [`doca-rmax`](..\u002F..\u002Flibs\u002Fdoca-rmax\u002FSKILL.md) and refuses to\n  collapse the two services into one.\n- **\"My Firefly container starts but PTP never reaches\n  `SLAVE` \u002F `MASTER` state — was it role, domain, profile, or\n  interface?\"** — worked example: *\"container green but the\n  ports-state output never advances past `LISTENING`\"*. Answered by\n  the four-axis-mismatch rule in\n  [`CAPABILITIES.md ## Error taxonomy`](CAPABILITIES.md#error-taxonomy)\n  + the layered ladder in\n  [`TASKS.md ## debug`](TASKS.md#debug).\n\n## Audience\n\nThis skill serves **external operators and platform teams who deploy\nthe DOCA Firefly Service container** to provide PTP-grade time\nsynchronization to time-sensitive workloads on BlueField + the host\nbehind it. Concretely: people running the Firefly container on\nBlueField Arm, choosing its PTP role \u002F profile \u002F domain \u002F interface\nfrom the public Firefly guide, wiring the host-side follower (chrony\nwith the PHC source, or `ptp4l` reading the PHC) so the host clock\ntracks the BlueField PHC, and validating the end-to-end discipline\n  before scaling a Rivermax, 5G UPF, financial-trading, or distributed-\ndatabase workload that depends on it.\n\nIt is **not** for NVIDIA developers contributing to Firefly itself,\nand it is **not** a programming guide for *building applications on\ntop of* DOCA libraries (that is\n[`doca-programming-guide`](..\u002F..\u002Fdoca-programming-guide\u002FSKILL.md)\nplus the matching `libs\u002F\u003Clibrary>` skill). Firefly is a **service**,\nnot a library: the operator runs a container and configures PTP via\nthe documented config surface; they do not link against a\n`libfirefly.so` to write their own program.\n\n**Path selection up front.** Use Firefly when sub-microsecond,\nPTP-grade time precision is required on BlueField AND the host (SMPTE\nST 2110 broadcast workloads layered on Rivermax, 5G UPF time\nrequirements, distributed systems that need PTP-grade time, anything\nwhere NTP \u002F chrony jitter is not tight enough). Do **not** reach for\nFirefly when NTP \u002F chrony already meets the workload's time-precision\nbudget, when no PTP-aware switching \u002F boundary-clock infrastructure\nexists in the path, or when pure software-side time precision is\nsufficient — in those cases the correct answer is to keep the host's\nexisting chrony \u002F NTP setup and route the agent away from Firefly,\nnot to deploy it speculatively.\n\n## When to load this skill\n\nLoad this skill when the user is doing **hands-on Firefly deployment\nwork** on a BlueField where DOCA is already installed. Concretely:\n\n- Deciding *whether* Firefly is the right answer for the user's\n  time-precision requirement (vs. keeping NTP \u002F chrony on the host).\n- Deploying the Firefly container on BlueField Arm — choosing image\n  source per the public DOCA Firefly Service Guide, mounting the\n  Firefly config, and starting \u002F stopping the container.\n- Choosing the four PTP configuration axes — PTP role (master \u002F\n  slave \u002F boundary clock \u002F transparent clock), profile (the\n  `PROFILE` env var accepts EXACTLY `default` \u002F `media` \u002F\n  `telco-l2` \u002F `custom` per `services\u002Ffirefly\u002Fdoca_firefly.yaml`;\n  these map onto industry PTP profile names: `default` → IEEE 1588,\n  `media` → SMPTE 2059-2, `telco-l2` → G.8275.1 only (G.8275.2\n  corresponds to the separate `telco-l3` config, reached via\n  `custom`) — do NOT put the industry names directly into the env\n  var), domain number,\n  network interface — for the user's deployment.\n- Wiring the host-side follower so the host clock tracks the\n  BlueField PHC (chrony with the PHC source, or `ptp4l` \u002F\n  `phc2sys` reading the PHC) — without this step the host clock\n  does NOT follow the Firefly-disciplined PHC, regardless of how\n  cleanly Firefly comes up.\n- Pairing Firefly with a time-sensitive consumer workload (Rivermax\n  SMPTE, 5G UPF, finance, distributed databases) and validating\n  the end-to-end discipline.\n- Reading the Firefly container's logs, the PHC offset, the\n  ports-state output, or any other documented observability surface\n  to confirm PTP is locked.\n- Debugging a Firefly deployment where the container is healthy but\n  PTP is not syncing, or PTP is syncing but the host clock is not\n  following, or sync is up but jitter is past spec.\n\nDo **not** load this skill for general DOCA orientation, install of\nDOCA itself, library-API questions, or non-PTP time topics. For\nthose, route via\n[`doca-public-knowledge-map`](..\u002F..\u002Fdoca-public-knowledge-map\u002FSKILL.md),\n[`doca-setup`](..\u002F..\u002Fdoca-setup\u002FSKILL.md), or the matching\n`libs\u002F\u003Clibrary>` skill.\n\n## What this skill provides\n\nThis is a **thin loader**. Substantive material lives in two\ncompanion files:\n\n- `CAPABILITIES.md` — Firefly's architecture (container that drives\n  the BlueField PHC and speaks PTP on the wire), the four PTP\n  configuration axes (role \u002F profile \u002F domain \u002F interface, with\n  transport as a fifth knob), the deployment shape (container on\n  BlueField Arm per the public Container Deployment Guide), the\n  pairing surface (Rivermax + host-side time-sync follower), the\n  observability surface (container logs + PHC offset + ports state),\n  the error taxonomy (four-axis-mismatch \u002F host-follower \u002F PTP-aware-\n  path \u002F container-runtime), and the safety policy (PTP-vs-NTP path\n  selection, END-TO-END discipline, smoke-before-scale).\n- `TASKS.md` — step-by-step workflows for the in-scope Firefly\n  verbs: `configure`, `build`, `modify`, `run`, `test`, `debug`,\n  plus a `Deferred task verbs` block routing out-of-scope questions\n  and a `Command appendix` of recurring commands.\n\nThe skill assumes a BlueField where DOCA is already installed and\nthe operator has the privileges the public Firefly Service Guide\nexpects to pull, run, and configure containers on BlueField Arm.\nIt does not cover installing DOCA — that path goes through\n[`doca-setup`](..\u002F..\u002Fdoca-setup\u002FSKILL.md).\n\n## What this skill deliberately does not ship\n\nThis skill is **agent guidance**, not a templates or sample-config\nbundle. To keep the boundary clean, it deliberately does not contain —\nand pull requests should not add:\n\n- **Pre-baked Firefly configuration files** (full PTP config blocks,\n  ready-to-run role \u002F profile \u002F domain bundles) intended to be\n  copy-pasted into production. PTP configuration is deployment-\n  specific (per the user's profile, domain plan, interface naming,\n  and upstream PTP topology); the safe answer for an external\n  operator is to derive the config from the public Firefly Service\n  Guide against their own deployment. The agent's job is to\n  prescribe the *procedure* and the *four-axis decision*, not to\n  ship a config the user might run unmodified.\n- **Container image names, tags, or registry paths.** The\n  authoritative image source is the public DOCA Firefly Service\n  Guide reachable through\n  [`doca-public-knowledge-map ## DOCA services`](..\u002F..\u002Fdoca-public-knowledge-map\u002FSKILL.md#doca-services);\n  Firefly's image tag is version-bound and changes between DOCA\n  releases. Inventing or memorizing a tag is the canonical\n  hallucination failure mode for a service skill.\n- **Host-side chrony stanzas or `ptp4l` \u002F `phc2sys` config files.**\n  Those are host-environment-specific and live on the host, not\n  inside the Firefly container. The skill names *that* the\n  host-side follower must be wired and *what its source must be*\n  (the BlueField PHC); the chrony \u002F `ptp4l` config bodies belong\n  to the host operator and to upstream Linux PTP documentation.\n- **A `samples\u002F`, `templates\u002F`, or `reference\u002F` subtree** of any\n  kind. A mock or incomplete artifact in this skill's tree, even\n  one labeled *\"reference\"*, is misleading: operators will read it\n  as production-ready.\n\n## Loading order\n\n1. Read this `SKILL.md` first to confirm the user's question is in\n   scope **and** that Firefly is the right answer at all (vs. keeping\n   NTP \u002F chrony on the host).\n2. **For Firefly's deployment shape, the four PTP configuration\n   axes, the Rivermax + host-follower pairing surface, the error\n   taxonomy, the observability surface, and the END-TO-END safety\n   policy, see [CAPABILITIES.md](CAPABILITIES.md).**\n3. **For step-by-step workflows — configure, build, modify, run,\n   test, debug — see [TASKS.md](TASKS.md).**\n\n## Related skills\n\n- [`doca-public-knowledge-map`](..\u002F..\u002Fdoca-public-knowledge-map\u002FSKILL.md)\n  — the routing table to the public DOCA Firefly Service Guide and\n  the rest of the public DOCA documentation set. The Firefly URL is\n  listed under\n  [`## DOCA services`](..\u002F..\u002Fdoca-public-knowledge-map\u002FSKILL.md#doca-services).\n- [`doca-setup`](..\u002F..\u002Fdoca-setup\u002FSKILL.md) — env preparation and\n  install verification on the BlueField where the Firefly container\n  will run, including the *I have no install yet* path via the\n  public NGC DOCA container. This skill assumes its preconditions\n  are satisfied on BlueField Arm.\n- [`doca-version`](..\u002F..\u002Fdoca-version\u002FSKILL.md) — canonical DOCA\n  version-handling rules. Firefly's container tag is version-bound;\n  this skill's `## Version compatibility` cross-links the four-way\n  match rule and adds the container-tag-lags-host-package overlay.\n- [`doca-structured-tools-contract`](..\u002F..\u002Fdoca-structured-tools-contract\u002FSKILL.md) —\n  the bundle's structured-tools precedence rule (detect \u002F prefer \u002F\n  fall back \u002F report). The Command appendix in [TASKS.md](TASKS.md)\n  honors this contract.\n- [`doca-programming-guide`](..\u002F..\u002Fdoca-programming-guide\u002FSKILL.md)\n  — general DOCA patterns. Firefly is service-shaped not library-\n  shaped, so the build \u002F modify \u002F first-app pattern there does not\n  apply directly, but the cross-library debug discipline (frontend-\n  before-backend, env-before-program) remains useful when Firefly\n  reports an error that originated in the container runtime or in\n  a DOCA library it called.\n- [`doca-rmax`](..\u002F..\u002Flibs\u002Fdoca-rmax\u002FSKILL.md) — the canonical\n  paired workload. SMPTE ST 2110 Rivermax streams depend on a\n  Firefly-disciplined PHC; Firefly is the time-source side and\n  Rivermax is the timing-precise data-plane side. The two skills\n  load together for any broadcast-style deployment, and they do\n  NOT collapse into one another — Firefly does not stream media;\n  Rivermax does not discipline the PHC.\n- [`doca-dms`](..\u002Fdoca-dms\u002FSKILL.md) — sibling service skill. The\n  agent reading both skills should see the same service-skill shape\n  (container, BlueField Arm, deployment pattern, smoke-before-scale,\n  env preconditions, config schema) layered on top of a different\n  per-service domain (DMS = device management via gNMI \u002F gNOI;\n  Firefly = time synchronization via PTP).\n- [`doca-debug`](..\u002F..\u002Fdoca-debug\u002FSKILL.md) — the cross-cutting\n  debug ladder (install \u002F version \u002F build \u002F link \u002F runtime \u002F\n  program \u002F driver). Firefly-specific debug (PTP not syncing,\n  host clock not following, jitter past spec) overlays on top of\n  that ladder.\n",{"data":32,"body":36},{"license":23,"name":4,"description":6,"metadata":33,"compatibility":35},{"kind":34},"service","BlueField-Arm-only DOCA service container; pulled from NVIDIA NGC and started under the BlueField OS container runtime. Host-side install is irrelevant. Requires a reachable PTP master (or runs as the master itself) and a PTP-aware network path; the host-side time follower (chrony \u002F ptp4l \u002F phc2sys reading the BlueField PHC) is also operator-owned.\n",{"type":37,"children":38},"root",[39,48,500,636,643,648,957,963,982,1040,1056,1062,1074,1208,1247,1253,1265,1347,1361,1367,1379,1512,1518,1567,1573],{"type":40,"tag":41,"props":42,"children":44},"element","h1",{"id":43},"doca-firefly-service",[45],{"type":46,"value":47},"text","DOCA Firefly Service",{"type":40,"tag":49,"props":50,"children":51},"blockquote",{},[52,120,380,448,483],{"type":40,"tag":53,"props":54,"children":55},"p",{},[56,62,64,71,73,78,80,86,88,94,96,102,104,110,112,118],{"type":40,"tag":57,"props":58,"children":59},"strong",{},[60],{"type":46,"value":61},"Subsystem inventory (Run-12 correction, verified Run-13).",{"type":46,"value":63},"\nDOCA Firefly is NOT just \"a PTP daemon.\" The shipped\n",{"type":40,"tag":65,"props":66,"children":68},"code",{"className":67},[],[69],{"type":46,"value":70},"doca_firefly.yaml",{"type":46,"value":72}," exposes ",{"type":40,"tag":57,"props":74,"children":75},{},[76],{"type":46,"value":77},"six",{"type":46,"value":79}," PTP-stack subsystems via\nenvironment variables, each with its own ",{"type":40,"tag":65,"props":81,"children":83},{"className":82},[],[84],{"type":46,"value":85},"*_STATE",{"type":46,"value":87},",\n",{"type":40,"tag":65,"props":89,"children":91},{"className":90},[],[92],{"type":46,"value":93},"*_CONFIG_FILE",{"type":46,"value":95},", and (where relevant) ",{"type":40,"tag":65,"props":97,"children":99},{"className":98},[],[100],{"type":46,"value":101},"*_INTERFACE",{"type":46,"value":103}," \u002F\n",{"type":40,"tag":65,"props":105,"children":107},{"className":106},[],[108],{"type":46,"value":109},"*_DEVICE",{"type":46,"value":111}," knobs (the count is six because the PTP Monitor\nsubsystem ships an internal ",{"type":40,"tag":65,"props":113,"children":115},{"className":114},[],[116],{"type":46,"value":117},"phc2sys",{"type":46,"value":119}," monitor client that is\ndistinct from the standalone PHC2SYS subsystem — both ship in\nthe same container image):",{"type":40,"tag":121,"props":122,"children":123},"ol",{},[124,166,233,285,325,356],{"type":40,"tag":125,"props":126,"children":127},"li",{},[128,133,135,141,143,149,150,156,158,164],{"type":40,"tag":57,"props":129,"children":130},{},[131],{"type":46,"value":132},"PTP",{"type":46,"value":134}," (",{"type":40,"tag":65,"props":136,"children":138},{"className":137},[],[139],{"type":46,"value":140},"PTP_STATE",{"type":46,"value":142},", ",{"type":40,"tag":65,"props":144,"children":146},{"className":145},[],[147],{"type":46,"value":148},"PTP_INTERFACE",{"type":46,"value":142},{"type":40,"tag":65,"props":151,"children":153},{"className":152},[],[154],{"type":46,"value":155},"PTP_CONFIG_FILE",{"type":46,"value":157},") —\nthe ",{"type":40,"tag":65,"props":159,"children":161},{"className":160},[],[162],{"type":46,"value":163},"ptp4l",{"type":46,"value":165}," daemon (or master, depending on profile) that\ndrives the BlueField PHC.",{"type":40,"tag":125,"props":167,"children":168},{},[169,174,175,181,182,188,189,195,196,202,203,209,211,223,225,231],{"type":40,"tag":57,"props":170,"children":171},{},[172],{"type":46,"value":173},"PTP Monitor",{"type":46,"value":134},{"type":40,"tag":65,"props":176,"children":178},{"className":177},[],[179],{"type":46,"value":180},"MONITOR_STATE",{"type":46,"value":142},{"type":40,"tag":65,"props":183,"children":185},{"className":184},[],[186],{"type":46,"value":187},"MONITOR_CONFIG_FILE",{"type":46,"value":87},{"type":40,"tag":65,"props":190,"children":192},{"className":191},[],[193],{"type":46,"value":194},"MONITOR_CLIENT_TYPE",{"type":46,"value":142},{"type":40,"tag":65,"props":197,"children":199},{"className":198},[],[200],{"type":46,"value":201},"MONITOR_CLIENT_PHC2SYS_INTERFACE",{"type":46,"value":87},{"type":40,"tag":65,"props":204,"children":206},{"className":205},[],[207],{"type":46,"value":208},"MONITOR_CLIENT_CONNECTION_TIMEOUT",{"type":46,"value":210},") — the monitor server +\nclient surface; the ",{"type":40,"tag":57,"props":212,"children":213},{},[214,216,221],{"type":46,"value":215},"internal ",{"type":40,"tag":65,"props":217,"children":219},{"className":218},[],[220],{"type":46,"value":117},{"type":46,"value":222}," monitor client",{"type":46,"value":224},"\n(",{"type":40,"tag":65,"props":226,"children":228},{"className":227},[],[229],{"type":46,"value":230},"MONITOR_CLIENT_TYPE=phc2sys",{"type":46,"value":232},") is a real subsystem inside\nFirefly, not just a host-side concern.",{"type":40,"tag":125,"props":234,"children":235},{},[236,241,242,248,249,255,256,262,264,269,271,276,278,283],{"type":40,"tag":57,"props":237,"children":238},{},[239],{"type":46,"value":240},"PHC2SYS",{"type":46,"value":134},{"type":40,"tag":65,"props":243,"children":245},{"className":244},[],[246],{"type":46,"value":247},"PHC2SYS_STATE",{"type":46,"value":142},{"type":40,"tag":65,"props":250,"children":252},{"className":251},[],[253],{"type":46,"value":254},"PHC2SYS_ARGS",{"type":46,"value":87},{"type":40,"tag":65,"props":257,"children":259},{"className":258},[],[260],{"type":46,"value":261},"PHC2SYS_CONFIG_FILE",{"type":46,"value":263},") — the ",{"type":40,"tag":57,"props":265,"children":266},{},[267],{"type":46,"value":268},"container-internal",{"type":46,"value":270}," ",{"type":40,"tag":65,"props":272,"children":274},{"className":273},[],[275],{"type":46,"value":117},{"type":46,"value":277},"\ninstance; the bundle previously framed ",{"type":40,"tag":65,"props":279,"children":281},{"className":280},[],[282],{"type":46,"value":117},{"type":46,"value":284}," as\nhost-only, which is wrong.",{"type":40,"tag":125,"props":286,"children":287},{},[288,293,294,300,301,307,309,315,317,323],{"type":40,"tag":57,"props":289,"children":290},{},[291],{"type":46,"value":292},"PPS",{"type":46,"value":134},{"type":40,"tag":65,"props":295,"children":297},{"className":296},[],[298],{"type":46,"value":299},"PPS_STATE",{"type":46,"value":142},{"type":40,"tag":65,"props":302,"children":304},{"className":303},[],[305],{"type":46,"value":306},"PPS_DEVICE",{"type":46,"value":308},") — the Pulse-Per-Second\noutput (with the additional ",{"type":40,"tag":65,"props":310,"children":312},{"className":311},[],[313],{"type":46,"value":314},"enable_while_running",{"type":46,"value":316}," and\n",{"type":40,"tag":65,"props":318,"children":320},{"className":319},[],[321],{"type":46,"value":322},"do_nothing",{"type":46,"value":324}," states beyond plain enable\u002Fdisable).",{"type":40,"tag":125,"props":326,"children":327},{},[328,333,334,340,341,347,348,354],{"type":40,"tag":57,"props":329,"children":330},{},[331],{"type":46,"value":332},"SyncE",{"type":46,"value":134},{"type":40,"tag":65,"props":335,"children":337},{"className":336},[],[338],{"type":46,"value":339},"SYNCE_STATE",{"type":46,"value":142},{"type":40,"tag":65,"props":342,"children":344},{"className":343},[],[345],{"type":46,"value":346},"SYNCE_INTERFACE",{"type":46,"value":87},{"type":40,"tag":65,"props":349,"children":351},{"className":350},[],[352],{"type":46,"value":353},"SYNCE_CONFIG_FILE",{"type":46,"value":355},") — Synchronous Ethernet frequency\ndistribution; orthogonal to PTP.",{"type":40,"tag":125,"props":357,"children":358},{},[359,364,365,371,372,378],{"type":40,"tag":57,"props":360,"children":361},{},[362],{"type":46,"value":363},"Firefly Servo",{"type":46,"value":134},{"type":40,"tag":65,"props":366,"children":368},{"className":367},[],[369],{"type":46,"value":370},"SERVO_STATE",{"type":46,"value":142},{"type":40,"tag":65,"props":373,"children":375},{"className":374},[],[376],{"type":46,"value":377},"SERVO_CONFIG_FILE",{"type":46,"value":379},") —\nthe proprietary Firefly servo loop (alternative to the\nupstream linuxptp servo).",{"type":40,"tag":53,"props":381,"children":382},{},[383,385,391,393,424,426,431,433,439,441,446],{"type":46,"value":384},"The valid ",{"type":40,"tag":65,"props":386,"children":388},{"className":387},[],[389],{"type":46,"value":390},"PROFILE",{"type":46,"value":392}," values are exactly ",{"type":40,"tag":57,"props":394,"children":395},{},[396,402,404,410,411,417,418],{"type":40,"tag":65,"props":397,"children":399},{"className":398},[],[400],{"type":46,"value":401},"default",{"type":46,"value":403}," \u002F ",{"type":40,"tag":65,"props":405,"children":407},{"className":406},[],[408],{"type":46,"value":409},"media",{"type":46,"value":103},{"type":40,"tag":65,"props":412,"children":414},{"className":413},[],[415],{"type":46,"value":416},"telco-l2",{"type":46,"value":403},{"type":40,"tag":65,"props":419,"children":421},{"className":420},[],[422],{"type":46,"value":423},"custom",{"type":46,"value":425}," (per ",{"type":40,"tag":65,"props":427,"children":429},{"className":428},[],[430],{"type":46,"value":70},{"type":46,"value":432}," comments) —\nthe agent must not invent additional values. Subsystems configured\nas ",{"type":40,"tag":65,"props":434,"children":436},{"className":435},[],[437],{"type":46,"value":438},"defined_by_profile",{"type":46,"value":440}," are controlled by the active ",{"type":40,"tag":65,"props":442,"children":444},{"className":443},[],[445],{"type":46,"value":390},{"type":46,"value":447},".",{"type":40,"tag":53,"props":449,"children":450},{},[451,453,459,461,467,468,474,475,481],{"type":46,"value":452},"Configuration-override env vars follow the pattern\n",{"type":40,"tag":65,"props":454,"children":456},{"className":455},[],[457],{"type":46,"value":458},"CONF_\u003CSUBSYSTEM>_\u003Csection>_\u003Ckey>",{"type":46,"value":460}," (e.g.\n",{"type":40,"tag":65,"props":462,"children":464},{"className":463},[],[465],{"type":46,"value":466},"CONF_PTP_global_priority1",{"type":46,"value":142},{"type":40,"tag":65,"props":469,"children":471},{"className":470},[],[472],{"type":46,"value":473},"CONF_SYNCE_global_backend",{"type":46,"value":87},{"type":40,"tag":65,"props":476,"children":478},{"className":477},[],[479],{"type":46,"value":480},"CONF_MONITOR_global_telemetry_export",{"type":46,"value":482},"); these are the\ndocumented surface for overriding individual config keys\nwithout shipping a full custom config file.",{"type":40,"tag":53,"props":484,"children":485},{},[486,491,493,498],{"type":40,"tag":57,"props":487,"children":488},{},[489],{"type":46,"value":490},"Configuration hierarchy:",{"type":46,"value":492}," the mounted Firefly config file is\nmandatory and owns the primary PTP axes (role, profile, domain,\ninterface, and transport). ",{"type":40,"tag":65,"props":494,"children":496},{"className":495},[],[497],{"type":46,"value":458},{"type":46,"value":499},"\nvariables are optional, documented per-key overrides of that file;\nthey are not a second standalone configuration model.",{"type":40,"tag":53,"props":501,"children":502},{},[503,508,510,516,518,523,525,530,532,537,539,543,545,549,551,556,558,568,570,580,582,587,589,598,600,610,612,617,619,624,634],{"type":40,"tag":57,"props":504,"children":505},{},[506],{"type":46,"value":507},"Where to start:",{"type":46,"value":509}," This skill is for ",{"type":40,"tag":511,"props":512,"children":513},"em",{},[514],{"type":46,"value":515},"operating",{"type":46,"value":517}," the DOCA Firefly\nService container, not for ",{"type":40,"tag":511,"props":519,"children":520},{},[521],{"type":46,"value":522},"linking against",{"type":46,"value":524}," a library. Firefly is\nthe ",{"type":40,"tag":57,"props":526,"children":527},{},[528],{"type":46,"value":529},"PTP \u002F PHC2SYS \u002F PPS \u002F SyncE \u002F Servo \u002F Monitor",{"type":46,"value":531}," stack that\ndrives and observes the BlueField PTP Hardware Clock (PHC); it is\n",{"type":40,"tag":511,"props":533,"children":534},{},[535],{"type":46,"value":536},"not",{"type":46,"value":538}," the host-side time follower, ",{"type":40,"tag":511,"props":540,"children":541},{},[542],{"type":46,"value":536},{"type":46,"value":544}," the consumer workload, and\n",{"type":40,"tag":511,"props":546,"children":547},{},[548],{"type":46,"value":536},{"type":46,"value":550}," a programming surface. If the user wants to ",{"type":40,"tag":511,"props":552,"children":553},{},[554],{"type":46,"value":555},"deploy",{"type":46,"value":557}," the\ncontainer, open ",{"type":40,"tag":559,"props":560,"children":562},"a",{"href":561},"TASKS.md",[563],{"type":40,"tag":65,"props":564,"children":566},{"className":565},[],[567],{"type":46,"value":561},{"type":46,"value":569}," and start at\n",{"type":40,"tag":559,"props":571,"children":573},{"href":572},"TASKS.md#configure",[574],{"type":40,"tag":65,"props":575,"children":577},{"className":576},[],[578],{"type":46,"value":579},"## configure",{"type":46,"value":581},". If the question is ",{"type":40,"tag":511,"props":583,"children":584},{},[585],{"type":46,"value":586},"what shape\nof service is Firefly and what PTP roles \u002F profiles does it speak",{"type":46,"value":588},",\nstart at ",{"type":40,"tag":559,"props":590,"children":592},{"href":591},"CAPABILITIES.md",[593],{"type":40,"tag":65,"props":594,"children":596},{"className":595},[],[597],{"type":46,"value":591},{"type":46,"value":599},". If DOCA is not installed\non the BlueField yet, route to\n",{"type":40,"tag":559,"props":601,"children":603},{"href":602},"..\u002F..\u002Fdoca-setup\u002FSKILL.md",[604],{"type":40,"tag":65,"props":605,"children":607},{"className":606},[],[608],{"type":46,"value":609},"doca-setup",{"type":46,"value":611}," first. If the user's\nreal question is ",{"type":40,"tag":511,"props":613,"children":614},{},[615],{"type":46,"value":616},"\"I have a Rivermax SMPTE workload and the docs say I\nneed PTP\"",{"type":46,"value":618},", the right pairing is this skill ",{"type":40,"tag":57,"props":620,"children":621},{},[622],{"type":46,"value":623},"plus",{"type":40,"tag":559,"props":625,"children":627},{"href":626},"..\u002F..\u002Flibs\u002Fdoca-rmax\u002FSKILL.md",[628],{"type":40,"tag":65,"props":629,"children":631},{"className":630},[],[632],{"type":46,"value":633},"doca-rmax",{"type":46,"value":635}," — Firefly disciplines\nthe PHC; Rivermax reads the disciplined time.",{"type":40,"tag":637,"props":638,"children":640},"h2",{"id":639},"example-questions-this-skill-answers-well",[641],{"type":46,"value":642},"Example questions this skill answers well",{"type":40,"tag":53,"props":644,"children":645},{},[646],{"type":46,"value":647},"The CLASSES of Firefly questions this skill is built to answer, each\nwith one worked example. The class is the load-bearing piece; the\nworked example is one instance.",{"type":40,"tag":649,"props":650,"children":651},"ul",{},[652,697,741,797,840,892],{"type":40,"tag":125,"props":653,"children":654},{},[655,660,662,667,669,679],{"type":40,"tag":57,"props":656,"children":657},{},[658],{"type":46,"value":659},"\"Do I actually need Firefly, or is NTP \u002F chrony good enough?\"",{"type":46,"value":661}," —\nworked example: ",{"type":40,"tag":511,"props":663,"children":664},{},[665],{"type":46,"value":666},"\"my distributed app is fine on chrony today; is\nthere a reason to add PTP?\"",{"type":46,"value":668},". Answered by the PTP-vs-NTP path-\nselection rule in\n",{"type":40,"tag":559,"props":670,"children":672},{"href":671},"CAPABILITIES.md#safety-policy",[673],{"type":40,"tag":65,"props":674,"children":676},{"className":675},[],[677],{"type":46,"value":678},"CAPABILITIES.md ## Safety policy",{"type":40,"tag":649,"props":680,"children":681},{},[682],{"type":40,"tag":125,"props":683,"children":684},{},[685,687,696],{"type":46,"value":686},"the env-prep checklist in\n",{"type":40,"tag":559,"props":688,"children":689},{"href":572},[690],{"type":40,"tag":65,"props":691,"children":693},{"className":692},[],[694],{"type":46,"value":695},"TASKS.md ## configure",{"type":46,"value":447},{"type":40,"tag":125,"props":698,"children":699},{},[700,705,707,712,714,724],{"type":40,"tag":57,"props":701,"children":702},{},[703],{"type":46,"value":704},"\"What four PTP configuration axes do I have to decide before\nstarting the container?\"",{"type":46,"value":706}," — worked example: ",{"type":40,"tag":511,"props":708,"children":709},{},[710],{"type":46,"value":711},"\"a SMPTE ST 2110\nbroadcast plant that wants Firefly in slave role on the wire-side\nport\"",{"type":46,"value":713},". Answered by the four-axis configuration table in\n",{"type":40,"tag":559,"props":715,"children":717},{"href":716},"CAPABILITIES.md#capabilities-and-modes",[718],{"type":40,"tag":65,"props":719,"children":721},{"className":720},[],[722],{"type":46,"value":723},"CAPABILITIES.md ## Capabilities and modes",{"type":40,"tag":649,"props":725,"children":726},{},[727],{"type":40,"tag":125,"props":728,"children":729},{},[730,732,740],{"type":46,"value":731},"the PTP-config step in\n",{"type":40,"tag":559,"props":733,"children":734},{"href":572},[735],{"type":40,"tag":65,"props":736,"children":738},{"className":737},[],[739],{"type":46,"value":695},{"type":46,"value":447},{"type":40,"tag":125,"props":742,"children":743},{},[744,749,750,770,772,780],{"type":40,"tag":57,"props":745,"children":746},{},[747],{"type":46,"value":748},"\"Firefly's container is running but the host's time isn't\nfollowing — what did I miss?\"",{"type":46,"value":706},{"type":40,"tag":511,"props":751,"children":752},{},[753,755,760,762,768],{"type":46,"value":754},"\"",{"type":40,"tag":65,"props":756,"children":758},{"className":757},[],[759],{"type":46,"value":163},{"type":46,"value":761}," \u002F\nFirefly says it's locked but ",{"type":40,"tag":65,"props":763,"children":765},{"className":764},[],[766],{"type":46,"value":767},"chronyc tracking",{"type":46,"value":769}," on the host shows\ndrift\"",{"type":46,"value":771},". Answered by the END-TO-END time-sync discipline in\n",{"type":40,"tag":559,"props":773,"children":774},{"href":671},[775],{"type":40,"tag":65,"props":776,"children":778},{"className":777},[],[779],{"type":46,"value":678},{"type":40,"tag":649,"props":781,"children":782},{},[783],{"type":40,"tag":125,"props":784,"children":785},{},[786,788,796],{"type":46,"value":787},"the host-follower step in\n",{"type":40,"tag":559,"props":789,"children":790},{"href":572},[791],{"type":40,"tag":65,"props":792,"children":794},{"className":793},[],[795],{"type":46,"value":695},{"type":46,"value":447},{"type":40,"tag":125,"props":798,"children":799},{},[800,805,806,811,813,821],{"type":40,"tag":57,"props":801,"children":802},{},[803],{"type":46,"value":804},"\"PTP locks but the offset \u002F jitter is way past spec — what's\nwrong with the path?\"",{"type":46,"value":706},{"type":40,"tag":511,"props":807,"children":808},{},[809],{"type":46,"value":810},"\"sync acquired but offset\nis in the tens of microseconds\"",{"type":46,"value":812},". Answered by the PTP-aware-path\nrule in\n",{"type":40,"tag":559,"props":814,"children":815},{"href":671},[816],{"type":40,"tag":65,"props":817,"children":819},{"className":818},[],[820],{"type":46,"value":678},{"type":40,"tag":649,"props":822,"children":823},{},[824],{"type":40,"tag":125,"props":825,"children":826},{},[827,829,839],{"type":46,"value":828},"the layered debug ladder in\n",{"type":40,"tag":559,"props":830,"children":832},{"href":831},"TASKS.md#debug",[833],{"type":40,"tag":65,"props":834,"children":836},{"className":835},[],[837],{"type":46,"value":838},"TASKS.md ## debug",{"type":46,"value":447},{"type":40,"tag":125,"props":841,"children":842},{},[843,848,849,854,856,864],{"type":40,"tag":57,"props":844,"children":845},{},[846],{"type":46,"value":847},"\"How does Firefly pair with a Rivermax SMPTE workload?\"",{"type":46,"value":661},{"type":40,"tag":511,"props":850,"children":851},{},[852],{"type":46,"value":853},"\"SMPTE ST 2110 video sender that needs to be PTP-\nlocked\"",{"type":46,"value":855},". Answered by the Rivermax-pairing rule in\n",{"type":40,"tag":559,"props":857,"children":858},{"href":716},[859],{"type":40,"tag":65,"props":860,"children":862},{"className":861},[],[863],{"type":46,"value":723},{"type":40,"tag":649,"props":865,"children":866},{},[867],{"type":40,"tag":125,"props":868,"children":869},{},[870,872,880,882,890],{"type":46,"value":871},"the pairing step in\n",{"type":40,"tag":559,"props":873,"children":874},{"href":572},[875],{"type":40,"tag":65,"props":876,"children":878},{"className":877},[],[879],{"type":46,"value":695},{"type":46,"value":881},", which routes the\nRivermax side to\n",{"type":40,"tag":559,"props":883,"children":884},{"href":626},[885],{"type":40,"tag":65,"props":886,"children":888},{"className":887},[],[889],{"type":46,"value":633},{"type":46,"value":891}," and refuses to\ncollapse the two services into one.",{"type":40,"tag":125,"props":893,"children":894},{},[895,915,916,928,930,940],{"type":40,"tag":57,"props":896,"children":897},{},[898,900,906,907,913],{"type":46,"value":899},"\"My Firefly container starts but PTP never reaches\n",{"type":40,"tag":65,"props":901,"children":903},{"className":902},[],[904],{"type":46,"value":905},"SLAVE",{"type":46,"value":403},{"type":40,"tag":65,"props":908,"children":910},{"className":909},[],[911],{"type":46,"value":912},"MASTER",{"type":46,"value":914}," state — was it role, domain, profile, or\ninterface?\"",{"type":46,"value":706},{"type":40,"tag":511,"props":917,"children":918},{},[919,921,927],{"type":46,"value":920},"\"container green but the\nports-state output never advances past ",{"type":40,"tag":65,"props":922,"children":924},{"className":923},[],[925],{"type":46,"value":926},"LISTENING",{"type":46,"value":754},{"type":46,"value":929},". Answered by\nthe four-axis-mismatch rule in\n",{"type":40,"tag":559,"props":931,"children":933},{"href":932},"CAPABILITIES.md#error-taxonomy",[934],{"type":40,"tag":65,"props":935,"children":937},{"className":936},[],[938],{"type":46,"value":939},"CAPABILITIES.md ## Error taxonomy",{"type":40,"tag":649,"props":941,"children":942},{},[943],{"type":40,"tag":125,"props":944,"children":945},{},[946,948,956],{"type":46,"value":947},"the layered ladder in\n",{"type":40,"tag":559,"props":949,"children":950},{"href":831},[951],{"type":40,"tag":65,"props":952,"children":954},{"className":953},[],[955],{"type":46,"value":838},{"type":46,"value":447},{"type":40,"tag":637,"props":958,"children":960},{"id":959},"audience",[961],{"type":46,"value":962},"Audience",{"type":40,"tag":53,"props":964,"children":965},{},[966,968,973,975,980],{"type":46,"value":967},"This skill serves ",{"type":40,"tag":57,"props":969,"children":970},{},[971],{"type":46,"value":972},"external operators and platform teams who deploy\nthe DOCA Firefly Service container",{"type":46,"value":974}," to provide PTP-grade time\nsynchronization to time-sensitive workloads on BlueField + the host\nbehind it. Concretely: people running the Firefly container on\nBlueField Arm, choosing its PTP role \u002F profile \u002F domain \u002F interface\nfrom the public Firefly guide, wiring the host-side follower (chrony\nwith the PHC source, or ",{"type":40,"tag":65,"props":976,"children":978},{"className":977},[],[979],{"type":46,"value":163},{"type":46,"value":981}," reading the PHC) so the host clock\ntracks the BlueField PHC, and validating the end-to-end discipline\nbefore scaling a Rivermax, 5G UPF, financial-trading, or distributed-\ndatabase workload that depends on it.",{"type":40,"tag":53,"props":983,"children":984},{},[985,987,991,993,997,999,1004,1006,1016,1018,1024,1026,1030,1032,1038],{"type":46,"value":986},"It is ",{"type":40,"tag":57,"props":988,"children":989},{},[990],{"type":46,"value":536},{"type":46,"value":992}," for NVIDIA developers contributing to Firefly itself,\nand it is ",{"type":40,"tag":57,"props":994,"children":995},{},[996],{"type":46,"value":536},{"type":46,"value":998}," a programming guide for ",{"type":40,"tag":511,"props":1000,"children":1001},{},[1002],{"type":46,"value":1003},"building applications on\ntop of",{"type":46,"value":1005}," DOCA libraries (that is\n",{"type":40,"tag":559,"props":1007,"children":1009},{"href":1008},"..\u002F..\u002Fdoca-programming-guide\u002FSKILL.md",[1010],{"type":40,"tag":65,"props":1011,"children":1013},{"className":1012},[],[1014],{"type":46,"value":1015},"doca-programming-guide",{"type":46,"value":1017},"\nplus the matching ",{"type":40,"tag":65,"props":1019,"children":1021},{"className":1020},[],[1022],{"type":46,"value":1023},"libs\u002F\u003Clibrary>",{"type":46,"value":1025}," skill). Firefly is a ",{"type":40,"tag":57,"props":1027,"children":1028},{},[1029],{"type":46,"value":34},{"type":46,"value":1031},",\nnot a library: the operator runs a container and configures PTP via\nthe documented config surface; they do not link against a\n",{"type":40,"tag":65,"props":1033,"children":1035},{"className":1034},[],[1036],{"type":46,"value":1037},"libfirefly.so",{"type":46,"value":1039}," to write their own program.",{"type":40,"tag":53,"props":1041,"children":1042},{},[1043,1048,1050,1054],{"type":40,"tag":57,"props":1044,"children":1045},{},[1046],{"type":46,"value":1047},"Path selection up front.",{"type":46,"value":1049}," Use Firefly when sub-microsecond,\nPTP-grade time precision is required on BlueField AND the host (SMPTE\nST 2110 broadcast workloads layered on Rivermax, 5G UPF time\nrequirements, distributed systems that need PTP-grade time, anything\nwhere NTP \u002F chrony jitter is not tight enough). Do ",{"type":40,"tag":57,"props":1051,"children":1052},{},[1053],{"type":46,"value":536},{"type":46,"value":1055}," reach for\nFirefly when NTP \u002F chrony already meets the workload's time-precision\nbudget, when no PTP-aware switching \u002F boundary-clock infrastructure\nexists in the path, or when pure software-side time precision is\nsufficient — in those cases the correct answer is to keep the host's\nexisting chrony \u002F NTP setup and route the agent away from Firefly,\nnot to deploy it speculatively.",{"type":40,"tag":637,"props":1057,"children":1059},{"id":1058},"when-to-load-this-skill",[1060],{"type":46,"value":1061},"When to load this skill",{"type":40,"tag":53,"props":1063,"children":1064},{},[1065,1067,1072],{"type":46,"value":1066},"Load this skill when the user is doing ",{"type":40,"tag":57,"props":1068,"children":1069},{},[1070],{"type":46,"value":1071},"hands-on Firefly deployment\nwork",{"type":46,"value":1073}," on a BlueField where DOCA is already installed. Concretely:",{"type":40,"tag":649,"props":1075,"children":1076},{},[1077,1089,1094,1175,1193,1198,1203],{"type":40,"tag":125,"props":1078,"children":1079},{},[1080,1082,1087],{"type":46,"value":1081},"Deciding ",{"type":40,"tag":511,"props":1083,"children":1084},{},[1085],{"type":46,"value":1086},"whether",{"type":46,"value":1088}," Firefly is the right answer for the user's\ntime-precision requirement (vs. keeping NTP \u002F chrony on the host).",{"type":40,"tag":125,"props":1090,"children":1091},{},[1092],{"type":46,"value":1093},"Deploying the Firefly container on BlueField Arm — choosing image\nsource per the public DOCA Firefly Service Guide, mounting the\nFirefly config, and starting \u002F stopping the container.",{"type":40,"tag":125,"props":1095,"children":1096},{},[1097,1099,1104,1106,1111,1112,1117,1118,1123,1124,1129,1131,1137,1139,1144,1146,1151,1153,1158,1160,1166,1168,1173],{"type":46,"value":1098},"Choosing the four PTP configuration axes — PTP role (master \u002F\nslave \u002F boundary clock \u002F transparent clock), profile (the\n",{"type":40,"tag":65,"props":1100,"children":1102},{"className":1101},[],[1103],{"type":46,"value":390},{"type":46,"value":1105}," env var accepts EXACTLY ",{"type":40,"tag":65,"props":1107,"children":1109},{"className":1108},[],[1110],{"type":46,"value":401},{"type":46,"value":403},{"type":40,"tag":65,"props":1113,"children":1115},{"className":1114},[],[1116],{"type":46,"value":409},{"type":46,"value":103},{"type":40,"tag":65,"props":1119,"children":1121},{"className":1120},[],[1122],{"type":46,"value":416},{"type":46,"value":403},{"type":40,"tag":65,"props":1125,"children":1127},{"className":1126},[],[1128],{"type":46,"value":423},{"type":46,"value":1130}," per ",{"type":40,"tag":65,"props":1132,"children":1134},{"className":1133},[],[1135],{"type":46,"value":1136},"services\u002Ffirefly\u002Fdoca_firefly.yaml",{"type":46,"value":1138},";\nthese map onto industry PTP profile names: ",{"type":40,"tag":65,"props":1140,"children":1142},{"className":1141},[],[1143],{"type":46,"value":401},{"type":46,"value":1145}," → IEEE 1588,\n",{"type":40,"tag":65,"props":1147,"children":1149},{"className":1148},[],[1150],{"type":46,"value":409},{"type":46,"value":1152}," → SMPTE 2059-2, ",{"type":40,"tag":65,"props":1154,"children":1156},{"className":1155},[],[1157],{"type":46,"value":416},{"type":46,"value":1159}," → G.8275.1 only (G.8275.2\ncorresponds to the separate ",{"type":40,"tag":65,"props":1161,"children":1163},{"className":1162},[],[1164],{"type":46,"value":1165},"telco-l3",{"type":46,"value":1167}," config, reached via\n",{"type":40,"tag":65,"props":1169,"children":1171},{"className":1170},[],[1172],{"type":46,"value":423},{"type":46,"value":1174},") — do NOT put the industry names directly into the env\nvar), domain number,\nnetwork interface — for the user's deployment.",{"type":40,"tag":125,"props":1176,"children":1177},{},[1178,1180,1185,1186,1191],{"type":46,"value":1179},"Wiring the host-side follower so the host clock tracks the\nBlueField PHC (chrony with the PHC source, or ",{"type":40,"tag":65,"props":1181,"children":1183},{"className":1182},[],[1184],{"type":46,"value":163},{"type":46,"value":103},{"type":40,"tag":65,"props":1187,"children":1189},{"className":1188},[],[1190],{"type":46,"value":117},{"type":46,"value":1192}," reading the PHC) — without this step the host clock\ndoes NOT follow the Firefly-disciplined PHC, regardless of how\ncleanly Firefly comes up.",{"type":40,"tag":125,"props":1194,"children":1195},{},[1196],{"type":46,"value":1197},"Pairing Firefly with a time-sensitive consumer workload (Rivermax\nSMPTE, 5G UPF, finance, distributed databases) and validating\nthe end-to-end discipline.",{"type":40,"tag":125,"props":1199,"children":1200},{},[1201],{"type":46,"value":1202},"Reading the Firefly container's logs, the PHC offset, the\nports-state output, or any other documented observability surface\nto confirm PTP is locked.",{"type":40,"tag":125,"props":1204,"children":1205},{},[1206],{"type":46,"value":1207},"Debugging a Firefly deployment where the container is healthy but\nPTP is not syncing, or PTP is syncing but the host clock is not\nfollowing, or sync is up but jitter is past spec.",{"type":40,"tag":53,"props":1209,"children":1210},{},[1211,1213,1217,1219,1229,1230,1238,1240,1245],{"type":46,"value":1212},"Do ",{"type":40,"tag":57,"props":1214,"children":1215},{},[1216],{"type":46,"value":536},{"type":46,"value":1218}," load this skill for general DOCA orientation, install of\nDOCA itself, library-API questions, or non-PTP time topics. For\nthose, route via\n",{"type":40,"tag":559,"props":1220,"children":1222},{"href":1221},"..\u002F..\u002Fdoca-public-knowledge-map\u002FSKILL.md",[1223],{"type":40,"tag":65,"props":1224,"children":1226},{"className":1225},[],[1227],{"type":46,"value":1228},"doca-public-knowledge-map",{"type":46,"value":87},{"type":40,"tag":559,"props":1231,"children":1232},{"href":602},[1233],{"type":40,"tag":65,"props":1234,"children":1236},{"className":1235},[],[1237],{"type":46,"value":609},{"type":46,"value":1239},", or the matching\n",{"type":40,"tag":65,"props":1241,"children":1243},{"className":1242},[],[1244],{"type":46,"value":1023},{"type":46,"value":1246}," skill.",{"type":40,"tag":637,"props":1248,"children":1250},{"id":1249},"what-this-skill-provides",[1251],{"type":46,"value":1252},"What this skill provides",{"type":40,"tag":53,"props":1254,"children":1255},{},[1256,1258,1263],{"type":46,"value":1257},"This is a ",{"type":40,"tag":57,"props":1259,"children":1260},{},[1261],{"type":46,"value":1262},"thin loader",{"type":46,"value":1264},". Substantive material lives in two\ncompanion files:",{"type":40,"tag":649,"props":1266,"children":1267},{},[1268,1278],{"type":40,"tag":125,"props":1269,"children":1270},{},[1271,1276],{"type":40,"tag":65,"props":1272,"children":1274},{"className":1273},[],[1275],{"type":46,"value":591},{"type":46,"value":1277}," — Firefly's architecture (container that drives\nthe BlueField PHC and speaks PTP on the wire), the four PTP\nconfiguration axes (role \u002F profile \u002F domain \u002F interface, with\ntransport as a fifth knob), the deployment shape (container on\nBlueField Arm per the public Container Deployment Guide), the\npairing surface (Rivermax + host-side time-sync follower), the\nobservability surface (container logs + PHC offset + ports state),\nthe error taxonomy (four-axis-mismatch \u002F host-follower \u002F PTP-aware-\npath \u002F container-runtime), and the safety policy (PTP-vs-NTP path\nselection, END-TO-END discipline, smoke-before-scale).",{"type":40,"tag":125,"props":1279,"children":1280},{},[1281,1286,1288,1294,1295,1301,1302,1308,1309,1315,1316,1322,1323,1329,1331,1337,1339,1345],{"type":40,"tag":65,"props":1282,"children":1284},{"className":1283},[],[1285],{"type":46,"value":561},{"type":46,"value":1287}," — step-by-step workflows for the in-scope Firefly\nverbs: ",{"type":40,"tag":65,"props":1289,"children":1291},{"className":1290},[],[1292],{"type":46,"value":1293},"configure",{"type":46,"value":142},{"type":40,"tag":65,"props":1296,"children":1298},{"className":1297},[],[1299],{"type":46,"value":1300},"build",{"type":46,"value":142},{"type":40,"tag":65,"props":1303,"children":1305},{"className":1304},[],[1306],{"type":46,"value":1307},"modify",{"type":46,"value":142},{"type":40,"tag":65,"props":1310,"children":1312},{"className":1311},[],[1313],{"type":46,"value":1314},"run",{"type":46,"value":142},{"type":40,"tag":65,"props":1317,"children":1319},{"className":1318},[],[1320],{"type":46,"value":1321},"test",{"type":46,"value":142},{"type":40,"tag":65,"props":1324,"children":1326},{"className":1325},[],[1327],{"type":46,"value":1328},"debug",{"type":46,"value":1330},",\nplus a ",{"type":40,"tag":65,"props":1332,"children":1334},{"className":1333},[],[1335],{"type":46,"value":1336},"Deferred task verbs",{"type":46,"value":1338}," block routing out-of-scope questions\nand a ",{"type":40,"tag":65,"props":1340,"children":1342},{"className":1341},[],[1343],{"type":46,"value":1344},"Command appendix",{"type":46,"value":1346}," of recurring commands.",{"type":40,"tag":53,"props":1348,"children":1349},{},[1350,1352,1360],{"type":46,"value":1351},"The skill assumes a BlueField where DOCA is already installed and\nthe operator has the privileges the public Firefly Service Guide\nexpects to pull, run, and configure containers on BlueField Arm.\nIt does not cover installing DOCA — that path goes through\n",{"type":40,"tag":559,"props":1353,"children":1354},{"href":602},[1355],{"type":40,"tag":65,"props":1356,"children":1358},{"className":1357},[],[1359],{"type":46,"value":609},{"type":46,"value":447},{"type":40,"tag":637,"props":1362,"children":1364},{"id":1363},"what-this-skill-deliberately-does-not-ship",[1365],{"type":46,"value":1366},"What this skill deliberately does not ship",{"type":40,"tag":53,"props":1368,"children":1369},{},[1370,1372,1377],{"type":46,"value":1371},"This skill is ",{"type":40,"tag":57,"props":1373,"children":1374},{},[1375],{"type":46,"value":1376},"agent guidance",{"type":46,"value":1378},", not a templates or sample-config\nbundle. To keep the boundary clean, it deliberately does not contain —\nand pull requests should not add:",{"type":40,"tag":649,"props":1380,"children":1381},{},[1382,1406,1428,1472],{"type":40,"tag":125,"props":1383,"children":1384},{},[1385,1390,1392,1397,1399,1404],{"type":40,"tag":57,"props":1386,"children":1387},{},[1388],{"type":46,"value":1389},"Pre-baked Firefly configuration files",{"type":46,"value":1391}," (full PTP config blocks,\nready-to-run role \u002F profile \u002F domain bundles) intended to be\ncopy-pasted into production. PTP configuration is deployment-\nspecific (per the user's profile, domain plan, interface naming,\nand upstream PTP topology); the safe answer for an external\noperator is to derive the config from the public Firefly Service\nGuide against their own deployment. The agent's job is to\nprescribe the ",{"type":40,"tag":511,"props":1393,"children":1394},{},[1395],{"type":46,"value":1396},"procedure",{"type":46,"value":1398}," and the ",{"type":40,"tag":511,"props":1400,"children":1401},{},[1402],{"type":46,"value":1403},"four-axis decision",{"type":46,"value":1405},", not to\nship a config the user might run unmodified.",{"type":40,"tag":125,"props":1407,"children":1408},{},[1409,1414,1416,1426],{"type":40,"tag":57,"props":1410,"children":1411},{},[1412],{"type":46,"value":1413},"Container image names, tags, or registry paths.",{"type":46,"value":1415}," The\nauthoritative image source is the public DOCA Firefly Service\nGuide reachable through\n",{"type":40,"tag":559,"props":1417,"children":1419},{"href":1418},"..\u002F..\u002Fdoca-public-knowledge-map\u002FSKILL.md#doca-services",[1420],{"type":40,"tag":65,"props":1421,"children":1423},{"className":1422},[],[1424],{"type":46,"value":1425},"doca-public-knowledge-map ## DOCA services",{"type":46,"value":1427},";\nFirefly's image tag is version-bound and changes between DOCA\nreleases. Inventing or memorizing a tag is the canonical\nhallucination failure mode for a service skill.",{"type":40,"tag":125,"props":1429,"children":1430},{},[1431,1449,1451,1456,1458,1463,1465,1470],{"type":40,"tag":57,"props":1432,"children":1433},{},[1434,1436,1441,1442,1447],{"type":46,"value":1435},"Host-side chrony stanzas or ",{"type":40,"tag":65,"props":1437,"children":1439},{"className":1438},[],[1440],{"type":46,"value":163},{"type":46,"value":403},{"type":40,"tag":65,"props":1443,"children":1445},{"className":1444},[],[1446],{"type":46,"value":117},{"type":46,"value":1448}," config files.",{"type":46,"value":1450},"\nThose are host-environment-specific and live on the host, not\ninside the Firefly container. The skill names ",{"type":40,"tag":511,"props":1452,"children":1453},{},[1454],{"type":46,"value":1455},"that",{"type":46,"value":1457}," the\nhost-side follower must be wired and ",{"type":40,"tag":511,"props":1459,"children":1460},{},[1461],{"type":46,"value":1462},"what its source must be",{"type":46,"value":1464},"\n(the BlueField PHC); the chrony \u002F ",{"type":40,"tag":65,"props":1466,"children":1468},{"className":1467},[],[1469],{"type":46,"value":163},{"type":46,"value":1471}," config bodies belong\nto the host operator and to upstream Linux PTP documentation.",{"type":40,"tag":125,"props":1473,"children":1474},{},[1475,1503,1505,1510],{"type":40,"tag":57,"props":1476,"children":1477},{},[1478,1480,1486,1487,1493,1495,1501],{"type":46,"value":1479},"A ",{"type":40,"tag":65,"props":1481,"children":1483},{"className":1482},[],[1484],{"type":46,"value":1485},"samples\u002F",{"type":46,"value":142},{"type":40,"tag":65,"props":1488,"children":1490},{"className":1489},[],[1491],{"type":46,"value":1492},"templates\u002F",{"type":46,"value":1494},", or ",{"type":40,"tag":65,"props":1496,"children":1498},{"className":1497},[],[1499],{"type":46,"value":1500},"reference\u002F",{"type":46,"value":1502}," subtree",{"type":46,"value":1504}," of any\nkind. A mock or incomplete artifact in this skill's tree, even\none labeled ",{"type":40,"tag":511,"props":1506,"children":1507},{},[1508],{"type":46,"value":1509},"\"reference\"",{"type":46,"value":1511},", is misleading: operators will read it\nas production-ready.",{"type":40,"tag":637,"props":1513,"children":1515},{"id":1514},"loading-order",[1516],{"type":46,"value":1517},"Loading order",{"type":40,"tag":121,"props":1519,"children":1520},{},[1521,1541,1554],{"type":40,"tag":125,"props":1522,"children":1523},{},[1524,1526,1532,1534,1539],{"type":46,"value":1525},"Read this ",{"type":40,"tag":65,"props":1527,"children":1529},{"className":1528},[],[1530],{"type":46,"value":1531},"SKILL.md",{"type":46,"value":1533}," first to confirm the user's question is in\nscope ",{"type":40,"tag":57,"props":1535,"children":1536},{},[1537],{"type":46,"value":1538},"and",{"type":46,"value":1540}," that Firefly is the right answer at all (vs. keeping\nNTP \u002F chrony on the host).",{"type":40,"tag":125,"props":1542,"children":1543},{},[1544],{"type":40,"tag":57,"props":1545,"children":1546},{},[1547,1549,1553],{"type":46,"value":1548},"For Firefly's deployment shape, the four PTP configuration\naxes, the Rivermax + host-follower pairing surface, the error\ntaxonomy, the observability surface, and the END-TO-END safety\npolicy, see ",{"type":40,"tag":559,"props":1550,"children":1551},{"href":591},[1552],{"type":46,"value":591},{"type":46,"value":447},{"type":40,"tag":125,"props":1555,"children":1556},{},[1557],{"type":40,"tag":57,"props":1558,"children":1559},{},[1560,1562,1566],{"type":46,"value":1561},"For step-by-step workflows — configure, build, modify, run,\ntest, debug — see ",{"type":40,"tag":559,"props":1563,"children":1564},{"href":561},[1565],{"type":46,"value":561},{"type":46,"value":447},{"type":40,"tag":637,"props":1568,"children":1570},{"id":1569},"related-skills",[1571],{"type":46,"value":1572},"Related skills",{"type":40,"tag":649,"props":1574,"children":1575},{},[1576,1599,1619,1642,1663,1676,1689,1704],{"type":40,"tag":125,"props":1577,"children":1578},{},[1579,1587,1589,1598],{"type":40,"tag":559,"props":1580,"children":1581},{"href":1221},[1582],{"type":40,"tag":65,"props":1583,"children":1585},{"className":1584},[],[1586],{"type":46,"value":1228},{"type":46,"value":1588},"\n— the routing table to the public DOCA Firefly Service Guide and\nthe rest of the public DOCA documentation set. The Firefly URL is\nlisted under\n",{"type":40,"tag":559,"props":1590,"children":1591},{"href":1418},[1592],{"type":40,"tag":65,"props":1593,"children":1595},{"className":1594},[],[1596],{"type":46,"value":1597},"## DOCA services",{"type":46,"value":447},{"type":40,"tag":125,"props":1600,"children":1601},{},[1602,1610,1612,1617],{"type":40,"tag":559,"props":1603,"children":1604},{"href":602},[1605],{"type":40,"tag":65,"props":1606,"children":1608},{"className":1607},[],[1609],{"type":46,"value":609},{"type":46,"value":1611}," — env preparation and\ninstall verification on the BlueField where the Firefly container\nwill run, including the ",{"type":40,"tag":511,"props":1613,"children":1614},{},[1615],{"type":46,"value":1616},"I have no install yet",{"type":46,"value":1618}," path via the\npublic NGC DOCA container. This skill assumes its preconditions\nare satisfied on BlueField Arm.",{"type":40,"tag":125,"props":1620,"children":1621},{},[1622,1632,1634,1640],{"type":40,"tag":559,"props":1623,"children":1625},{"href":1624},"..\u002F..\u002Fdoca-version\u002FSKILL.md",[1626],{"type":40,"tag":65,"props":1627,"children":1629},{"className":1628},[],[1630],{"type":46,"value":1631},"doca-version",{"type":46,"value":1633}," — canonical DOCA\nversion-handling rules. Firefly's container tag is version-bound;\nthis skill's ",{"type":40,"tag":65,"props":1635,"children":1637},{"className":1636},[],[1638],{"type":46,"value":1639},"## Version compatibility",{"type":46,"value":1641}," cross-links the four-way\nmatch rule and adds the container-tag-lags-host-package overlay.",{"type":40,"tag":125,"props":1643,"children":1644},{},[1645,1655,1657,1661],{"type":40,"tag":559,"props":1646,"children":1648},{"href":1647},"..\u002F..\u002Fdoca-structured-tools-contract\u002FSKILL.md",[1649],{"type":40,"tag":65,"props":1650,"children":1652},{"className":1651},[],[1653],{"type":46,"value":1654},"doca-structured-tools-contract",{"type":46,"value":1656}," —\nthe bundle's structured-tools precedence rule (detect \u002F prefer \u002F\nfall back \u002F report). The Command appendix in ",{"type":40,"tag":559,"props":1658,"children":1659},{"href":561},[1660],{"type":46,"value":561},{"type":46,"value":1662},"\nhonors this contract.",{"type":40,"tag":125,"props":1664,"children":1665},{},[1666,1674],{"type":40,"tag":559,"props":1667,"children":1668},{"href":1008},[1669],{"type":40,"tag":65,"props":1670,"children":1672},{"className":1671},[],[1673],{"type":46,"value":1015},{"type":46,"value":1675},"\n— general DOCA patterns. Firefly is service-shaped not library-\nshaped, so the build \u002F modify \u002F first-app pattern there does not\napply directly, but the cross-library debug discipline (frontend-\nbefore-backend, env-before-program) remains useful when Firefly\nreports an error that originated in the container runtime or in\na DOCA library it called.",{"type":40,"tag":125,"props":1677,"children":1678},{},[1679,1687],{"type":40,"tag":559,"props":1680,"children":1681},{"href":626},[1682],{"type":40,"tag":65,"props":1683,"children":1685},{"className":1684},[],[1686],{"type":46,"value":633},{"type":46,"value":1688}," — the canonical\npaired workload. SMPTE ST 2110 Rivermax streams depend on a\nFirefly-disciplined PHC; Firefly is the time-source side and\nRivermax is the timing-precise data-plane side. The two skills\nload together for any broadcast-style deployment, and they do\nNOT collapse into one another — Firefly does not stream media;\nRivermax does not discipline the PHC.",{"type":40,"tag":125,"props":1690,"children":1691},{},[1692,1702],{"type":40,"tag":559,"props":1693,"children":1695},{"href":1694},"..\u002Fdoca-dms\u002FSKILL.md",[1696],{"type":40,"tag":65,"props":1697,"children":1699},{"className":1698},[],[1700],{"type":46,"value":1701},"doca-dms",{"type":46,"value":1703}," — sibling service skill. The\nagent reading both skills should see the same service-skill shape\n(container, BlueField Arm, deployment pattern, smoke-before-scale,\nenv preconditions, config schema) layered on top of a different\nper-service domain (DMS = device management via gNMI \u002F gNOI;\nFirefly = time synchronization via PTP).",{"type":40,"tag":125,"props":1705,"children":1706},{},[1707,1717],{"type":40,"tag":559,"props":1708,"children":1710},{"href":1709},"..\u002F..\u002Fdoca-debug\u002FSKILL.md",[1711],{"type":40,"tag":65,"props":1712,"children":1714},{"className":1713},[],[1715],{"type":46,"value":1716},"doca-debug",{"type":46,"value":1718}," — the cross-cutting\ndebug ladder (install \u002F version \u002F build \u002F link \u002F runtime \u002F\nprogram \u002F driver). Firefly-specific debug (PTP not syncing,\nhost clock not following, jitter past spec) overlays on top of\nthat ladder.",{"items":1720,"total":1879},[1721,1739,1757,1768,1780,1794,1807,1821,1834,1845,1859,1868],{"slug":1722,"name":1722,"fn":1723,"description":1724,"org":1725,"tags":1726,"stars":1736,"repoUrl":1737,"updatedAt":1738},"nemoclaw-user-guide","retrieve NemoClaw documentation and configuration","Guides human users' AI agents to the NemoClaw docs MCP server and canonical Fern documentation in Markdown form. Use when users ask how to install, configure, operate, troubleshoot, secure, or learn NemoClaw with an AI coding assistant. Trigger keywords - nemoclaw docs, use nemoclaw with ai agent, nemoclaw mcp docs, nemoclaw install help, nemoclaw quickstart, nemoclaw markdown docs, llms.txt, agent skills.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1727,1730,1733],{"name":1728,"slug":1729,"type":15},"Documentation","documentation",{"name":1731,"slug":1732,"type":15},"MCP","mcp",{"name":1734,"slug":1735,"type":15},"Search","search",21777,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNemoClaw","2026-07-20T06:00:01.461044",{"slug":1740,"name":1740,"fn":1741,"description":1742,"org":1743,"tags":1744,"stars":1754,"repoUrl":1755,"updatedAt":1756},"mcore-build-and-dependency","manage Megatron-LM development environments","Container-based dev environment setup and dependency management for Megatron-LM. Covers acquiring and launching the CI container, uv package management, and updating uv.lock.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1745,1748,1751],{"name":1746,"slug":1747,"type":15},"Containers","containers",{"name":1749,"slug":1750,"type":15},"Deployment","deployment",{"name":1752,"slug":1753,"type":15},"Python","python",17049,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FMegatron-LM","2026-07-27T06:06:11.249662",{"slug":1758,"name":1758,"fn":1759,"description":1760,"org":1761,"tags":1762,"stars":1754,"repoUrl":1755,"updatedAt":1767},"mcore-bump-base-image","update NVIDIA PyTorch base images","Bump the NVIDIA PyTorch base image (`nvcr.io\u002Fnvidia\u002Fpytorch:YY.MM-py3`) used by Megatron-LM CI. Covers the two pin sites (GitHub CI in `docker\u002F.ngc_version.dev` and GitLab CI in `.gitlab\u002Fstages\u002F01.build.yml`), the post-bump CI loop (re-run functional tests, refresh golden values, mark broken tests), and the gotchas that bit PRs",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1763,1766],{"name":1764,"slug":1765,"type":15},"CI\u002FCD","ci-cd",{"name":1749,"slug":1750,"type":15},"2026-07-14T05:25:59.97109",{"slug":1769,"name":1769,"fn":1770,"description":1771,"org":1772,"tags":1773,"stars":1754,"repoUrl":1755,"updatedAt":1779},"mcore-cicd","manage CI\u002FCD pipelines for Megatron-LM","CI\u002FCD reference for Megatron-LM. Covers CI pipeline structure, PR scope labels, triggering internal GitLab CI (which force-pushes the current branch to a pull-request\u002FBRANCH ref — always dry-run and verify the destination first; never run against shared or protected branches), and CI failure investigation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1774,1775,1776],{"name":1764,"slug":1765,"type":15},{"name":1749,"slug":1750,"type":15},{"name":1777,"slug":1778,"type":15},"GitHub","github","2026-07-27T06:06:12.278222",{"slug":1781,"name":1781,"fn":1782,"description":1783,"org":1784,"tags":1785,"stars":1754,"repoUrl":1755,"updatedAt":1793},"mcore-create-issue","investigate CI failures and create issues","Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1786,1789,1790],{"name":1787,"slug":1788,"type":15},"Debugging","debugging",{"name":1777,"slug":1778,"type":15},{"name":1791,"slug":1792,"type":15},"Triage","triage","2026-07-14T05:25:57.442089",{"slug":1795,"name":1795,"fn":1796,"description":1797,"org":1798,"tags":1799,"stars":1754,"repoUrl":1755,"updatedAt":1806},"mcore-linting-and-formatting","lint and format Megatron-LM code","Linting and formatting for Megatron-LM. Covers running autoformat.sh, tools (ruff, black, isort, pylint, mypy), and code style rules.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1800,1803],{"name":1801,"slug":1802,"type":15},"Best Practices","best-practices",{"name":1804,"slug":1805,"type":15},"Code Analysis","code-analysis","2026-07-14T05:25:56.18433",{"slug":1808,"name":1808,"fn":1809,"description":1810,"org":1811,"tags":1812,"stars":1754,"repoUrl":1755,"updatedAt":1820},"mcore-migrate-gpt-to-hybrid","migrate Megatron-LM models to HybridModel","Migration guide for moving Megatron Core GPTModel checkpoints, model providers, training commands, and layer mappings to HybridModel.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1813,1816,1819],{"name":1814,"slug":1815,"type":15},"Machine Learning","machine-learning",{"name":1817,"slug":1818,"type":15},"Migration","migration",{"name":9,"slug":8,"type":15},"2026-07-17T06:07:11.777011",{"slug":1822,"name":1822,"fn":1823,"description":1824,"org":1825,"tags":1826,"stars":1754,"repoUrl":1755,"updatedAt":1833},"mcore-onboard-gb200-1node-tests","onboard functional tests for GB200","Onboard 1-node GitHub MR functional tests for GB200 from existing mr-scoped 2-node tests.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1827,1830],{"name":1828,"slug":1829,"type":15},"QA","qa",{"name":1831,"slug":1832,"type":15},"Testing","testing","2026-07-14T05:25:53.673039",{"slug":1835,"name":1835,"fn":1836,"description":1837,"org":1838,"tags":1839,"stars":1754,"repoUrl":1755,"updatedAt":1844},"mcore-run-on-slurm","launch distributed training jobs on SLURM","How to launch distributed Megatron-LM training jobs on a SLURM cluster. Covers a minimal sbatch skeleton, environment-variable setup for torch.distributed.run, CUDA_DEVICE_MAX_CONNECTIONS rules across hardware and parallelism modes, container conventions, monitoring, and per-rank failure diagnosis.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1840,1841],{"name":1749,"slug":1750,"type":15},{"name":1842,"slug":1843,"type":15},"Infrastructure","infrastructure","2026-07-14T05:25:49.362534",{"slug":1846,"name":1846,"fn":1847,"description":1848,"org":1849,"tags":1850,"stars":1754,"repoUrl":1755,"updatedAt":1858},"mcore-split-pr","split pull requests to reduce review load","Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1851,1854,1855],{"name":1852,"slug":1853,"type":15},"Code Review","code-review",{"name":1777,"slug":1778,"type":15},{"name":1856,"slug":1857,"type":15},"Pull Requests","pull-requests","2026-07-14T05:26:01.226578",{"slug":1860,"name":1860,"fn":1861,"description":1862,"org":1863,"tags":1864,"stars":1754,"repoUrl":1755,"updatedAt":1867},"mcore-testing","run and manage Megatron-LM tests","Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1865,1866],{"name":1828,"slug":1829,"type":15},{"name":1831,"slug":1832,"type":15},"2026-07-14T05:25:54.928983",{"slug":1869,"name":1869,"fn":1870,"description":1871,"org":1872,"tags":1873,"stars":1754,"repoUrl":1755,"updatedAt":1878},"nightly-sync","manage nightly main-to-dev sync workflows","Domain knowledge for the nightly main-to-dev sync workflow. Covers merge strategy, CI architecture, failure investigation, and known issues.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1874,1877],{"name":1875,"slug":1876,"type":15},"Automation","automation",{"name":1764,"slug":1765,"type":15},"2026-07-30T05:29:03.275638",496,{"items":1881,"total":1977},[1882,1899,1909,1923,1933,1948,1963],{"slug":1883,"name":1883,"fn":1884,"description":1885,"org":1886,"tags":1887,"stars":20,"repoUrl":21,"updatedAt":1898},"accelerated-computing-cudf","accelerate data processing with cuDF","Official NVIDIA-authored guidance for NVIDIA cuDF GPU DataFrames, pandas acceleration, dask-cuDF, ETL, joins, groupby, CSV\u002FParquet I\u002FO, nullable semantics, and multi-GPU DataFrame workloads.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1888,1891,1894,1895],{"name":1889,"slug":1890,"type":15},"Data Analysis","data-analysis",{"name":1892,"slug":1893,"type":15},"Data Engineering","data-engineering",{"name":9,"slug":8,"type":15},{"name":1896,"slug":1897,"type":15},"Performance","performance","2026-07-14T05:28:43.176466",{"slug":1900,"name":1900,"fn":1901,"description":1902,"org":1903,"tags":1904,"stars":20,"repoUrl":21,"updatedAt":1908},"aiq-deploy","deploy and manage NVIDIA AI-Q infrastructure","Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1905,1906,1907],{"name":1749,"slug":1750,"type":15},{"name":1842,"slug":1843,"type":15},{"name":9,"slug":8,"type":15},"2026-07-14T05:29:06.667109",{"slug":1910,"name":1910,"fn":1911,"description":1912,"org":1913,"tags":1914,"stars":20,"repoUrl":21,"updatedAt":1922},"aiq-research","conduct deep research with AI-Q","Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1915,1918,1919],{"name":1916,"slug":1917,"type":15},"Agents","agents",{"name":9,"slug":8,"type":15},{"name":1920,"slug":1921,"type":15},"Research","research","2026-07-14T05:28:06.816956",{"slug":1924,"name":1924,"fn":1925,"description":1926,"org":1927,"tags":1928,"stars":20,"repoUrl":21,"updatedAt":1932},"amc-run-sample-calibration","run AMC sample dataset calibration","Run end-to-end calibration on the shipped sample dataset (sdg_08_2_sample_data_010926.zip) against a running AMC microservice. Use when user says 'test sample dataset', 'run sample calibration', 'verify AMC install', or 'launch and test'.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1929,1930,1931],{"name":1889,"slug":1890,"type":15},{"name":9,"slug":8,"type":15},{"name":1831,"slug":1832,"type":15},"2026-07-17T05:29:03.913266",{"slug":1934,"name":1934,"fn":1935,"description":1936,"org":1937,"tags":1938,"stars":20,"repoUrl":21,"updatedAt":1947},"amc-run-video-calibration","calibrate video datasets with AutoMagicCalib","Calibrate a new dataset from pre-recorded video files via the AutoMagicCalib REST API. Use when user has local MP4s and says 'calibrate my videos', 'run AMC on these videos', or similar. For RTSP\u002Flive streams, use amc-run-rtsp-calibration instead.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1939,1940,1943,1944],{"name":1875,"slug":1876,"type":15},{"name":1941,"slug":1942,"type":15},"Imaging","imaging",{"name":9,"slug":8,"type":15},{"name":1945,"slug":1946,"type":15},"Video","video","2026-07-17T05:28:53.905004",{"slug":1949,"name":1949,"fn":1950,"description":1951,"org":1952,"tags":1953,"stars":20,"repoUrl":21,"updatedAt":1962},"amc-setup-calibration-stack","deploy AutoMagicCalib microservice with Docker","Launch AutoMagicCalib microservice and web UI from NGC release images via Docker Compose. Use when user says 'deploy auto calibration', 'launch auto calibration', 'launch AMC', 'start MS+UI', or 'set up auto-magic-calib'. Requires NGC API key.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1954,1955,1958,1959],{"name":1749,"slug":1750,"type":15},{"name":1956,"slug":1957,"type":15},"Docker","docker",{"name":9,"slug":8,"type":15},{"name":1960,"slug":1961,"type":15},"Operations","operations","2026-07-17T05:28:56.913999",{"slug":1964,"name":1964,"fn":1965,"description":1966,"org":1967,"tags":1968,"stars":20,"repoUrl":21,"updatedAt":1976},"cudaq-guide","develop quantum applications with CUDA-Q","CUDA-Q onboarding guide for installation, test programs, GPU simulation, QPU hardware, and quantum applications.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[1969,1970,1973],{"name":9,"slug":8,"type":15},{"name":1971,"slug":1972,"type":15},"Quantum Computing","quantum-computing",{"name":1974,"slug":1975,"type":15},"Simulation","simulation","2026-07-14T05:26:58.898253",305]