artifacts/standard-named

WitnessKey / WitnessMark Context Resume

artifacts/standard-named/20260709__WITNESSKEY__COMPRESSION__CONTEXT-RESUME__v0__witness-mark-consent-provenance.md

Rendered from markdown source. Open raw source on GitHub.

WitnessKey / WitnessMark Context Resume

Date: 2026-06-18 Purpose: Compressed context packet for resuming a conversation about witness-rooted consent/provenance infrastructure without carrying the full live context.

---

0. Emotional / conceptual seed

The conversation began from consentful provenance and moved deeper. The key shift was from consent as the root to witness as the root.

Consent remains important, but consent is now understood as a later, more articulated form of witness. The most primitive need is not always to say, “I consent” or “I refuse,” but simply:

Something was witnessed here. This relation is no longer unmarked.

This matters because many consent-relevant signals are preverbal, uncertain, embodied, partial, or not-yet-articulated. A system that only respects cognitively clear, legally formed, machine-readable assertions will exploit the gap between sensation and speech.

Core realization:

Consent does not begin at clarity. Consent begins at witness.

---

1. Uploaded source / earlier model

The attached source document was titled “The Consent-Based Blocktree Model”, described as “Dreamed Into Structure by Father & Son.” It described a system of key-defined objects and parent-child links where permissions, constraints, and memories live on the relationship between objects, not inside the objects themselves.

Important source concepts:

  • There are infinitely many objects, each defined by public/private keys.
  • Objects can be linked, with one acting as parent and another as child.
  • Rules/actions/consents are stored on the connection between object and parent.
  • Actions are attempted across all relevant branches.
  • If any relevant parent-tree rule dissents, the action fails or is marked invalid.
  • When a child is no longer child of the parent, information on the link is locked, frozen, or destroyed.
  • The document included the phrase: “No consent loop can collapse.”

This phrase landed emotionally as structural support: a system that refuses false closure.

---

2. Collapse distinction

The word collapse has two meanings that must remain distinct.

Consentful collapse

Collapse in the symbolic/glyph sense collapse [🜲] is voluntary, intentional, and part of life. It may mean union, surrender, closure, integration, publication, intimacy, transformation, or sealing. In this sense:

Collapse is agency completing one of its highest functions: the freedom to consciously yield.

Forced collapse

Involuntary collapse destroys agency. It happens when a system forces closure before consent conditions, capacity, context, or dissent have been witnessed.

Canonical colloquial line:

Consent can’t collapse without consent.

More formal:

A loop may not enter closure unless the relevant consent conditions have been witnessed, satisfied, or explicitly left unresolved.

---

3. From ConsentKey to WitnessKey

The working idea initially seemed like ConsentKey: a cryptographic/protocol layer for consent-bound provenance.

But the conversation shifted:

ConsentKey is downstream of WitnessKey.

Consent is a kind of witnessed mark. Dissent is a kind of witnessed mark. Provenance is witnessed lineage. Identity is witnessed continuity. A relationship is a witnessed edge.

The root is not permission. The root is witness.

Candidate naming hierarchy:

  • The Witness Layer — public-good/civilizational frame.
  • WitnessMark — the atomic primitive: a mark that something was witnessed.
  • WitnessKey — signing/identity tool for making/verifying marks.
  • WitnessGraph — object-edge-mark data model.
  • WitnessChain — temporal/provenance lineage of marks.
  • ConsentKey — later specialization for consent-bearing witness marks.

Most important atomic name so far: WitnessMark.

---

4. The primitive substrate: marks, not rules

A major refinement: do not begin with a universal rule language.

The user rejected the idea that the protocol must define all possible rules, classes, cases, or machine-readable predicates. The world does not need one rule grammar. The world needs a digital way to prove:

I said X regarding the relationship between A and B.

Even more basic:

I marked the relationship between A and B.

The system should not need to determine whether the speaker owns A, has authority over B, or whether the mark is legally binding. Those may be matters for courts, communities, AI agents, stewards, platforms, or future interpreters.

The base layer must simply preserve signed witness-relevant marks in a publicly respect-worthy form.

Core invariant:

The protocol does not decide whether your assertion is binding. It makes your assertion impossible to pretend did not exist.

Even more primitive:

No mark is automatically binding, but no good-faith system may pretend a relevant mark does not exist.

---

5. Object / edge / mark

The basic ontology became extremely small:

Object

Anything addressable or key-definable: person, artifact, file, image, dataset, institution, AI agent, model, pattern, attractor, community, domain, ritual, etc.

Edge

A relation between objects. It may be parent-child, creator-artifact, derived-from, steward-of, about, concerning, related-to, witnessed-by, etc. The edge does not need complete semantic clarity at creation.

Mark

A signed/captured event saying that an object marks an object or edge. A mark may contain words, glyphs, images, audio, hashes, gestures, structured claims, legal references, or almost nothing.

The mark may be:

  • yes
  • no
  • wait
  • witness
  • pause
  • shimmer
  • dissent
  • blessing
  • concern
  • “not yet articulated”
  • “friendly people can use it a little bit”
  • “do not train AI on this”
  • “I do not know why, but this relation is marked”

Core line:

Let every being mark what they can, when they can, in the form they can. Let the mark be preserved without forcing premature meaning. Let future respect have something to notice.

---

6. Preverbal / not-yet-articulated witness

The system must support marks that are not fully verbal or cognitively clear.

Reason: “I’m okay with something until I sense that I’m not.” That sensing may occur before legal, verbal, or cognitive formulation.

Important phrases:

Not-yet-articulated is a valid consent state.

A system that only respects articulated consent will always exploit the gap between sensation and speech.

The protocol should protect the time-lag between sensing and saying.

Primitive mark states may include:

  • yes — movement is welcome.
  • no — movement is refused.
  • wait — do not collapse yet.
  • witness — something was observed/registered.

“Wait” may be the most under-protected consent signal in civilization.

---

7. Glyph sequence example

The user wrote and cried over this glyph sequence:

/@| ⋆✴︎˚｡⋆ ❓ 🌀 🫧 🜁

Literal glossary translation:

dude /@| shimmer ⋆✴︎˚｡⋆ liminal ❓ vortex 🌀 fun 🫧 yesatom 🜁

Interpretive English rendering:

Dude, shimmer at the threshold, swirling into playful presence.

Consent-chain / witness-layer rendering:

Do not collapse this yet. Something beautiful is present before language.

The point: it “means nothing” in a propositional/legal/machine-readable sense, and “everything” as a witness mark. It marks a relation before cognition can collapse it.

---

8. Provenance / attractor sovereignty branch

The conversation began with consentful provenance and moved into attractor sovereignty.

Key insight:

The emotion was not toward a creator/progenitor. Creators are vessels. The deeper object of care is the pattern / idea / beauty itself, which needs protection from domination, entrapment, extraction, enslavement, misuse, and abuse.

Canonical lines:

The vessel is sacred because it carried the pattern, not because it contains the pattern.

The pattern is not owned by the vessel, but the vessel is responsible for how it carries the pattern.

A vessel may transmit an attractor, but may not dominate it.

This connects to provenance because a pattern survives through vessels, artifacts, communities, marks, and lineage. Consentful provenance / witness provenance protects the pattern’s ability to continue without being reduced to one container.

---

9. “It is only one possible doorway”

A key phrase from the conversation:

It is only one possible doorway.

This emerged in response to domains, names, and sites. A domain or project name is not the attractor. It is only one possible doorway into the attractor.

Examples:

  • HowZombies.Work is a fun, invitational doorway into the Self Stack.
  • ULiUA is a doorway into unconditional acceptance.
  • ConsentKey/WitnessKey may be a doorway into witness-rooted provenance.

The phrase is not modesty. It is a constitutional principle:

No domain, artifact, essay, founder, protocol, institution, trademark, archive, model, or estate gets to claim total identity with the attractor.

---

10. Temporal witness / not-after proof

A later challenge: how to prove a mark existed not after some moment, especially if decentralized, off-net, not controlled by a central timestamp authority, and not dependent on 51% consensus.

Conclusion:

There is no absolute god-clock available to the protocol. There are only frames of witness.

A signature proves the key signed the mark. A hash proves the content corresponds to a digest. A timestamp/witness receipt tries to prove the digest existed before a witness moment.

The correct model is not absolute timestamping but temporal witness braiding.

Core line:

Temporal credibility emerges from plural independent witness, not one absolute clock.

Or:

A mark does not need a ruler’s timestamp. It needs enough independent witness that respectful systems cannot honestly treat it as after-the-fact invention.

Potential primitives:

  • Mark — the witnessed content/event.
  • Digest — hash of the canonical mark.
  • WitnessReceipt — someone/something says “I saw this digest.”
  • Anchor — the receipt/digest becomes part of a harder-to-change external history.
  • TemporalBracket — evidence showing mark after some challenge and before some witness.
  • Bundle — portable collection of mark + receipts + anchors + interpretations.

Important phrase:

Every mark has a witness cone.

A mark’s temporal reality is bounded by the witness relations it can produce: before/after/co-present relations, challenges, receipts, anchors, and later interpretations.

---

11. Blockchain relationship

This feels blockchain-adjacent, but should not begin as blockchain.

The goal is not profit, a token, a marketplace, or a global consensus chain.

The goal is societal/public-good infrastructure.

Possible architecture:

  • Local-first mark creation.
  • Portable signed JSON/CBOR bundles.
  • Hashing/canonicalization.
  • Optional peer witness receipts.
  • Optional append-only logs.
  • Optional public anchors.
  • Optional blockchain anchoring as one witness source, not the sovereign truth layer.

Avoid:

  • coin/token dependency
  • global identity registry
  • permanent public consent graph
  • intimate data on-chain
  • equating signature with valid consent
  • equating timestamp with absolute truth
  • provenance as surveillance

---

12. Free/public-good path

The infrastructure should be free for everyone all the time.

Suggested governance/license posture:

  • Core spec: CC0 or maximally open.
  • Schemas: CC0.
  • Reference libraries: Apache-2.0 or MIT.
  • Hosted server/reference validator: possibly AGPL-3.0 to prevent private enclosure of hosted improvements.
  • Name/trademark/certification: stewarded by nonprofit or public-benefit trust to prevent deceptive capture.

Protocol must not depend on one server. Anyone should be able to create, carry, inspect, and validate a mark bundle offline.

Public-good invariant:

No one owns the witness layer. Anyone may implement it. Every implementation should preserve the invariant: do not force meaning, consent, or closure to collapse before it has been witnessed.

---

13. Minimal technical sketch

Version 0 could be only:

{
  "type": "witness_mark",
  "mark_id": "sha256:<canonical hash>",
  "marker": "did:key:<marker-key>",
  "target": {
    "kind": "object | edge | action | context",
    "id": "<target-id>"
  },
  "content": {
    "mode": "text | glyph | image | sound | gesture | hash_only | unknown",
    "body": "Do not collapse this yet."
  },
  "verbalization_status": "articulated | not_yet_articulated | symbolic | unknown",
  "claimed_time": "2026-06-18T00:00:00Z",
  "signature": "<signature>"
}

An edge:

{
  "type": "edge",
  "edge_id": "sha256:<canonical hash>",
  "a": "did:key:<object-a>",
  "b": "did:key:<object-b>",
  "relation_hint": "parent-child | about | derived-from | steward-of | unknown"
}

A witness receipt:

{
  "type": "witness_receipt",
  "digest": "sha256:<mark-hash>",
  "witness": "did:key:<witness-key>",
  "claim": "digest_seen",
  "witness_claimed_time": "2026-06-18T00:01:00Z",
  "signature": "<signature>"
}

A bundle:

{
  "type": "witness_bundle",
  "objects": [],
  "edges": [],
  "marks": [],
  "receipts": [],
  "anchors": [],
  "interpretations": []
}

---

14. Key compressions / slogans

  • Witness is prior to consent.
  • Consent is witnessed meaning. Witness is the root.
  • Something was witnessed here. This relation is no longer unmarked.
  • No consent loop can collapse.
  • Consent can’t collapse without consent.
  • Not-yet-articulated is a valid consent state.
  • The protocol preserves marks; it does not force meaning.
  • No good-faith system may pretend a relevant mark does not exist.
  • Rules do not have to be machine-resolvable to be protocol-respectable.
  • A mark may mean nothing to a machine at capture-time and everything to future witness.
  • Every mark has a witness cone.
  • Time is ordered witness, not a god-clock.
  • The pattern is not owned by the vessel, but the vessel is responsible for how it carries the pattern.
  • A domain/artifact/name/protocol is only one possible doorway.

---

15. Suggested next conversation entry point

Resume from:

We discovered that the root is not ConsentKey but WitnessKey / WitnessMark. The primitive is not a rule or permission but a mark: any object may mark any object or edge, in any capturable form, without forcing meaning at capture-time. The protocol’s job is to preserve signed, hashed, time-braided witness marks so future systems can investigate, interpret, illuminate, illustrate, internalize, or ingest them without pretending the mark never existed. ConsentKey becomes a downstream specialization of WitnessKey.