@kungfu-tech/kfd 1.0.0-alpha.14 → 1.0.0-alpha.16

package/decisions/kfd-3.md

@@ -1,4 +1,4 @@
-# KFD-3: Cooperation must start from transparent value — compliance must not be coerced
+# KFD-3: Cooperation must start from trusted value — compliance must not be coerced
 
 - Status: active
 - Number: 3
@@ -7,12 +7,12 @@
 
 ## One sentence
 
-Cooperation must start from transparent value.
+Cooperation must start from trusted value.
 
 A product must not obtain cooperation through pressure, manipulation, hidden
-control, or forced workflow capture. It must make value, choices, and
-constraints visible enough for intelligent participants to understand, decide,
-and cooperate.
+control, or forced workflow capture. It must make facts, value, choices, and
+constraints transparent enough for intelligent participants to trust what is
+being offered, understand the available path, decide, and cooperate.
 
 ## Decision type
 
@@ -30,11 +30,12 @@ kungfu-systems takes toward humans and agents as reasoning participants.
 Within the KFD-1/2/3 foundation, this is the relationship path:
 
 ```text
-cooperation must start from transparent value
+cooperation must start from trusted value
 ```
 
 KFD-2 protects the truth path: show facts before asking for trust. KFD-3
-protects the relationship path: show value before asking for cooperation.
+protects the relationship path: make value transparent enough to be trusted
+before asking for cooperation.
 
 ## Principle
 
@@ -60,7 +61,7 @@ The default product path should therefore follow this chain:
 
 ```text
 transparent facts
-  -> discoverable value
+  -> trusted value
   -> stable choice
   -> explainable constraint
   -> voluntary cooperation
@@ -85,7 +86,7 @@ Products may recommend a path, refuse unsafe actions, or require explicit
 approval. They should not pretend that forced compliance is the same as
 understanding or trust.
 
-### 2. Make value discoverable through facts
+### 2. Make value trusted through transparent facts
 
 Humans and agents should be able to discover what the product can do, why it is
 useful, what it observed, what it changed, and what boundary applies without
@@ -93,7 +94,8 @@ needing oral context, private maintainer memory, or web-only documentation.
 
 Agent-facing surfaces should expose local, versioned, machine-readable and
 human-readable facts wherever possible. A capable agent should be able to learn
-the product's value by inspecting the product's own facts and commands.
+the product's value, and why that value can be trusted, by inspecting the
+product's own facts and commands.
 
 ### 3. Use constraints as transparent safety, not hidden control
 
@@ -142,9 +144,10 @@ how it can be changed, escalated, or revoked when appropriate
 - It does not turn a private founder narrative into a public repository rule.
   This public rule is about product stance, adoption, safety, and cooperation
   with intelligent participants.
-- It does not supersede KFD-2. Facts and responsibility still come first; this
-  KFD states how those facts should be presented to humans and agents without
-  coercion.
+- It does not supersede KFD-2. Facts and responsibility still come first;
+  transparent value is the route by which value becomes trusted, not a
+  substitute for trust. This KFD states how those facts and values should be
+  presented to humans and agents without coercion.
 
 ## Relation to KFD-2
 
@@ -155,12 +158,12 @@ hidden control. Together:
 ```text
 KFD-1: facts must not drift.
 KFD-2: trust must start from facts.
-KFD-3: cooperation must start from transparent value.
+KFD-3: cooperation must start from trusted value.
 ```
 
 KFD-1 protects the fact-source layer. KFD-2 protects the trust layer. KFD-3
-protects the relationship with the intelligent participant who must walk that
-path.
+protects the relationship with the intelligent participant who must decide
+whether the offered value is trustworthy enough to walk that path.
 
 ## Implementation case: the KFD package
 

package/kfd.release.json

@@ -4,7 +4,7 @@
   "line": "v1.0",
   "channel": "alpha",
   "npmPackage": "@kungfu-tech/kfd",
-  "npmVersion": "1.0.0-alpha.14",
+  "npmVersion": "1.0.0-alpha.16",
   "source": {
     "repository": "kungfu-systems/kfd",
     "branch": "alpha/v1/v1.0"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kungfu-tech/kfd",
-  "version": "1.0.0-alpha.14",
+  "version": "1.0.0-alpha.16",
   "description": "Kung Fu Decisions (KFD): the kungfu-systems organization-wide decision registry, as a consumable artifact",
   "license": "Apache-2.0",
   "files": [
@@ -12,6 +12,7 @@
     "kfd.release.json",
     "schemas",
     "site",
+    "scripts",
     "buildchain.release-propagation.json",
     "release-impact.json",
     ".buildchain/kfd-1/contract-world.witness.json",
@@ -29,6 +30,7 @@
     "./site/kfd-site.json": "./site/kfd-site.json",
     "./buildchain.release-propagation.json": "./buildchain.release-propagation.json",
     "./release-impact.json": "./release-impact.json",
+    "./scripts/*.mjs": "./scripts/*.mjs",
     "./buildchain/kfd-1/contract-world.witness.json": "./.buildchain/kfd-1/contract-world.witness.json",
     "./buildchain/kfd-2/public-release-trust.claim.json": "./.buildchain/kfd-2/public-release-trust.claim.json",
     "./buildchain/kfd-3/collaboration-interface.json": "./.buildchain/kfd-3/collaboration-interface.json",
@@ -41,6 +43,7 @@
   },
   "scripts": {
     "check": "node scripts/check.mjs",
+    "update:site-bundle": "node scripts/update-site-bundle.mjs",
     "update:kfd-1-witness": "node scripts/update-kfd-1-witness.mjs",
     "update:kfd-2-claim": "node scripts/update-kfd-2-claim.mjs",
     "update:kfd-3-witness": "node scripts/update-kfd-3-witness.mjs"

package/registry.json

@@ -26,7 +26,7 @@
       "number": 3,
       "id": "KFD-3",
       "slug": "kfd-3",
-      "title": "Cooperation must start from transparent value: compliance must not be coerced",
+      "title": "Cooperation must start from trusted value: compliance must not be coerced",
       "kind": "principle",
       "status": "active",
       "path": "decisions/kfd-3.md",

package/release-impact.json

@@ -9,14 +9,14 @@
   "versionImpact": {
     "final": "minor",
     "source": "kfd-surface-register",
-    "rationale": "This change additively registers KFD-owned standards metadata, the KFD-2 trust taxonomy, KFD-2 release trust schemas, KFD-3 collaboration-interface schemas, KFD-3 self-verification witnesses, and KFD-1 document/interface integrity bindings while keeping existing registry and decision surfaces compatible."
+    "rationale": "This change additively registers KFD-owned standards metadata, the KFD-2 trust taxonomy, KFD-2 release trust schemas, KFD-3 collaboration-interface schemas, KFD-3 self-verification witnesses, KFD-1 document/interface integrity bindings, and the README-backed KFD site homepage projection while keeping existing registry and decision surfaces compatible."
   },
   "surfaceImpacts": [
     {
       "id": "kfd-content",
       "impact": "patch",
       "class": "content",
-      "rationale": "KFD documents are append-only content coordinates; current documentation changes clarify the KFD public fact-source, license, trademark, official-status, and derivative-authority boundaries without altering the decision numbers or registry shape."
+      "rationale": "KFD documents are append-only content coordinates; current documentation changes clarify KFD-3's foundation wording from transparent value to trusted value so the KFD-1/2/3 chain reads facts -> trust -> cooperation, while preserving the existing non-coercion and transparency requirements."
     },
     {
       "id": "kfd-registry-schema",
@@ -34,7 +34,13 @@
       "id": "kfd-package-structure",
       "impact": "minor",
       "class": "additive",
-      "rationale": "The npm package now publishes the KFD-2 trust taxonomy, KFD-2 schemas, KFD-2 documentation, KFD-3 self collaboration-interface witnesses, TRADEMARKS.md, public fact-source metadata, and agent quickstart/self-proof documentation through existing schemas/, docs/, standards.json, site/, .buildchain/, and subpath exports while preserving existing README.md, decisions/, registry.json, and site/ paths."
+      "rationale": "The npm package now publishes the KFD-2 trust taxonomy, KFD-2 schemas, KFD-2 documentation, KFD-3 self collaboration-interface witnesses, TRADEMARKS.md, public fact-source metadata, agent quickstart/self-proof documentation, and repository verification scripts through existing schemas/, docs/, standards.json, site/, scripts/, .buildchain/, and subpath exports while preserving existing README.md, decisions/, registry.json, and site/ paths."
+    },
+    {
+      "id": "kfd-site-homepage-bundle",
+      "impact": "minor",
+      "class": "additive",
+      "rationale": "site/kfd-site.json now exposes generated README-backed homepage.sections and homepage.displayPlan fields, and scripts/check.mjs verifies the checked-in bundle matches the README projection so downstream sites can render KFD-owned homepage content without maintaining their own README parser or drifting copy."
     },
     {
       "id": "kfd-3-self-collaboration",
@@ -61,5 +67,5 @@
       "rationale": "The KFD to site-libkungfu-dev propagation graph now targets the downstream site's actual main branch and documents the exact KFD package surfaces consumed by kfd.libkungfu.dev, without changing the release propagation graph contract."
     }
   ],
-  "summary": "KFD v1.0 production promotion is minor-impact because it additively exposes KFD-2 trust taxonomy and release trust metadata, KFD-1/2/3 interface version metadata, KFD-3 self-verification witnesses, document integrity bindings, and a corrected site release-propagation target for Buildchain and other consumers; existing registry, decision text, site bundle, and propagation graph contracts remain compatible."
+  "summary": "KFD v1.0 production promotion is minor-impact because it additively exposes KFD-2 trust taxonomy and release trust metadata, KFD-1/2/3 interface version metadata, KFD-3 self-verification witnesses, document integrity bindings, a README-backed homepage bundle/display plan, and a corrected site release-propagation target for Buildchain and other consumers; existing registry, decision text, site bundle, and propagation graph contracts remain compatible."
 }