Nasiko Control Plane
Use this skill when a user explicitly asks to install, inspect, or operate the
Nasiko control plane with ECC.
Safety contract
- Begin with
ecc nasiko status --json. Status is read-only.
- Installation always requires explicit user consent and
--yes.
- Install only an ECC-qualified pinned version, currently
v0.1.0.
- Preview first with
ecc nasiko install --version v0.1.0 --dry-run --json.
- Install with
ecc nasiko install --version v0.1.0 --yes --json only after the
user reviews the version, registry origin, digest, and destination.
- Remove only a still-qualified ECC-managed binary with
ecc nasiko uninstall --version v0.1.0 --yes --json. Preview removal with
--dry-run first.
- The qualified source is
https://github.com/Nasiko-Labs/nasiko, licensed
under Apache-2.0; artifact and extracted-binary SHA-256 values are pinned.
- Never replace the qualified command with a downloaded shell or PowerShell
bootstrap script.
- Never put secrets or credentials in command arguments, logs, skill output,
install metadata, or ECC state.
- Nasiko telemetry and any sharing with Nasiko or Ito must be opt-in and
separately disclosed. Installation is not telemetry consent.
Lifecycle boundary
The initial ECC bridge supports qualified installation, read-only status, and
ownership-checked uninstall. Use the canonical Nasiko CLI directly for connection, authentication,
launch, deployment, or shutdown until those verbs have their own verified ECC
contracts. Do not guess CLI verbs.
Installing the CLI does not prove that a control-plane server is running, an
agent is governed, routing or ACLs work, observability is complete, telemetry
was enabled, or Ito compute is connected. Report each state separately.
Failure behavior
- If the platform, architecture, version, manifest, digest, archive, binary, or
destination fails validation, stop without executing the artifact.
- Do not fall back to
latest.
- Do not search arbitrary
PATH entries. Use ECC's qualified location or an
explicit absolute ECC_NASIKO_CLI_EXECUTABLE for development verification.
- Do not treat a partial or ambiguous installation as success.
1---2name: nasiko-control-plane3description: Install, detect, and operate the optional Nasiko agent control plane through ECC with pinned artifacts, explicit consent, and telemetry and secrets boundaries.4---56# Nasiko Control Plane78Use this skill when a user explicitly asks to install, inspect, or operate the9Nasiko control plane with ECC.1011## Safety contract1213- Begin with `ecc nasiko status --json`. Status is read-only.14- Installation always requires explicit user consent and `--yes`.15- Install only an ECC-qualified pinned version, currently `v0.1.0`.16- Preview first with `ecc nasiko install --version v0.1.0 --dry-run --json`.17- Install with `ecc nasiko install --version v0.1.0 --yes --json` only after the18 user reviews the version, registry origin, digest, and destination.19- Remove only a still-qualified ECC-managed binary with20 `ecc nasiko uninstall --version v0.1.0 --yes --json`. Preview removal with21 `--dry-run` first.22- The qualified source is `https://github.com/Nasiko-Labs/nasiko`, licensed23 under Apache-2.0; artifact and extracted-binary SHA-256 values are pinned.24- Never replace the qualified command with a downloaded shell or PowerShell25 bootstrap script.26- Never put secrets or credentials in command arguments, logs, skill output,27 install metadata, or ECC state.28- Nasiko telemetry and any sharing with Nasiko or Ito must be opt-in and29 separately disclosed. Installation is not telemetry consent.3031## Lifecycle boundary3233The initial ECC bridge supports qualified installation, read-only status, and34ownership-checked uninstall. Use the canonical Nasiko CLI directly for connection, authentication,35launch, deployment, or shutdown until those verbs have their own verified ECC36contracts. Do not guess CLI verbs.3738Installing the CLI does not prove that a control-plane server is running, an39agent is governed, routing or ACLs work, observability is complete, telemetry40was enabled, or Ito compute is connected. Report each state separately.4142## Failure behavior4344- If the platform, architecture, version, manifest, digest, archive, binary, or45 destination fails validation, stop without executing the artifact.46- Do not fall back to `latest`.47- Do not search arbitrary `PATH` entries. Use ECC's qualified location or an48 explicit absolute `ECC_NASIKO_CLI_EXECUTABLE` for development verification.49- Do not treat a partial or ambiguous installation as success.
gongyijie85