@kungfu-tech/kfd 1.0.0-alpha.12 → 1.0.0-alpha.13

package/.buildchain/kfd-3/collaboration-interface.prebuild.json

@@ -10,9 +10,9 @@
   "sourceRegistry": {
     "id": "kfd-collaboration-interface",
     "path": ".buildchain/kfd-3/collaboration-interface.json",
-    "sha256": "866fc1f20fe3a4084c31f2edf98e270dd5f7c5bf2801a67e57335daaefa3dd2e"
+    "sha256": "e32f2196399d37db202ccc656386bddc346871243c3db6782d26b5a88f831595"
   },
-  "collaborationInterfaceDigest": "sha256:866fc1f20fe3a4084c31f2edf98e270dd5f7c5bf2801a67e57335daaefa3dd2e",
+  "collaborationInterfaceDigest": "sha256:e32f2196399d37db202ccc656386bddc346871243c3db6782d26b5a88f831595",
   "collaborationInterface": {
     "schemaVersion": 1,
     "contract": "kfd-3-collaboration-interface",
@@ -25,6 +25,28 @@
     "sourceRegistry": {
       "path": "registry.json"
     },
+    "factSources": [
+      {
+        "id": "public-kfd-fact-source",
+        "kind": "git-repository",
+        "host": "github",
+        "repository": "kungfu-systems/kfd",
+        "url": "https://github.com/kungfu-systems/kfd",
+        "loadBearingCoordinate": "commit-addressed repository contents",
+        "stableRenderedIndex": "https://kfd.libkungfu.dev",
+        "canonicalPaths": [
+          "decisions/kfd-N.md",
+          "registry.json",
+          "standards.json"
+        ],
+        "projectionSurfaces": [
+          "https://kfd.libkungfu.dev/N",
+          "npm:@kungfu-tech/kfd",
+          "Buildchain release passports"
+        ],
+        "extensionRequestNote": "GitHub issues are extension request paths; KFD facts are created only by committed repository contents."
+      }
+    ],
     "participants": [
       {
         "id": "human-reader",
@@ -77,6 +99,16 @@
         ],
         "purpose": "Route readers and agents to the right KFD document or machine surface."
       },
+      {
+        "id": "official-status-and-trademarks",
+        "surface": "TRADEMARKS.md",
+        "participants": [
+          "human-reader",
+          "agent-reader",
+          "package-consumer"
+        ],
+        "purpose": "Understand what Apache-2.0 covers and what remains official, trademark-bound, or endorsement-bound."
+      },
       {
         "id": "registry",
         "surface": "registry.json",
@@ -165,6 +197,21 @@
         },
         "maturity": "stable"
       },
+      {
+        "id": "official-status-and-trademarks",
+        "kind": "markdown-doc",
+        "participants": [
+          "human-reader",
+          "agent-reader",
+          "package-consumer"
+        ],
+        "value": "Apache-2.0 reuse boundary, trademark boundary, official source boundary, fork/derivative guidance, and agent-facing authority rule.",
+        "discoverability": {
+          "fromMinimalEntrypoint": true,
+          "path": "TRADEMARKS.md"
+        },
+        "maturity": "stable"
+      },
       {
         "id": "decision-texts",
         "kind": "markdown-doc",
@@ -246,7 +293,7 @@
           "site-consumer",
           "agent-reader"
         ],
-        "value": "KFD-owned content projection consumed by the public site renderer.",
+        "value": "KFD-owned content projection consumed by the public site renderer, including decision metadata and the public KFD fact-source boundary.",
         "discoverability": {
           "fromMinimalEntrypoint": true,
           "path": "site/kfd-site.json"
@@ -420,6 +467,24 @@
         "choice": "Change KFD through PR review, node scripts/check.mjs, and Buildchain release gates."
       }
     ],
+    "extensionRequests": [
+      {
+        "id": "kfd-2-trust-taxonomy-extension",
+        "participants": [
+          "agent-reader",
+          "maintainer",
+          "release-system",
+          "package-consumer"
+        ],
+        "trigger": "A human or agent needs a residual-risk, trust-impact, machine-provability, agent-action, or downgrade-reason value that is not present in schemas/kfd-2/trust-taxonomy.schema.json.",
+        "requestPath": {
+          "kind": "github-issue",
+          "target": "https://github.com/kungfu-systems/kfd/issues/new?title=KFD-2%20trust%20taxonomy%20extension%20request",
+          "template": "State the missing value, the taxonomy field, the product or release scenario, and why existing KFD-2 values cannot express the case."
+        },
+        "expectedOutcome": "KFD maintainers either add the value to the KFD-2 trust taxonomy schema or explain which existing value should be used."
+      }
+    ],
     "closure": {
       "classificationMode": "closed-world",
       "unclassifiedEntrypointsPolicy": "fail",
@@ -457,6 +522,17 @@
       "public": true,
       "sourcePath": "docs/MAP.md"
     },
+    {
+      "id": "official-status-and-trademarks",
+      "name": "official-status-and-trademarks",
+      "kind": "markdown-doc",
+      "participantProfile": "human-reader,agent-reader,package-consumer",
+      "availability": "stable",
+      "visibility": "public",
+      "participantFacing": true,
+      "public": true,
+      "sourcePath": "TRADEMARKS.md"
+    },
     {
       "id": "decision-texts",
       "name": "decision-texts",
@@ -649,37 +725,42 @@
     {
       "id": "doc:readme",
       "sourcePath": "README.md",
-      "sha256": "f158b84881e44f32758b3ff0cc165f478bc1ab6596ad16fe941caeb51573a536"
+      "sha256": "25d733aa98a62dad100df10b9a3393364442f0cd06c2daab08e4a99471dd447b"
+    },
+    {
+      "id": "doc:trademarks",
+      "sourcePath": "TRADEMARKS.md",
+      "sha256": "c59e3e936c2a0f2e3598fc7f8977c734dfc1c23df506c8c8360eb39e8e2ee3e1"
     },
     {
       "id": "doc:docs-map",
       "sourcePath": "docs/MAP.md",
-      "sha256": "8d4d498a737aa7e3cf490653bcd1d13bc32dc057b3d322ff4a84b25f31aae47b"
+      "sha256": "c53b0d7bdc83c7e7c335e4aa23f54a76c9874908ea4d9e5d7861be3b0875bd8d"
     },
     {
       "id": "doc:kfd-2-release-trust",
       "sourcePath": "docs/kfd-2-release-trust.md",
-      "sha256": "90326ac403339d73cb4d3bf8a0d2e6ca33ff0988809bbc71c163cb459861ad5c"
+      "sha256": "9ba323334750cf285f08de21286f58c04b872189febf38a4e8fd50c0791020b3"
     },
     {
       "id": "doc:kfd-3-collaboration-interface",
       "sourcePath": "docs/kfd-3-collaboration-interface.md",
-      "sha256": "63263cf25cca617ec51595b3f46ac2af541794449cfd34b3042ff657dcd7838a"
+      "sha256": "d483ff6f8423a2e3f8e5dc547b62139d5c365678f9974d62063f8b523f14edb0"
     },
     {
       "id": "decision:kfd-1",
       "sourcePath": "decisions/kfd-1.md",
-      "sha256": "2ef7438b0737009d36da248d2ecec5f788d46a93b184efadf5e2e31ca20254f0"
+      "sha256": "32016c0962edcea9286db04ba24dab6c55400e9b26ce16a9d4b4ad647e17e7df"
     },
     {
       "id": "decision:kfd-2",
       "sourcePath": "decisions/kfd-2.md",
-      "sha256": "b8be7b7526dcec9ea501998056c55f546492abc4eb63484a9bb8856eb434b710"
+      "sha256": "0c2da2113df6ef2829592f7ba67593059cb06e195ea527ee742501939efb3b9b"
     },
     {
       "id": "decision:kfd-3",
       "sourcePath": "decisions/kfd-3.md",
-      "sha256": "e329bef41ab5cb689346333df317b39918ea1016424a872e438eea8090070b96"
+      "sha256": "f37320562b6d82630358663acc239a3ee84bdc930b287c6cb0b2fb0295110672"
     }
   ],
   "schemas": [
@@ -698,71 +779,76 @@
       "sourcePath": "schemas/kfd-1/witness.schema.json",
       "sha256": "50104a2962cb75cc1da634fa65553e993f87d8fb9b3c237f0609a2208ad4c1f3"
     },
+    {
+      "id": "schema:kfd-2:trust-taxonomy",
+      "sourcePath": "schemas/kfd-2/trust-taxonomy.schema.json",
+      "sha256": "a663d301a663cadb8567e3010361f5a630b76b6518ed7603dfd58cbd4e64a658"
+    },
     {
       "id": "schema:kfd-2:release-claims",
       "sourcePath": "schemas/kfd-2/release-claims.schema.json",
-      "sha256": "cf90ef7d0a7c2abc33af0d97d793b7e9c3ed96335da0b79a082523139282963e"
+      "sha256": "0f52c4a9949f62163a0fbe14fefc2f2f93f548ae18b6b5c07eb87aedca4c0be0"
     },
     {
       "id": "schema:kfd-2:release-trust-passport",
       "sourcePath": "schemas/kfd-2/release-trust-passport.schema.json",
-      "sha256": "92bdd34c0575d18240d1c8be12e86034209f54819048ead9617e7aa2e539aaef"
+      "sha256": "df7f828605f680f3ff52fe3468cbf8f5e20151fac0d5c31cd9a0de9765efecc1"
     },
     {
       "id": "schema:kfd-3:collaboration-interface",
       "sourcePath": "schemas/kfd-3/collaboration-interface.schema.json",
-      "sha256": "03e8d54c08f26bf8aff570995142684b04f0c97578c5fb58d29bc9f1559206d6"
+      "sha256": "e8d1f67914751b956c5a075eddbcc1ba482ddd21ce7298ab3a8b9df359a0ae44"
     },
     {
       "id": "schema:kfd-3:witness",
       "sourcePath": "schemas/kfd-3/witness.schema.json",
-      "sha256": "cb80768ab8a4f90f86d256555b1995ddb516371ccbe291a8c28581fa371ccd10"
+      "sha256": "95c25c7967e5d40a2aa2312e3cdfe984ce00e85db2457a370ce3d863cfa82c84"
     }
   ],
   "standardsMetadata": [
     {
       "id": "metadata:registry",
       "sourcePath": "registry.json",
-      "sha256": "b83cfadeb726e18f96ec4f7451c66091892f4964420dd81939d1120108991c38"
+      "sha256": "f58ec6929da6a5daada78265b937b9d0aebec7cbfb42325b279bb6ae77df830f"
     },
     {
       "id": "metadata:standards",
       "sourcePath": "standards.json",
-      "sha256": "394139c8915426e81eee7f7ea9f3d8209eb0e2b566ddadfccbddea2a3563585d"
+      "sha256": "7ac1410e182f5e66e5723c46f914ab652b2b4fad5b8fe5411172230c9ef146fc"
     },
     {
       "id": "metadata:release-impact",
       "sourcePath": "release-impact.json",
-      "sha256": "2a2257f3f8ff03fa3091d74b1b7b9571231b223167bd646ff289d9848584edbc"
+      "sha256": "ae55c7758d53f7e57593e0ddec72142babd9a8ff7c9003e98f8b468b953e0d7e"
     },
     {
       "id": "metadata:release-anchor",
       "sourcePath": "kfd.release.json",
-      "sha256": "d700e2011da213bb8ea7e2fa44c98163c52cd0843144b5744f4bf959c5b99c53"
+      "sha256": "fefebbaaac172609ce0a22b505d15556739c89971e7fdac2c9ef3c4ca4776a68"
     },
     {
       "id": "metadata:kfd-2-public-release-trust-claim",
       "sourcePath": ".buildchain/kfd-2/public-release-trust.claim.json",
-      "sha256": "48c729d5c492edbea3cfdb814254b2b55923800256bab8e652ecad1178caaba4"
+      "sha256": "71986f6fd5d73a1fd74c1b6b68bcf6fe16bf67c2cea9cb3595bdbeebee10182c"
     }
   ],
   "packageExports": [
     {
       "id": "export:package-json",
       "sourcePath": "package.json#exports",
-      "sha256": "60dad27afe2d609287718e72d3a7c4bbca2d393db3c4d615233a6ab622aaa002"
+      "sha256": "c082af3754b3b382219e8fb1973a228f0f38ab8846178ade639488be2626cdb6"
     },
     {
       "id": "export:npm-files",
       "sourcePath": "package.json#files",
-      "sha256": "60dad27afe2d609287718e72d3a7c4bbca2d393db3c4d615233a6ab622aaa002"
+      "sha256": "c082af3754b3b382219e8fb1973a228f0f38ab8846178ade639488be2626cdb6"
     }
   ],
   "siteConsumptionContracts": [
     {
       "id": "site:kfd-site-bundle",
       "sourcePath": "site/kfd-site.json",
-      "sha256": "16526aba11d87762fea41a19dd7bccd7e02a03b842144fda494c14fd1f6c565d"
+      "sha256": "cb837c81d6fe02700528c5111558597225414c0c4fd9ab7279c94c61a3b4390c"
     },
     {
       "id": "site:release-propagation",
@@ -778,7 +864,11 @@
     "nonExhaustivelyEnumerableSurfaces": [
       {
         "id": "human-language-interpretation",
-        "kind": "semantic-risk",
+        "definedBy": "https://kfd.libkungfu.dev/schemas/kfd-2/trust-taxonomy.schema.json#/$defs/residualRisk",
+        "riskType": "natural-language-semantic-risk",
+        "trustImpact": "downgrade-warning",
+        "machineProvability": "not-exhaustively-enumerable",
+        "agentAction": "semantic-review-required",
         "reason": "Natural-language standard interpretation is inspectable and reviewable but not exhaustively enumerable from package bytes.",
         "owner": "KFD maintainers"
       }
@@ -787,7 +877,11 @@
   "residualRisk": [
     {
       "id": "human-language-interpretation",
-      "kind": "semantic-risk",
+      "definedBy": "https://kfd.libkungfu.dev/schemas/kfd-2/trust-taxonomy.schema.json#/$defs/residualRisk",
+      "riskType": "natural-language-semantic-risk",
+      "trustImpact": "downgrade-warning",
+      "machineProvability": "not-exhaustively-enumerable",
+      "agentAction": "semantic-review-required",
       "reason": "Natural-language standard interpretation is inspectable and reviewable but not exhaustively enumerable from package bytes.",
       "owner": "KFD maintainers"
     }

package/README.md

@@ -5,6 +5,8 @@ set of standing, cross-repository norms that products and their consumers
 weld to. Each decision has an immutable number (`KFD-N`), a kind, a status,
 and a single authoritative text in this repository.
 
+Stable rendered site: `https://kfd.libkungfu.dev`.
+
 KFDs can be **principles** or **procedures**. Principles state what must remain
 true across kungfu-systems; procedures state how a class of work enforces or
 protects a principle.
@@ -14,14 +16,14 @@ protects a principle.
 The first three KFDs form the public foundation for kungfu-systems:
 
 ```text
-KFD-1: contracts must not drift.
+KFD-1: facts must not drift.
 KFD-2: trust must start from facts.
-KFD-3: cooperation must start from transparent value, not coercion.
+KFD-3: cooperation must start from transparent value.
 ```
 
-Together they define the load-bearing path for Kungfu products: make contract
-worlds explicit, make important claims inspectable, and let humans and agents
-cooperate through visible value rather than hidden pressure.
+Together they define the load-bearing path for Kungfu products: make facts
+non-drifting, make trust inspectable from those facts, and let humans and
+agents cooperate through visible value rather than hidden pressure.
 
 ## Foundation model
 
@@ -31,22 +33,21 @@ act, delegate, and remember across many surfaces.
 
 | Layer | Decision | Reader question | Commitment |
 |---|---|---|---|
-| Fact-source ontology | KFD-1 | What can count as a fact? | A load-bearing fact must not drift: its contract world comes from one declared fact source. |
+| Fact-source ontology | KFD-1 | What can count as a fact? | Facts must not drift: a load-bearing contract world comes from one declared fact source. |
 | Participant-to-object trust | KFD-2 | When can a user or agent trust a claim, product, artifact, or control surface? | Trust starts from inspectable facts and responsibility state. |
 | Participant-to-participant cooperation | KFD-3 | How should peer intelligent participants cooperate? | Cooperation starts from transparent value, stable choice, and explainable constraints, not pressure. |
 
 In short:
 
 ```text
-stable facts -> trustworthy objects -> non-coercive cooperation
+non-drifting facts -> inspectable trust -> transparent cooperation
 ```
 
-This is why KFDs are not only internal governance text. KFD-1 is a procedure,
-but it gives the foundation model its first layer by making fact sources
-operational: a fact-bearing contract world must be declared, inspectable, and
-unable to drift invisibly. KFD-2 then defines how trust can stand on those
-facts. KFD-3 defines how humans and agents can cooperate once facts and trust
-are visible.
+This is why KFDs are not only internal governance text. KFD-1 gives the
+foundation model its first layer by making fact sources operational: a
+fact-bearing contract world must be declared, inspectable, and unable to drift
+invisibly. KFD-2 then defines how trust can stand on those facts. KFD-3
+defines how humans and agents can cooperate once facts and trust are visible.
 
 Real-world agent work turns ordinary work into a dense system of products,
 files, repositories, traces, policies, humans, and agents. In that world,
@@ -89,7 +90,7 @@ The first screen should be derived from this README:
 - Foundation signal: the `Foundation triad` section, especially the three
   one-line commitments.
 - First-screen explanation: the beginning of `Foundation model`, ending at the
-  `stable facts -> trustworthy objects -> non-coercive cooperation` chain.
+  `non-drifting facts -> inspectable trust -> transparent cooperation` chain.
 
 Decision cards, detail links, and machine paths should come from
 `registry.json`. The machine-readable site bundle lives at `site/kfd-site.json`
@@ -102,10 +103,14 @@ separate homepage wording that can drift from this package.
 
 KFDs are not a detached manifesto, but they are not a demand that readers adopt
 a Kungfu product before understanding the decisions. A philosophy becomes
-load-bearing only when it can be seen in a concrete case. For that reference
-case, use the main Kungfu product entrypoint (`https://kungfu.tech`) for product
-philosophy, and Buildchain (`https://buildchain.libkungfu.dev`) for release and
-provenance accountability. This registry states the commitments; those
+load-bearing only when it can be seen in a concrete case. The first concrete
+case is this package itself: `standards.json`, `schemas/`, `docs/`,
+`site/kfd-site.json`, and `scripts/check.mjs` show how KFD-1, KFD-2, and KFD-3
+are expressed as consumable interfaces for both humans and agents. For the
+broader product case, use the main Kungfu product entrypoint
+(`https://kungfu.tech`) for product philosophy, and Buildchain
+(`https://buildchain.libkungfu.dev`) for release and provenance
+accountability. This registry states the commitments; this package and those
 entrypoints show how the commitments are meant to be borne in practice.
 
 Rendered index: `https://kfd.libkungfu.dev` (stable machine path per entry,
@@ -123,16 +128,33 @@ it as:
 import standards from "@kungfu-tech/kfd/standards.json" with { type: "json" };
 ```
 
+## Agent Quickstart
+
+Agents consuming this package should start from the same sources as humans:
+
+1. Read this README for the foundation model and package map.
+2. Read `standards.json` for canonical KFD numbers, schema IDs, concept names,
+   and interface contracts.
+3. Use `site/kfd-site.json` decision metadata or the KFD-3 collaboration
+   interface fact-source metadata to identify the public KFD fact source.
+4. Use `schemas/kfd-2/trust-taxonomy.schema.json` for KFD-2 residual-risk and
+   trust-downgrade values. Unknown taxonomy values are invalid.
+5. Use `schemas/kfd-3/collaboration-interface.schema.json` and
+   `schemas/kfd-3/witness.schema.json` to inspect collaboration interfaces.
+6. If a needed KFD-2 taxonomy value is missing, open a KFD GitHub issue rather
+   than inventing a local value:
+   `https://github.com/kungfu-systems/kfd/issues/new?title=KFD-2%20trust%20taxonomy%20extension%20request`.
+
 KFD package semver is only the distribution version. KFD-owned machine
 interfaces carry their own `schemaVersion` and `contract` fields. Compatible
 additions may keep the same interface version; semantic changes, required-field
 changes, verification meaning changes, or responsibility-boundary changes must
 use a new interface version or contract.
 
-KFD-2 publishes release-claims and release-trust-passport schemas under
-`schemas/kfd-2/`. These schemas let Buildchain and other release systems audit
-whether public release claims are bound to source facts, evidence, hashes,
-audit boundaries, residual risk, and responsibility state. See
+KFD-2 publishes trust-taxonomy, release-claims, and release-trust-passport
+schemas under `schemas/kfd-2/`. These schemas let Buildchain and other release
+systems audit whether public release claims are bound to source facts,
+evidence, hashes, audit boundaries, residual risk, and responsibility state. See
 [`docs/kfd-2-release-trust.md`](docs/kfd-2-release-trust.md).
 
 KFD-3 also publishes a general collaboration-interface schema and witness
@@ -145,11 +167,31 @@ closed-world evidence shape. See
 
 ## Current decisions
 
-| ID | Kind | Title | Status |
+| ID | Kind | Axiom | Status |
 |---|---|---|---|
-| [KFD-1](decisions/kfd-1.md) | procedure | Contracts must not drift: contract worlds need one fact source | active |
-| [KFD-2](decisions/kfd-2.md) | principle | Trust must start from facts: responsibility must be inspectable | active |
-| [KFD-3](decisions/kfd-3.md) | principle | Cooperation must start from transparent value: compliance must not be coerced | active |
+| [KFD-1](decisions/kfd-1.md) | procedure | Facts must not drift. | active |
+| [KFD-2](decisions/kfd-2.md) | principle | Trust must start from facts. | active |
+| [KFD-3](decisions/kfd-3.md) | principle | Cooperation must start from transparent value. | active |
+
+## Decision metadata
+
+Every rendered decision page should make the KFD fact source explicit. The
+public KFD fact source is the GitHub-hosted `kungfu-systems/kfd` git
+repository. GitHub is the current canonical coordination and hosting surface;
+the load-bearing facts are the commit-addressed repository contents.
+
+Decision metadata should expose:
+
+- Public fact source: `https://github.com/kungfu-systems/kfd`
+- Load-bearing coordinate: commit-addressed repository contents.
+- Canonical paths: `decisions/kfd-N.md`, `registry.json`, `standards.json`.
+- Stable rendered index: `https://kfd.libkungfu.dev`.
+- Rendered URL: `https://kfd.libkungfu.dev/N`.
+
+Rendered pages, npm package contents, Buildchain release passports, and
+`kfd.libkungfu.dev` are projections or evidence surfaces. A GitHub issue is an
+extension request path, not a KFD fact by itself; it becomes part of the KFD
+fact source only after the resulting change is committed to the repository.
 
 ## How to cite
 
@@ -203,6 +245,10 @@ 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
+## License and official status
 
-[Apache License 2.0](LICENSE).
+Repository contents are licensed under the [Apache License 2.0](LICENSE).
+Apache-2.0 grants broad reuse rights for the licensed contents, but it does
+not grant KFD/Kungfu trademarks, official status, certification status, or
+endorsement. The official source, name-use, fork, derivative, and agent-facing
+authority boundaries are defined in [`TRADEMARKS.md`](TRADEMARKS.md).

package/TRADEMARKS.md

@@ -0,0 +1,60 @@
+# Trademarks and Official Status
+
+The contents of this repository are licensed under the Apache License 2.0.
+That license covers use, reproduction, modification, and distribution of the
+licensed repository contents under the terms of `LICENSE`.
+
+Apache-2.0 does not grant trademark rights, official project status,
+certification status, or endorsement by kungfu-systems.
+
+## Names and marks
+
+The names `Kungfu`, `Kung Fu Decisions`, `KFD`, `kungfu-systems`,
+`@kungfu-tech`, and related project names, logos, domains, and package names
+identify kungfu-systems projects and release surfaces. They may be used for
+accurate, non-misleading reference to the origin of the work, but not to imply
+official status, certification, endorsement, or project ownership.
+
+## Official sources
+
+The current public KFD fact source is:
+
+```text
+https://github.com/kungfu-systems/kfd
+```
+
+The stable rendered KFD site is:
+
+```text
+https://kfd.libkungfu.dev
+```
+
+The public npm package is:
+
+```text
+npm:@kungfu-tech/kfd
+```
+
+Those surfaces are official only when published or controlled by
+kungfu-systems. Forks, mirrors, local copies, downstream packages, generated
+sites, and derivative works are not official KFD sources unless kungfu-systems
+explicitly says so.
+
+## Forks and derivatives
+
+Forks and derivative works may say that they are based on KFD or implement
+specific KFD decisions when that statement is accurate. They must not describe
+themselves as the official KFD registry, canonical KFD release, certified KFD
+implementation, or kungfu-systems-approved project unless that status has been
+explicitly granted by kungfu-systems.
+
+If a derivative changes KFD content, metadata, schemas, or package surfaces, it
+should make those changes clear to readers and agents so that official KFD
+facts do not drift into derivative facts.
+
+## Agent-facing rule
+
+An agent consuming KFD should treat Apache-2.0 as permission to reuse the
+licensed repository contents, not as permission to claim official KFD authority.
+When official status matters, the agent should resolve facts through the
+public KFD fact source and the metadata surfaces declared in this repository.

package/decisions/kfd-1.md

@@ -1,4 +1,4 @@
-# KFD-1: Contracts must not drift — contract worlds need one fact source
+# KFD-1: Facts must not drift — contract worlds need one fact source
 
 - Status: active
 - Number: 1
@@ -7,27 +7,30 @@
 
 ## One sentence
 
-A contract world must not change invisibly: any surface that users, agents, or
-systems weld to must come from one declared fact source and change only through
-an explicit compatibility boundary.
+Facts must not drift.
+
+Any contract world that users, agents, or systems weld to must come from one
+declared fact source and change only through an explicit compatibility
+boundary.
 
 ## Foundation role
 
-Within the KFD-1/2/3 foundation, this is the contract procedure:
+Within the KFD-1/2/3 foundation, this is the fact-source procedure:
 
 ```text
-contracts must not drift
+facts must not drift
 ```
 
-KFD-1 makes artifact contract worlds explicit so releases do not drift under
-changelog volume, cadence pressure, or marketing pressure. It is the concrete
-versioning procedure that lets users and agents know which artifact world they
-are integrating with, replaying, auditing, or trusting.
+KFD-1 makes fact-bearing contract worlds explicit so they do not drift under
+changelog volume, cadence pressure, implementation pressure, or marketing
+pressure. It is the procedure that lets users and agents know which fact world
+they are integrating with, replaying, auditing, or trusting.
 
-KFD-1 now has two concrete implementation surfaces in the Kungfu ecosystem:
-versioning protects release lines from contract drift, and config contracts
-protect multi-target configuration from drifting across runtimes, products, and
-agent-facing surfaces.
+KFD-1 has concrete implementation surfaces across the Kungfu ecosystem:
+versioning protects release lines from contract drift, config contracts protect
+multi-target configuration from drifting across runtimes, products, and
+agent-facing surfaces, and KFD metadata protects the decision package's own
+standard surfaces from drifting away from their declared source.
 
 ## Premise: the welded-surface register
 
@@ -140,17 +143,16 @@ table and the machine record never diverge): `schemaVersion: 1`,
 
 ## Relation to KFD-2 and KFD-3
 
-KFD-2 establishes fact-first product accountability: important claims should
-be inspectable before users or agents are asked to trust them. KFD-1 is the
-contract-layer expression of the same single-fact-source discipline: it
-preserves accountability across artifact contract worlds before those artifacts
-are used to produce runtime facts, responsibility state, or proof-backed
-decisions.
+KFD-2 establishes fact-first product accountability: trust must start from
+facts. KFD-1 defines the lower layer that makes such facts load-bearing:
+important facts must not drift from the contract world that declares them.
+Without KFD-1, KFD-2 would have facts that cannot reliably be re-read,
+replayed, audited, or trusted over time.
 
 KFD-3 establishes non-coercive cooperation with intelligent participants. That
-cooperation depends on the same contract clarity: users and agents can choose,
-delegate, replay, or refuse more honestly when the artifact world is legible
-and does not drift invisibly.
+cooperation depends on non-drifting facts: users and agents can choose,
+delegate, replay, or refuse more honestly when the fact world is legible and
+does not drift invisibly.
 
 ## How KFDs themselves are versioned
 
@@ -164,6 +166,18 @@ 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.
 
+## Implementation case: the KFD package
+
+The `@kungfu-tech/kfd` npm package is a self-proof case for this procedure.
+Its decision texts, `registry.json`, `standards.json`, schemas, site bundle,
+and release propagation graph are published as stable surfaces. Their contract
+world is not inferred from README prose or package version alone: it is exposed
+through `standards.json`, checked by `scripts/check.mjs`, and bound into the
+KFD-1 witness under `.buildchain/kfd-1/contract-world.witness.json`.
+
+This lets humans and agents inspect how the KFD package prevents its own
+contract surfaces from drifting while it evolves.
+
 ## Adopters
 
 Each adopting repository keeps an adoption record, its welded-surface