← Nexo YAML IronCONTENT HISTORY

Update to Nexo YAML Iron

Snapshot Oct 31, 2026 · 12:10 UTC · version 2026.1.1

Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.

WHAT CHANGED

Instructions updated for inspect-kubernetes-relationships

Full description — Now says: declared workload, Service, Ingress or resource-reference relationships and explicit unknown evidence. Use detailed inspection for underlying facts and...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Nexo YAML Iron and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Full description

Before

Sep 30, 2026 · 23:15 UTC

established Service, Deployment, or Ingress relationship findings and explicit uncertainty. Use detailed inspection only when deeper evidence is needed. Do not use it as evidence of live cluster state, Helm output, policy compliance,

After

Oct 31, 2026 · 12:10 UTC

declared workload, Service, Ingress or resource-reference relationships and explicit unknown evidence. Use detailed inspection for underlying facts and joins. Do not use this as evidence of live cluster state, policy compliance

Skill instructions

Before

Sep 30, 2026 · 23:15 UTC

established Service, Deployment, or Ingress relationship findings and explicit uncertainty. Use detailed inspection only when deeper evidence is needed. Do not use it as evidence of live cluster state, Helm output, policy compliance, or ...

After

Oct 31, 2026 · 12:10 UTC

declared workload, Service, Ingress or resource-reference relationships and explicit unknown evidence. Use detailed inspection for underlying facts and joins. Do not use this as evidence of live cluster state, policy compliance or runtim...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,48 +1,94 @@
 ---
 name: inspect-kubernetes-relationships
-description: Review supplied local Kubernetes YAML with Nexo YAML Iron when the user needs established Service, Deployment, or Ingress relationship findings and explicit uncertainty. Use detailed inspection only when deeper evidence is needed. Do not use it as evidence of live cluster state, Helm output, policy compliance, or runtime health.
+description: Review supplied local Kubernetes YAML with Nexo YAML Iron when the user needs declared workload, Service, Ingress or resource-reference relationships and explicit unknown evidence. Use detailed inspection for underlying facts and joins. Do not use this as evidence of live cluster state, policy compliance or runtime health.
 ---
 
 # Review Kubernetes Relationships
 
-Use the bundled executable at `${PLUGIN_ROOT}/scripts/nexo-yaml-iron` as the authoritative analyzer. Codex may explain Nexo's structured result but must not compute, fill, relabel, or replace Nexo state from intuition.
+Use the executable bundled with this plugin as the authoritative analyzer. Explain
+its structured results without computing, filling, relabeling or replacing Nexo
+state from intuition. This release requires local execution on macOS ARM64.
+
+## Locate the executable
+
+Use `${PLUGIN_ROOT}/scripts/nexo-yaml-iron` when the host supplies a resolved plugin
+root. If that variable is not defined, derive the root from the actual installed
+location of this file: `skills/inspect-kubernetes-relationships/SKILL.md` is two
+levels below it. Use that absolute root with `/scripts/nexo-yaml-iron`. Do not
+substitute a same-named command from PATH or a development checkout.
+
+If the host cannot execute local programs or the platform is unsupported, explain
+the compatibility requirement and stop rather than guessing a result.
 
 ## Run the review
 
-For a supplied local manifest path, run:
+For a manifest path explicitly supplied or authorized by the user:
 
-```bash
+```sh
 "${PLUGIN_ROOT}/scripts/nexo-yaml-iron" review <path>
 ```
 
-Treat this bounded Review result as the primary product-facing output. Preserve Nexo’s distinction between established findings and explicit unknowns. Do not infer a missing finding, fill an unknown, or reconstruct a different relationship state from intuition.
-
-The current implementation supports Kubernetes Service, Deployment, and Ingress. Report other kinds as outside current coverage instead of treating their absence from the result as success.
+If the user supplies YAML text, use the host's local file tools to place the exact
+text in a temporary YAML file before invoking the executable. Preserve its document
+boundaries and values. Do not add a namespace, rewrite fields or scan unrelated
+files. Redact credential values before they are supplied; opaque output is not
+redaction of content already sent to an AI host. Do not split oversized input to
+bypass the 512 KiB file budget.
+
+Present this compact Review result first, preserving established findings and
+explicit unknowns. No reported finding is not a safety or completeness verdict.
+
+## Coverage
+
+Supported declaration kinds are Pod, Deployment, ReplicaSet, StatefulSet,
+DaemonSet, Job, CronJob, Service, Ingress, ConfigMap, Secret, ServiceAccount,
+PersistentVolumeClaim and Namespace. Coverage concerns supported fields and
+relationships, not complete Kubernetes semantics. Keep actual workload kinds and
+namespace-qualified identifiers attached to the explanation.
+
+ConfigMap text, key references, container environment sources, mounts, volumes,
+ServiceAccounts and named resource dependencies can be inspected where supported.
+Explain only supplied text and established reference relationships. Do not infer
+runtime environment expansion or precedence. Secret payloads and binary values
+remain opaque in structured output; do not ask for real credentials.
+
+Unsupported kinds or fields remain outside coverage. Init-container port evidence
+is unknown in this slice. Missing supplied declarations do not prove cluster absence.
 
-## Use detailed inspection only when needed
+## Detailed inspection
 
-When the user needs the underlying machine evidence or a deeper diagnostic view, run:
+Use Inspect when the user needs underlying evidence, complete joins or a deeper
+view of ambiguous Service-port/backend evidence:
 
-```bash
+```sh
 "${PLUGIN_ROOT}/scripts/nexo-yaml-iron" inspect <path> --format json
 ```
 
-Use `--format ndjson` only when row-oriented output is specifically useful. Add `--snapshot`, `--partition`, or `--namespace` only when the user supplies or needs those artifact coordinates. These labels describe the report; they do not establish live cluster state.
-
-## Present the result
-
-For Review output:
-
-- present Nexo's established findings as findings;
-- present Nexo's unresolved evidence as explicit unknowns;
-- keep canonical subjects and identifiers attached to the explanation;
-- do not convert an unknown into a negative finding or downgrade an established mismatch because unrelated evidence is unknown.
-
-If detailed `inspect` evidence is used, keep source keys, namespace context, relationship cases, and gap cases attached to the explanation. `No reported finding` is not proof that a deployment is safe, complete, policy-compliant, or healthy.
+Review is a compact projection and does not enumerate every established
+relationship. Preserve relevant Inspect evidence when Review omits a summary.
+Use `--format ndjson` only when row-oriented output is useful. Add `--snapshot`,
+`--partition` or `--namespace` only for requested artifact coordinates; these flags
+do not supply a missing manifest namespace or establish live cluster state.
+
+## Explain the evidence
+
+- Preserve findings, unknowns, source keys, namespaces, route bindings and gap cases.
+- A known witness can coexist with residual unknowns. Do not erase either one.
+- An unknown does not establish a negative finding. A removed gap does not prove repair.
+- Explain ConfigMap references from supplied facts; do not invent unseen values.
+- If a diagram helps or the user requests one, show a small relevant relationship
+  using color for established, unresolved and unknown evidence. Keep it grounded
+  in structured output and avoid drawing every artifact row.
+- If the executable fails or returns an error object, report that failure without
+  inventing results. Preserve the original input.
 
 ## Boundaries
 
-- Do not connect to a cluster, read kubeconfig, call cloud APIs, render Helm, apply manifests, mutate YAML, or claim runtime observation.
-- Do not present Nexo as a generic YAML linter, admission controller, security scanner, or auto-fixer.
-- If the user asks for edits or deployment actions after Review or inspection, treat that as a separate task and authorization boundary.
-- If the executable fails or returns an error object, report the failure and preserve the original input rather than guessing a result.
+Do not contact a cluster, read kubeconfig, call cloud APIs, render Helm, apply
+manifests or mutate the supplied YAML as part of this review. Edits requested by
+the user are a separate task. Do not present Nexo as a generic linter, security
+scanner, admission controller or auto-fixer. This release does not collect
+telemetry, observe conversations or invoke experimental 7T interpretation.
+
+Packaged sample manifests are in `../../examples/`; use them only when requested
+for a demonstration. Real user reviews must use the user's supplied input.
Full technical diff · 2 changed fields

changed /description

BEFORE
"Review supplied local Kubernetes YAML with Nexo YAML Iron when the user needs established Service, Deployment, or Ingress relationship findings and explicit uncertainty. Use detailed inspection only when deeper evidence is needed. Do not use it as evidence of live cluster state, Helm output, policy compliance, or runtime health."
AFTER
"Review supplied local Kubernetes YAML with Nexo YAML Iron when the user needs declared workload, Service, Ingress or resource-reference relationships and explicit unknown evidence. Use detailed inspection for underlying facts and joins. Do not use this as evidence of live cluster state, policy compliance or runtime health."

changed /skill_md_contents

BEFORE
"---\nname: inspect-kubernetes-relationships\ndescription: Review supplied local Kubernetes YAML with Nexo YAML Iron when the user needs established Service, Deployment, or Ingress relationship findings and explicit uncertainty. Use detailed inspection only when deeper evidence is needed. Do not use it as evidence of live cluster state, Helm output, policy compliance, or runtime health.\n---\n\n# Review Kubernetes Relationships\n\nUse the bundled executable at `${PLUGIN_ROOT}/scripts/nexo-yaml-iron` as the authoritative analyzer. Codex may explain Nexo's structured result but must not compute, fill, relabel, or replace Nexo state from intuition.\n\n## Run the review\n\nFor a supplied local manifest path, run:\n\n```bash\n\"${PLUGIN_ROOT}/scripts/nexo-yaml-iron\" review <path>\n```\n\nTreat this bounded Review result as the primary product-facing output. Preserve Nexo’s distinction between established findings and explicit unknowns. Do not infer a missing finding, fill an unknown, or reconstruct a different relationship state from intuition.\n\nThe current implementation supports Kubernetes Service, Deployment, and Ingress. Report other kinds as outside current coverage instead of treating their absence from the result as success.\n\n## Use detailed inspection only when needed\n\nWhen the user needs the underlying machine evidence or a deeper diagnostic view, run:\n\n```bash\n\"${PLUGIN_ROOT}/scripts/nexo-yaml-iron\" inspect <path> --format json\n```\n\nUse `--format ndjson` only when row-oriented output is specifically useful. Add `--snapshot`, `--partition`, or `--namespace` only when the user supplies or needs those artifact coordinates. These labels describe the report; they do not establish live cluster state.\n\n## Present the result\n\nFor Review output:\n\n- present Nexo's established findings as findings;\n- present Nexo's unresolved evidence as explicit unknowns;\n- keep canonical subjects and identifiers attached to the explanation;\n- do not convert an unknown into a negative finding or downgrade an established mismatch because unrelated evidence is unknown.\n\nIf detailed `inspect` evidence is used, keep source keys, namespace context, relationship cases, and gap cases attached to the explanation. `No reported finding` is not proof that a deployment is safe, complete, policy-compliant, or healthy.\n\n## Boundaries\n\n- Do not connect to a cluster, read kubeconfig, call cloud APIs, render Helm, apply manifests, mutate YAML, or claim runtime observation.\n- Do not present Nexo as a generic YAML linter, admission controller, security scanner, or auto-fixer.\n- If the user asks for edits or deployment actions after Review or inspection, treat that as a separate task and authorization boundary.\n- If the executable fails or returns an error object, report the failure and preserve the original input rather than guessing a result.\n"
AFTER
"---\nname: inspect-kubernetes-relationships\ndescription: Review supplied local Kubernetes YAML with Nexo YAML Iron when the user needs declared workload, Service, Ingress or resource-reference relationships and explicit unknown evidence. Use detailed inspection for underlying facts and joins. Do not use this as evidence of live cluster state, policy compliance or runtime health.\n---\n\n# Review Kubernetes Relationships\n\nUse the executable bundled with this plugin as the authoritative analyzer. Explain\nits structured results without computing, filling, relabeling or replacing Nexo\nstate from intuition. This release requires local execution on macOS ARM64.\n\n## Locate the executable\n\nUse `${PLUGIN_ROOT}/scripts/nexo-yaml-iron` when the host supplies a resolved plugin\nroot. If that variable is not defined, derive the root from the actual installed\nlocation of this file: `skills/inspect-kubernetes-relationships/SKILL.md` is two\nlevels below it. Use that absolute root with `/scripts/nexo-yaml-iron`. Do not\nsubstitute a same-named command from PATH or a development checkout.\n\nIf the host cannot execute local programs or the platform is unsupported, explain\nthe compatibility requirement and stop rather than guessing a result.\n\n## Run the review\n\nFor a manifest path explicitly supplied or authorized by the user:\n\n```sh\n\"${PLUGIN_ROOT}/scripts/nexo-yaml-iron\" review <path>\n```\n\nIf the user supplies YAML text, use the host's local file tools to place the exact\ntext in a temporary YAML file before invoking the executable. Preserve its document\nboundaries and values. Do not add a namespace, rewrite fields or scan unrelated\nfiles. Redact credential values before they are supplied; opaque output is not\nredaction of content already sent to an AI host. Do not split oversized input to\nbypass the 512 KiB file budget.\n\nPresent this compact Review result first, preserving established findings and\nexplicit unknowns. No reported finding is not a safety or completeness verdict.\n\n## Coverage\n\nSupported declaration kinds are Pod, Deployment, ReplicaSet, StatefulSet,\nDaemonSet, Job, CronJob, Service, Ingress, ConfigMap, Secret, ServiceAccount,\nPersistentVolumeClaim and Namespace. Coverage concerns supported fields and\nrelationships, not complete Kubernetes semantics. Keep actual workload kinds and\nnamespace-qualified identifiers attached to the explanation.\n\nConfigMap text, key references, container environment sources, mounts, volumes,\nServiceAccounts and named resource dependencies can be inspected where supported.\nExplain only supplied text and established reference relationships. Do not infer\nruntime environment expansion or precedence. Secret payloads and binary values\nremain opaque in structured output; do not ask for real credentials.\n\nUnsupported kinds or fields remain outside coverage. Init-container port evidence\nis unknown in this slice. Missing supplied declarations do not prove cluster absence.\n\n## Detailed inspection\n\nUse Inspect when the user needs underlying evidence, complete joins or a deeper\nview of ambiguous Service-port/backend evidence:\n\n```sh\n\"${PLUGIN_ROOT}/scripts/nexo-yaml-iron\" inspect <path> --format json\n```\n\nReview is a compact projection and does not enumerate every established\nrelationship. Preserve relevant Inspect evidence when Review omits a summary.\nUse `--format ndjson` only when row-oriented output is useful. Add `--snapshot`,\n`--partition` or `--namespace` only for requested artifact coordinates; these flags\ndo not supply a missing manifest namespace or establish live cluster state.\n\n## Explain the evidence\n\n- Preserve findings, unknowns, source keys, namespaces, route bindings and gap cases.\n- A known witness can coexist with residual unknowns. Do not erase either one.\n- An unknown does not establish a negative finding. A removed gap does not prove repair.\n- Explain ConfigMap references from supplied facts; do not invent unseen values.\n- If a diagram helps or the user requests one, show a small relevant relationship\n  using color for established, unresolved and unknown evidence. Keep it grounded\n  in structured output and avoid drawing every artifact row.\n- If the executable fails or returns an error object, report that failure without\n  inventing results. Preserve the original input.\n\n## Boundaries\n\nDo not contact a cluster, read kubeconfig, call cloud APIs, render Helm, apply\nmanifests or mutate the supplied YAML as part of this review. Edits requested by\nthe user are a separate task. Do not present Nexo as a generic linter, security\nscanner, admission controller or auto-fixer. This release does not collect\ntelemetry, observe conversations or invoke experimental 7T interpretation.\n\nPackaged sample manifests are in `../../examples/`; use them only when requested\nfor a demonstration. Real user reviews must use the user's supplied input.\n"
Full snapshot data
{
  "description": "Review supplied local Kubernetes YAML with Nexo YAML Iron when the user needs declared workload, Service, Ingress or resource-reference relationships and explicit unknown evidence. Use detailed inspection for underlying facts and joins. Do not use this as evidence of live cluster state, policy compliance or runtime health.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 385
    }
  ],
  "name": "inspect-kubernetes-relationships",
  "skill_md_contents": "---\nname: inspect-kubernetes-relationships\ndescription: Review supplied local Kubernetes YAML with Nexo YAML Iron when the user needs declared workload, Service, Ingress or resource-reference relationships and explicit unknown evidence. Use detailed inspection for underlying facts and joins. Do not use this as evidence of live cluster state, policy compliance or runtime health.\n---\n\n# Review Kubernetes Relationships\n\nUse the executable bundled with this plugin as the authoritative analyzer. Explain\nits structured results without computing, filling, relabeling or replacing Nexo\nstate from intuition. This release requires local execution on macOS ARM64.\n\n## Locate the executable\n\nUse `${PLUGIN_ROOT}/scripts/nexo-yaml-iron` when the host supplies a resolved plugin\nroot. If that variable is not defined, derive the root from the actual installed\nlocation of this file: `skills/inspect-kubernetes-relationships/SKILL.md` is two\nlevels below it. Use that absolute root with `/scripts/nexo-yaml-iron`. Do not\nsubstitute a same-named command from PATH or a development checkout.\n\nIf the host cannot execute local programs or the platform is unsupported, explain\nthe compatibility requirement and stop rather than guessing a result.\n\n## Run the review\n\nFor a manifest path explicitly supplied or authorized by the user:\n\n```sh\n\"${PLUGIN_ROOT}/scripts/nexo-yaml-iron\" review <path>\n```\n\nIf the user supplies YAML text, use the host's local file tools to place the exact\ntext in a temporary YAML file before invoking the executable. Preserve its document\nboundaries and values. Do not add a namespace, rewrite fields or scan unrelated\nfiles. Redact credential values before they are supplied; opaque output is not\nredaction of content already sent to an AI host. Do not split oversized input to\nbypass the 512 KiB file budget.\n\nPresent this compact Review result first, preserving established findings and\nexplicit unknowns. No reported finding is not a safety or completeness verdict.\n\n## Coverage\n\nSupported declaration kinds are Pod, Deployment, ReplicaSet, StatefulSet,\nDaemonSet, Job, CronJob, Service, Ingress, ConfigMap, Secret, ServiceAccount,\nPersistentVolumeClaim and Namespace. Coverage concerns supported fields and\nrelationships, not complete Kubernetes semantics. Keep actual workload kinds and\nnamespace-qualified identifiers attached to the explanation.\n\nConfigMap text, key references, container environment sources, mounts, volumes,\nServiceAccounts and named resource dependencies can be inspected where supported.\nExplain only supplied text and established reference relationships. Do not infer\nruntime environment expansion or precedence. Secret payloads and binary values\nremain opaque in structured output; do not ask for real credentials.\n\nUnsupported kinds or fields remain outside coverage. Init-container port evidence\nis unknown in this slice. Missing supplied declarations do not prove cluster absence.\n\n## Detailed inspection\n\nUse Inspect when the user needs underlying evidence, complete joins or a deeper\nview of ambiguous Service-port/backend evidence:\n\n```sh\n\"${PLUGIN_ROOT}/scripts/nexo-yaml-iron\" inspect <path> --format json\n```\n\nReview is a compact projection and does not enumerate every established\nrelationship. Preserve relevant Inspect evidence when Review omits a summary.\nUse `--format ndjson` only when row-oriented output is useful. Add `--snapshot`,\n`--partition` or `--namespace` only for requested artifact coordinates; these flags\ndo not supply a missing manifest namespace or establish live cluster state.\n\n## Explain the evidence\n\n- Preserve findings, unknowns, source keys, namespaces, route bindings and gap cases.\n- A known witness can coexist with residual unknowns. Do not erase either one.\n- An unknown does not establish a negative finding. A removed gap does not prove repair.\n- Explain ConfigMap references from supplied facts; do not invent unseen values.\n- If a diagram helps or the user requests one, show a small relevant relationship\n  using color for established, unresolved and unknown evidence. Keep it grounded\n  in structured output and avoid drawing every artifact row.\n- If the executable fails or returns an error object, report that failure without\n  inventing results. Preserve the original input.\n\n## Boundaries\n\nDo not contact a cluster, read kubeconfig, call cloud APIs, render Helm, apply\nmanifests or mutate the supplied YAML as part of this review. Edits requested by\nthe user are a separate task. Do not present Nexo as a generic linter, security\nscanner, admission controller or auto-fixer. This release does not collect\ntelemetry, observe conversations or invoke experimental 7T interpretation.\n\nPackaged sample manifests are in `../../examples/`; use them only when requested\nfor a demonstration. Real user reviews must use the user's supplied input.\n"
}

SHA-256 of public snapshot: bc6fd0a133a3dea6ab2e760a8f3a4a3226845ed8d0568b2dd9258306a15a9242