@kungfu-tech/kfd 1.0.0-alpha.0 → 1.0.0-alpha.1

package/README.md

@@ -146,7 +146,9 @@ scripts/       conformance check: registry and documents must agree
 `node scripts/check.mjs` (also `pnpm run check`) verifies numbering
 uniqueness, registry/document agreement, status validity, and the release
 impact ledger required by Buildchain production release passports. Releases are
-governed by Buildchain; this package versions itself under KFD-1's own rules.
+governed by Buildchain; this package versions itself under KFD-1's own rules:
+the outer package line remains `v1.0`, while patch and prerelease numbers are
+advanced by Buildchain release promotion.
 
 ## Release impact ledger
 
@@ -160,7 +162,9 @@ release-passport-impact-json: release-impact.json
 For ordinary KFD content changes, keep `kfd-content` at `patch`. Move
 `kfd-registry-schema` or `kfd-package-structure` to `minor` or `major` only
 when those machine-consumed surfaces add or break fields, meanings, package
-paths, or published structure under KFD-1.
+paths, or published structure under KFD-1. These values are Buildchain release
+passport impact classifications; they do not by themselves open a new
+`@kungfu-tech/kfd` package major or minor line.
 
 ## License
 

package/decisions/kfd-1.md

@@ -157,10 +157,12 @@ and does not drift invisibly.
 KFD documents are append-only. A KFD's number is immutable and is the
 content-layer coordinate; substantive semantic change is made by minting a new
 KFD that supersedes the old number (namespace welding applied to decisions).
-Consequently, in the `@kungfu-tech/kfd` package, content operations — new
-KFDs, status flips, editorial clarifications — are patches; only the machine
-surfaces of the package itself (the registry schema, the package structure)
-can move minor or major.
+Consequently, in the `@kungfu-tech/kfd` package, the outer package line stays
+fixed at `v1.0`. Content operations — new KFDs, status flips, editorial
+clarifications — are patches. Machine surfaces of the package itself (the
+registry schema, the package structure) can still require `minor` or `major`
+surface-impact review in the Buildchain release passport, but that review
+classification is not a silent package-line upgrade.
 
 ## Adopters
 

package/package.json

@@ -1,10 +1,24 @@
 {
   "name": "@kungfu-tech/kfd",
-  "version": "1.0.0-alpha.0",
+  "version": "1.0.0-alpha.1",
   "description": "Kung Fu Decisions (KFD): the kungfu-systems organization-wide decision registry, as a consumable artifact",
   "license": "Apache-2.0",
-  "files": ["README.md", "decisions", "registry.json", "site", "docs"],
-  "scripts": {"check": "node scripts/check.mjs"},
-  "publishConfig": {"registry": "https://registry.npmjs.org/", "access": "public"},
-  "repository": {"type": "git", "url": "git+https://github.com/kungfu-systems/kfd.git"}
+  "files": [
+    "README.md",
+    "decisions",
+    "registry.json",
+    "site",
+    "docs"
+  ],
+  "scripts": {
+    "check": "node scripts/check.mjs"
+  },
+  "publishConfig": {
+    "registry": "https://registry.npmjs.org/",
+    "access": "public"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/kungfu-systems/kfd.git"
+  }
 }