statecraft.
Catalog/rustev

054-npm-rustev-scope

The npm packages move to the owner's @rustev scope (amends 027 and 031)

Lifecycle approvedImplementation completeVerification unknownQualification unknown

A narrow amendment of approved specs 027 and 031. Both specs named the npm packages under the `@statecrafting` scope and recorded that whether that scope could be used was not established. The owner publishes Rustev under the npm organization `rustev` (2026-10-25). This spec moves every npm package from `@statecrafting/` to `@rustev/` and changes nothing else: the native package `@rustev/rustev`, its platform packages `@rustev/rustev-<platform>`, and the WebAssembly package `@rustev/rustev-wasm`. No API, export, crate name, container image or GitHub location changes. Ratified by the owner on 2026-10-25 (A-56).

Read the full pinned specification ↗

Relationships

Claimed units

  • extends
    {
  "nature": "amending",
  "spec": "027-node-and-wasm-bindings",
  "unit": {
    "kind": "directory",
    "path": "integrations/rustev-node/"
  }
}
  • extends
    {
  "nature": "amending",
  "spec": "027-node-and-wasm-bindings",
  "unit": {
    "kind": "directory",
    "path": "integrations/rustev-wasm/"
  }
}
  • extends
    {
  "nature": "amending",
  "spec": "027-node-and-wasm-bindings",
  "unit": {
    "kind": "directory",
    "path": "tools/rustev-conformance/"
  }
}
  • extends
    {
  "nature": "amending",
  "spec": "031-public-api-and-release-family",
  "unit": {
    "kind": "directory",
    "path": "tools/rustev-release/"
  }
}

Source headings

  1. 054: The npm packages move to the owner's @rustev scope (amends 027 and 031)
  2. 1. Purpose
  3. 2. Territory
  4. 3. Names
  5. 4. Out of scope
  6. 5. Observable negative cases
  7. Acceptance
  8. Verification
  9. Decisions at approval
  10. Implementation record

Frozen anchors

No frozen anchors declared.