@kungfu-tech/kfd 1.0.0-alpha.18 → 1.0.0-alpha.19

package/README.md

@@ -73,7 +73,25 @@ systems. KFD is part of that bootstrap: the worldview is forged through the same
 transparent and inspectable mechanisms it asks products to provide.
 
 This README states the architecture; KFD-1, KFD-2, and KFD-3 provide the
-detailed rules.
+foundation rules.
+
+## Practice guidelines
+
+KFDs after the foundation triad may define practice guidelines: procedures
+that apply the foundation to a specific class of real-world product behavior.
+They do not expand the foundation triad; they show how the foundation behaves
+when a product must make a concrete kind of reality legible.
+
+| Layer | Decision | Reader question | Commitment |
+|---|---|---|---|
+| Perspective-bearing views | KFD-4 | How should a product show time, history, replay, sync, or mixed-source work state? | Timelines must declare their observer: a useful view states who is observing, which facts were accepted, and how concurrent facts were projected. |
+
+KFD-4 is the first such guideline. It applies KFD-1/2/3 to the problem of
+perspective and timeline order. In a multi-machine or multi-agent world, a
+product should not pretend to own a universal global clock. It should preserve
+non-drifting facts, make trust start from those facts, and let participants
+cooperate by exposing the observer, accepted ranges, causal constraints, and
+projection policy behind the view.
 
 ## Adoption boundary
 
@@ -102,6 +120,8 @@ The first screen should be derived from this README:
 - First-screen explanation: the beginning of `Foundation model`, ending at the
   `non-drifting facts -> inspectable trust -> trusted value -> voluntary
   cooperation` chain.
+- Practice signal: the `Practice guidelines` section, starting with KFD-4 as
+  the declared-observer rule for perspective-bearing timeline views.
 
 Decision cards, detail links, and machine paths should come from
 `registry.json`. The machine-readable site bundle lives at `site/kfd-site.json`
@@ -124,9 +144,9 @@ 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. 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
+`site/kfd-site.json`, and `scripts/check.mjs` show how KFD-1, KFD-2, KFD-3,
+and KFD-4 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
@@ -184,6 +204,11 @@ KFD-3. The KFD-owned boundary is the standard vocabulary, schema IDs, and
 closed-world evidence shape. See
 [`docs/kfd-3-collaboration-interface.md`](docs/kfd-3-collaboration-interface.md).
 
+KFD-4 publishes an observer-perspective schema under `schemas/kfd-4/`. It gives
+humans and agents a standard vocabulary for observer, accepted facts,
+projection policy, causal constraints, degraded evidence, and verification
+state when a product shows a perspective-bearing timeline.
+
 ## Current decisions
 
 | ID | Kind | Axiom | Status |
@@ -191,6 +216,7 @@ closed-world evidence shape. See
 | [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 trusted value. | active |
+| [KFD-4](decisions/kfd-4.md) | procedure | Timelines must declare their observer. | active |
 
 ## Decision metadata
 

package/buildchain.contract-lock.json

@@ -3,13 +3,13 @@
   "contract": "kungfu-buildchain-contract-lock",
   "buildchain": {
     "ref": "v2",
-    "resolvedSha": "93a42bdfbf60f32fc24e5cc6640f5352eec97224",
+    "resolvedSha": "aa039c39e7d5a5a74d078025a21a47676fadca82",
     "contract": "kungfu-buildchain-runtime-contract-world",
-    "contractDigest": "sha256:7b2fed2dacdf37234ca03e656904611b9c3dd48a4f229be387c7c1393f57fc5b",
-    "compatibilityDigest": "sha256:36421b592a782decbfe31a7d8d42d70ce1100a56a2c4f4a0ccc21f0617dc72bf",
+    "contractDigest": "sha256:590724458a59dfed521c876c24cedec43124409b4be79f4ce839ce26ce9f98de",
+    "compatibilityDigest": "sha256:407d6d5ee6a96a34d2cc30db9ac64cf4b1819ab6d77bd7a57a07a124f22101ca",
     "majorLine": "v2",
     "compatibilityPolicy": "major-compatible",
-    "acceptedAt": "2026-07-07T09:29:33.317Z",
+    "acceptedAt": "2026-07-08T02:03:03.789Z",
     "surfaces": [
       {
         "id": "reusable-build",
@@ -21,6 +21,11 @@
         "kind": "workflow",
         "breakingDigest": "sha256:403d2fcdb0c5eabe749e89102defad69745f70a1556707bec7831fcc2e9fa8f8"
       },
+      {
+        "id": "web-surface",
+        "kind": "workflow",
+        "breakingDigest": "sha256:82ee63cb336e40d832dfff4a1c5e6cbfa221a4fc8b2359990033bc931bffc43a"
+      },
       {
         "id": "promote-buildchain-ref-action",
         "kind": "action",
@@ -54,7 +59,17 @@
       {
         "id": "buildchain-cli",
         "kind": "cli",
-        "breakingDigest": "sha256:097db3e67509bedda8c6548bf1edfbfcf57f7b5510520b6a7b7e078d7ec087c8"
+        "breakingDigest": "sha256:90a73892b2d6c214048448d5f45df75639bdf7b7e8fefd9c596e04b087407bcc"
+      },
+      {
+        "id": "homebrew-distribution-index",
+        "kind": "node-api",
+        "breakingDigest": "sha256:148c0387ff4cea76433bbde80cd9d77c5aa67e1a29856ced33e4d819366f2213"
+      },
+      {
+        "id": "readme-badge-facts",
+        "kind": "node-api",
+        "breakingDigest": "sha256:bcd72ad6dfba8013c96f8b2f7b0a307d2e7713972a1219348f0d5ecc493939a0"
       },
       {
         "id": "agent-manual-registry",

package/decisions/kfd-4.md

@@ -0,0 +1,182 @@
+# KFD-4: Timelines must declare their observer — useful views need a stated perspective
+
+- Status: active
+- Number: 4
+- Kind: procedure
+- Applies to: every kungfu-systems product, repository, release surface, extension surface, hosted surface, and agent-facing interface that represents time, ordering, history, timelines, sync, replay, or mixed-source work facts
+
+## One sentence
+
+Timelines must declare their observer.
+
+A product must not present a mixed-source ordering as an absolute view from
+nowhere. A useful view of reality must state who is observing, which facts were
+accepted, and how concurrent facts were projected.
+
+## Decision type
+
+KFDs can be principles or procedures:
+
+- A **principle** states what must remain true across kungfu-systems even as
+  products, repositories, and release lines change.
+- A **procedure** states how a class of work enforces or protects a principle.
+
+This KFD is a procedure. It is not a fourth foundation principle beside
+KFD-1/2/3. It is the first practice guideline derived from the foundation
+triad: once facts are non-drifting, trust starts from facts, and cooperation
+starts from trusted value, a product still has to say from which perspective a
+time-ordered view is being offered.
+
+## Practice role
+
+Within the KFD structure, KFD-1/2/3 form the foundation:
+
+```text
+facts must not drift
+  -> trust must start from facts
+  -> cooperation must start from trusted value
+```
+
+KFD-4 applies that foundation to perspective, ordering, and action. It answers
+this practice question:
+
+```text
+In a complex world, from which declared perspective is this view useful,
+stable, and trustworthy?
+```
+
+## Procedure
+
+When a product combines facts from multiple machines, agents, processes,
+sessions, sources, repositories, providers, or external systems, it should
+treat the visible timeline as an observer-relative projection over accepted
+facts, not as a claim that the product has found one absolute global clock.
+
+The authoritative record should be facts and evidence:
+
+- source-local records and their local order;
+- provenance for source, participant, location, session, run, or adapter;
+- accepted ranges, heads, cursors, watermarks, and capture boundaries;
+- causal links between observations, decisions, actions, and results;
+- payload hashes, schema bindings, receipts, redaction states, and verification
+  results.
+
+The visible timeline is a view over those facts. Its perspective must be
+declared enough that another human or agent can reproduce the same view from
+the same accepted facts.
+
+## What a declared perspective should include
+
+A perspective-bearing timeline should identify, where applicable:
+
+- the observer or observer location whose view is being presented;
+- the accepted fact sources, ranges, watermarks, and freshness boundaries;
+- the projection policy version;
+- the ordering rule for concurrent or causally unrelated facts;
+- the deterministic tie-breaker used when policy and source-local order are not
+  enough;
+- the degraded state when causality, payloads, schemas, accepted ranges, or
+  freshness are incomplete.
+
+Causal facts dominate projection policy. A product may order concurrent facts
+by observer policy, source priority, or deterministic tie-breaker, but it must
+not invert a known causal dependency. If it cannot produce a valid total order
+without hiding missing causality or missing evidence, it should report a
+degraded view rather than silently sorting by wall-clock time.
+
+## What it requires
+
+- GUI, CLI, API, export, and agent-facing timeline surfaces should make the
+  observer or projection policy inspectable when they mix sources.
+- Wall-clock time may be used for display, latency, diagnostics, and
+  source-local ordering, but it must not be the only proof of cross-source
+  order.
+- Exported bundles that claim a timeline order should carry enough perspective
+  metadata for another consumer to reproduce that order.
+- Storage and sync systems should preserve source provenance, accepted ranges,
+  and causal links rather than flattening remote facts into anonymous local
+  records.
+- Fsck, release gates, or other verification systems should eventually be able
+  to check that a projected view does not contradict known facts, invert known
+  causality, or hide an incomplete accepted range.
+
+## What it does not require
+
+- It does not say there are no facts. Facts and causality remain load-bearing.
+- It does not permit arbitrary narratives, invented evidence, or convenient
+  ordering.
+- It does not require a universal global clock, a permanent global sequencer,
+  or distributed consensus for every timeline.
+- It does not forbid a product from having a default observer policy.
+- It does not solve conflicts between independently written authority roots.
+  Conflict policy must be explicit when it exists.
+- It does not supersede KFD-1, KFD-2, or KFD-3. It applies them to
+  perspective-bearing views.
+
+## Relation to KFD-1, KFD-2, and KFD-3
+
+KFD-1 says facts must not drift. KFD-4 depends on that: a perspective-bearing
+timeline must stand on accepted facts, not on a driftable story.
+
+KFD-2 says trust must start from facts. KFD-4 applies that to ordering: trust
+in a timeline comes from reproducibility under declared facts and declared
+projection policy, not from an undeclared claim to absolute time.
+
+KFD-3 says cooperation must start from trusted value. KFD-4 applies that to
+multi-participant work: humans and agents may carry different perspectives,
+but cooperation becomes possible when those perspectives expose their facts,
+constraints, and view policies instead of forcing everyone into a hidden
+ordering.
+
+Together:
+
+```text
+KFD-1: facts must not drift.
+KFD-2: trust must start from facts.
+KFD-3: cooperation must start from trusted value.
+KFD-4: timelines must declare their observer.
+```
+
+The first three define the foundation. KFD-4 is a practice guideline for how
+that foundation behaves when a product shows time, history, replay, sync, or
+mixed-source work state.
+
+## Implementation case: Kungfu observer timelines
+
+Kungfu's observer-relative timeline design is the first concrete product case.
+Kungfu stores causal runtime facts, source provenance, accepted ranges,
+manifests, payload evidence, and verification results. A mixed-source timeline
+is a deterministic projection from an explicit observer policy; it is not a
+claim that Kungfu has discovered one universal global clock.
+
+That design lets a local user sync facts from another machine, inspect agent
+work that happened elsewhere, and still ask precise questions:
+
+```text
+which facts did this observer accept?
+which source or location did each fact come from?
+which causal links constrain the order?
+which concurrent facts were ordered by policy?
+can another consumer reproduce the same view?
+```
+
+This is the product-level form of the KFD-4 procedure.
+
+## Implementation case: the KFD package
+
+The `@kungfu-tech/kfd` npm package publishes a KFD-4 observer-perspective
+schema under `schemas/kfd-4/observer-perspective.schema.json`. The schema is
+not a mandatory runtime data model for every adopter. It is the KFD-owned
+vocabulary for declaring observer, accepted facts, projection policy, causal
+constraints, and degraded evidence state in products that need a
+perspective-bearing timeline.
+
+## Adopters
+
+Each adopting repository cites this KFD when designing or changing a timeline,
+history view, replay view, source sync flow, multi-machine view, multi-agent
+view, audit bundle, or exported record that orders facts from more than one
+source or perspective.
+
+Adopters should keep local implementation detail in repository documents and
+reference this KFD rather than restating it.

package/docs/MAP.md

@@ -5,8 +5,11 @@
 | What is KFD, and what decisions exist? | [`../README.md`](../README.md) |
 | What is the KFD-1/2/3 foundation triad? | [`../README.md`](../README.md#foundation-triad) |
 | What worldview structure does the foundation triad express? | [`../README.md`](../README.md#foundation-model) |
+| What practice guidelines are derived from the foundation triad? | [`../README.md`](../README.md#practice-guidelines) |
+| How should a product show timeline order from a declared perspective? | [KFD-4](../decisions/kfd-4.md) |
+| What schema should products use for KFD-4 observer-relative timeline views? | [`../schemas/kfd-4/observer-perspective.schema.json`](../schemas/kfd-4/observer-perspective.schema.json) |
 | How should an agent quickly understand this package? | [`../README.md`](../README.md#agent-quickstart) |
-| What is the concrete self-proof case for KFD-1/2/3? | [`../README.md`](../README.md#product-proof-path) and the implementation case in each KFD |
+| What is the concrete self-proof case for KFD-1/2/3/4? | [`../README.md`](../README.md#product-proof-path) and the implementation case in each KFD |
 | Where is the public KFD fact source? | [`../README.md`](../README.md#decision-metadata) and [`../site/kfd-site.json`](../site/kfd-site.json) decision metadata |
 | What does Apache-2.0 cover, and what remains official/trademark-bound? | [`../TRADEMARKS.md`](../TRADEMARKS.md) |
 | What should a site renderer consume to render `kfd.libkungfu.dev`? | [`../site/kfd-site.json`](../site/kfd-site.json) |

package/kfd.release.json

@@ -4,7 +4,7 @@
   "line": "v1.0",
   "channel": "alpha",
   "npmPackage": "@kungfu-tech/kfd",
-  "npmVersion": "1.0.0-alpha.18",
+  "npmVersion": "1.0.0-alpha.19",
   "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.18",
+  "version": "1.0.0-alpha.19",
   "description": "Kung Fu Decisions (KFD): the kungfu-systems organization-wide decision registry, as a consumable artifact",
   "license": "Apache-2.0",
   "files": [

package/registry.json

@@ -31,6 +31,16 @@
       "status": "active",
       "path": "decisions/kfd-3.md",
       "url": "https://kfd.libkungfu.dev/3"
+    },
+    {
+      "number": 4,
+      "id": "KFD-4",
+      "slug": "kfd-4",
+      "title": "Timelines must declare their observer: useful views need a stated perspective",
+      "kind": "procedure",
+      "status": "active",
+      "path": "decisions/kfd-4.md",
+      "url": "https://kfd.libkungfu.dev/4"
     }
   ]
 }

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, KFD-1 document/interface integrity bindings, and the README-backed KFD site homepage projection 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-4 observer-perspective schema, 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 add the public adoption boundary that keeps KFD an engineering discipline rather than a belief test, while preserving the existing decision numbers and registry shape."
+      "rationale": "KFD documents are append-only content coordinates; current documentation changes add KFD-4 as a practice guideline for declared observer timelines, while preserving existing decision numbers and registry shape."
     },
     {
       "id": "kfd-registry-schema",
@@ -28,13 +28,13 @@
       "id": "kfd-standards-metadata",
       "impact": "minor",
       "class": "additive",
-      "rationale": "standards.json and schemas/ add the KFD-2 trust-taxonomy schema ID, release-claims and release-trust-passport schema IDs, explicit KFD-1/2/3 interface versions, KFD document SHA-256 bindings, KFD-owned concept names, KFD-3 fact-source interface metadata, and official-status interface metadata for downstream consumers."
+      "rationale": "standards.json and schemas/ add the KFD-2 trust-taxonomy schema ID, release-claims and release-trust-passport schema IDs, explicit KFD-1/2/3/4 interface versions, KFD-4 observer-perspective schema metadata, KFD document SHA-256 bindings, KFD-owned concept names, KFD-3 fact-source interface metadata, and official-status interface metadata for downstream consumers."
     },
     {
       "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, agent quickstart/self-proof documentation, Buildchain contract lock metadata, 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."
+      "rationale": "The npm package now publishes the KFD-2 trust taxonomy, KFD-2 schemas, KFD-2 documentation, KFD-3 self collaboration-interface witnesses, KFD-4 observer-perspective schema, TRADEMARKS.md, public fact-source metadata, agent quickstart/self-proof documentation, Buildchain contract lock metadata, 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-buildchain-contract-lock",
@@ -46,7 +46,7 @@
       "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, including the adoption-boundary homepage section, 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."
+      "rationale": "site/kfd-site.json now exposes generated README-backed homepage.sections and homepage.displayPlan fields, including the adoption-boundary and practice-guidelines homepage sections, 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",
@@ -73,5 +73,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, Buildchain contract lock metadata, 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."
+  "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/4 interface version metadata, KFD-3 self-verification witnesses, KFD-4 observer-perspective schema, Buildchain contract lock metadata, 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."
 }

package/schemas/kfd-4/observer-perspective.schema.json

@@ -0,0 +1,272 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://kfd.libkungfu.dev/schemas/kfd-4/observer-perspective.schema.json",
+  "title": "KFD-4 observer perspective",
+  "type": "object",
+  "required": [
+    "schemaVersion",
+    "contract",
+    "standard",
+    "id",
+    "observer",
+    "acceptedFacts",
+    "projectionPolicy",
+    "verification"
+  ],
+  "properties": {
+    "schemaVersion": {
+      "const": 1
+    },
+    "contract": {
+      "const": "kfd-4-observer-perspective"
+    },
+    "standard": {
+      "const": "kfd-4"
+    },
+    "id": {
+      "type": "string",
+      "minLength": 1
+    },
+    "observer": {
+      "$ref": "#/$defs/observer"
+    },
+    "acceptedFacts": {
+      "type": "array",
+      "items": {
+        "$ref": "#/$defs/acceptedFactSource"
+      },
+      "minItems": 1
+    },
+    "projectionPolicy": {
+      "$ref": "#/$defs/projectionPolicy"
+    },
+    "causalConstraints": {
+      "type": "array",
+      "items": {
+        "$ref": "#/$defs/causalConstraint"
+      },
+      "default": []
+    },
+    "degradedEvidence": {
+      "type": "array",
+      "items": {
+        "$ref": "#/$defs/degradedEvidence"
+      },
+      "default": []
+    },
+    "verification": {
+      "$ref": "#/$defs/verification"
+    }
+  },
+  "additionalProperties": false,
+  "$defs": {
+    "observer": {
+      "type": "object",
+      "required": [
+        "id",
+        "kind"
+      ],
+      "properties": {
+        "id": {
+          "type": "string",
+          "minLength": 1
+        },
+        "kind": {
+          "enum": [
+            "human",
+            "agent",
+            "runtime-location",
+            "product-view",
+            "service",
+            "other"
+          ]
+        },
+        "location": {
+          "type": "string"
+        },
+        "description": {
+          "type": "string"
+        }
+      },
+      "additionalProperties": false
+    },
+    "acceptedFactSource": {
+      "type": "object",
+      "required": [
+        "sourceId",
+        "sourceKind"
+      ],
+      "properties": {
+        "sourceId": {
+          "type": "string",
+          "minLength": 1
+        },
+        "sourceKind": {
+          "enum": [
+            "local-runtime",
+            "remote-runtime",
+            "imported-bundle",
+            "adapter",
+            "repository",
+            "release-artifact",
+            "external-system",
+            "other"
+          ]
+        },
+        "location": {
+          "type": "string"
+        },
+        "acceptedRange": {
+          "type": "string"
+        },
+        "watermark": {
+          "type": "string"
+        },
+        "manifest": {
+          "type": "string"
+        },
+        "freshness": {
+          "type": "string"
+        },
+        "provenance": {
+          "type": "string"
+        }
+      },
+      "additionalProperties": false
+    },
+    "projectionPolicy": {
+      "type": "object",
+      "required": [
+        "policyVersion",
+        "causalDominance",
+        "tieBreaker"
+      ],
+      "properties": {
+        "policyVersion": {
+          "type": "string",
+          "minLength": 1
+        },
+        "observerLocation": {
+          "type": "string"
+        },
+        "sourcePriority": {
+          "type": "array",
+          "items": {
+            "type": "string"
+          },
+          "default": []
+        },
+        "causalDominance": {
+          "const": true
+        },
+        "concurrentOrdering": {
+          "type": "string",
+          "description": "How concurrent or causally unrelated facts are ordered under this perspective."
+        },
+        "tieBreaker": {
+          "type": "string",
+          "minLength": 1
+        }
+      },
+      "additionalProperties": false
+    },
+    "causalConstraint": {
+      "type": "object",
+      "required": [
+        "before",
+        "after",
+        "basis"
+      ],
+      "properties": {
+        "before": {
+          "type": "string",
+          "minLength": 1
+        },
+        "after": {
+          "type": "string",
+          "minLength": 1
+        },
+        "basis": {
+          "enum": [
+            "causal-parent",
+            "trigger-frame",
+            "stream-topology",
+            "manifest-boundary",
+            "accepted-range",
+            "source-local-order",
+            "other"
+          ]
+        },
+        "evidence": {
+          "type": "string"
+        }
+      },
+      "additionalProperties": false
+    },
+    "degradedEvidence": {
+      "type": "object",
+      "required": [
+        "id",
+        "state",
+        "reason"
+      ],
+      "properties": {
+        "id": {
+          "type": "string",
+          "minLength": 1
+        },
+        "state": {
+          "enum": [
+            "missing-causality",
+            "missing-payload",
+            "missing-schema",
+            "stale-source",
+            "incomplete-range",
+            "unknown-policy-version",
+            "unverified-source",
+            "other"
+          ]
+        },
+        "reason": {
+          "type": "string",
+          "minLength": 1
+        },
+        "impact": {
+          "enum": [
+            "display-warning",
+            "trust-downgrade",
+            "view-invalid",
+            "action-required"
+          ]
+        }
+      },
+      "additionalProperties": false
+    },
+    "verification": {
+      "type": "object",
+      "required": [
+        "result"
+      ],
+      "properties": {
+        "result": {
+          "enum": [
+            "pass",
+            "degraded",
+            "fail",
+            "not-checked"
+          ]
+        },
+        "command": {
+          "type": "string"
+        },
+        "checkedAt": {
+          "type": "string"
+        },
+        "notes": {
+          "type": "string"
+        }
+      },
+      "additionalProperties": false
+    }
+  }
+}