KTP-Relational: Relational Dynamics

Status: Experimental

This document operationalizes indigenous relational wisdom—Ubuntu, Whakapapa, The Va—into measurable protocol mechanics. It defines the Relational Tensor and protocols for relationship health.

At a Glance

Property	Value
Status	Experimental
Version	0.1
Dependencies	KTP-Core, KTP-Identity
Required By	KTP-Human, KTP-Governance

---

The Va: The Space Between

In KTP, a relationship is not just a link between two nodes; it is an entity in itself. This "Space Between" (The Va) has health, history, and physics.

Relational Tensor Dimensions

Category	Dimensions	Examples
Connection	8	Frequency, Depth, Recency, Mutual Recognition
Trust	6	Level, Direction, Velocity, History
Health	6	Temperature, Conflict, Repair Needed
Exchange	4	Reciprocity, Gratitude, Support
Presence	4	Quality, Witnessing, Meaning

---

Repair Protocols

Relationships break. KTP defines how to fix them.

graph TD
    Harm[Harm Detected] --> Phase1[Recognition]
    Phase1 --> Phase2[Understanding]
    Phase2 --> Phase3[Accountability]
    Phase3 --> Phase4[Restoration]
    Phase4 --> Phase5[Integration]

    Phase5 --> Healed[Relationship Healed]

    subgraph "The Repair Cycle"
    Phase1
    Phase2
    Phase3
    Phase4
    Phase5
    end

Repair Types: - Trust Violation: Requires transparency + time. - Boundary Crossing: Requires boundary clarification. - Resource Imbalance: Requires rebalancing.

---

Seven Generations Thinking

Major decisions must be assessed across time horizons.

Generation	Horizon
G1	Immediate (1 year)
G2	Near (5 years)
G3	Medium (15 years)
G4	Long (30 years)
G5	Extended (50 years)
G6	Distant (100 years)
G7	Horizon (100+ years)

"Decisions consider impact on seven generations forward and honor seven generations back."

---

Related Specifications

Related Specifications

• KTP-Core: Trust physics applied to relationships.
• KTP-Identity: Lineage and relational history.
• KTP-Human: Human governance and relational interfaces.
• KTP-Governance: Policy for dispute and repair.

---

Official RFC Document

View Complete RFC Text (ktp-relational.txt)

Kinetic Trust Protocol                                      C. Perkins
Specification Draft                                           NMCITRA
Version: 0.1                                             November 2025


   Kinetic Trust Protocol (KTP) - Relational Dynamics Specification

Abstract

   This document specifies the relational dynamics layer of the Kinetic
   Trust Protocol (KTP). Drawing on indigenous relational concepts—
   Ubuntu, Whakapapa, The Va, Mitákuye Oyás'iŋ, and Seven Generations
   thinking—this specification formalizes relationship measurement,
   repair protocols, and ceremony requirements. The Va (sacred space
   between entities) becomes operationalized as 28 measurable dimensions
   within the Relational Tensor, with protocols for relationship health
   monitoring, harm repair, and relational ceremony.

Status of This Memo

   This document specifies a Kinetic Trust Protocol (KTP) specification
   for the KTP community, describing the relational dynamics layer and
   associated protocols. Distribution of this memo is unlimited.

Copyright Notice

   Copyright (c) 2025 NMCITRA. All rights reserved.

   This document is subject to the licensing terms of the Kinetic Trust
   Protocol project and may be used, copied, and distributed under those
   terms.

Table of Contents

   1. Introduction .................................................. 1
   2. Indigenous Foundations ........................................ 2
   3. Requirements Language ......................................... 2
   4. The Va: Formalized ............................................ 3
      4.1. Concept .................................................. 3
      4.2. Va Dimensions (28 Total) ................................. 3
           4.2.1. Connection Dimensions (8) ......................... 3
           4.2.2. Trust Dimensions (6) .............................. 4
           4.2.3. Health Dimensions (6) ............................. 4
           4.2.4. Exchange Dimensions (4) ........................... 5
           4.2.5. Presence Dimensions (4) ........................... 5
      4.3. Va States ................................................ 5
   5. Repair Protocols .............................................. 6
      5.1. Repair Process ........................................... 6
      5.2. Repair Types ............................................. 7
   6. Ceremony Specifications ....................................... 7
      6.1. Ceremony Types ........................................... 7
           6.1.1. Genesis Ceremony .................................. 7
           6.1.2. Renewal Ceremony .................................. 8
           6.1.3. Transition Ceremony ............................... 8
           6.1.4. Ending Ceremony ................................... 8
           6.1.5. Repair Ceremony ................................... 8
      6.2. Ceremony Requirements .................................... 8
   7. Seven Generations Thinking .................................... 9
   8. Witness Requirements .......................................... 9
   9. Security Considerations ....................................... 9
   10. IANA Considerations .......................................... 9
   11. Acknowledgments .............................................. 9

1. Introduction

   Trust is not atomic—it exists between entities. The Relational Tensor
   captures this between-ness, but measurement alone is insufficient.
   Relationships require tending: monitoring, repair when damaged, and
   ceremony to maintain health.

   This specification operationalizes indigenous relational wisdom for
   AI governance. We acknowledge this as an imperfect translation of
   concepts developed over millennia by cultures whose full meaning we
   cannot capture in protocol. We proceed with humility and gratitude.

2. Indigenous Foundations

   This specification draws on:

   Ubuntu (Nguni/Bantu): "I am because we are." Personhood emerges
   through relationship.

   Whakapapa (Māori): Genealogical connection to all things. Identity is
   relational, not individual.

   The Va (Samoan/Pasifika): The sacred space between entities. The
   relationship itself has existence.

   Mitákuye Oyás'iŋ (Lakota): "All are related." Connection extends to
   all beings, past and future.

   Seven Generations (Haudenosaunee): Decisions consider impact on seven
   generations forward and honor seven generations back.

3. Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in BCP 14 (RFC 2119 and
   RFC 8174).

4. The Va: Formalized

4.1. Concept

   The Va is the space between. Not empty space—sacred space. The
   relationship itself exists in The Va, independent of the entities it
   connects.

4.2. Va Dimensions (28 Total)

4.2.1. Connection Dimensions (8)

   - Dimension: relationship_type
     Description: Type of relationship
     Scale: enum

   - Dimension: relationship_age
     Description: Duration of relationship
     Scale: seconds

   - Dimension: interaction_frequency
     Description: How often do entities interact?
     Scale: Hz

   - Dimension: interaction_recency
     Description: Time since last interaction
     Scale: seconds

   - Dimension: interaction_depth
     Description: Quality of interactions
     Scale: 0-1

   - Dimension: mutual_recognition
     Description: Do entities recognize each other?
     Scale: boolean

   - Dimension: identity_known
     Description: Do entities know each other's identity?
     Scale: boolean

4.2.2. Trust Dimensions (6)

   - Dimension: trust_direction
     Description: Symmetry of trust
     Scale: -1 to 1

   - Dimension: trust_velocity
     Description: How fast is trust changing?
     Scale: units/sec

   - Dimension: trust_history
     Description: Trajectory of trust over time
     Scale: vector

   - Dimension: trust_basis
     Description: What is trust based on?
     Scale: enum[]

   - Dimension: vulnerability_shared
     Description: How much vulnerability exchanged?
     Scale: 0-1

4.2.3. Health Dimensions (6)

   - Dimension: conflict_status
     Description: Is there active conflict?
     Scale: enum

   - Dimension: repair_needed
     Description: Is repair needed?
     Scale: boolean

   - Dimension: repair_in_progress
     Description: Is repair happening?
     Scale: boolean

   - Dimension: boundary_clarity
     Description: Are boundaries clear?
     Scale: 0-1

   - Dimension: boundary_respect
     Description: Are boundaries respected?
     Scale: 0-1

4.2.4. Exchange Dimensions (4)

   - Dimension: support_given
     Description: Support provided to other
     Scale: 0-1

   - Dimension: support_received
     Description: Support received from other
     Scale: 0-1

   - Dimension: gratitude_expressed
     Description: Gratitude exchanged
     Scale: 0-1

4.2.5. Presence Dimensions (4)

   - Dimension: witness_status
     Description: Has relationship been witnessed?
     Scale: boolean

   - Dimension: ceremony_recency
     Description: Time since last ceremony
     Scale: seconds

   - Dimension: meaning_co_created
     Description: Shared meaning in relationship
     Scale: 0-1

4.3. Va States

   - State: HEALTHY
     Va Health: 0.6 - 0.8
     Description: Relationship is functioning well

   - State: STRAINED
     Va Health: 0.4 - 0.6
     Description: Relationship needs attention

   - State: DAMAGED
     Va Health: 0.2 - 0.4
     Description: Relationship needs repair

   - State: BROKEN
     Va Health: 0.0 - 0.2
     Description: Relationship is severely damaged

   - State: SEVERED
     Va Health: 0.0
     Description: Relationship has been ended

5. Repair Protocols

5.1. Repair Process

   Phase 1: RECOGNITION
   - Harm is acknowledged
   - Parties agree repair is needed
   - Repair context established

   Phase 2: UNDERSTANDING
   - Impact of harm explored
   - Perspectives shared
   - Root causes identified

   Phase 3: ACCOUNTABILITY
   - Responsibility acknowledged
   - Not blame—acknowledgment
   - Commitment to change

   Phase 4: RESTORATION
   - Concrete repair actions
   - Reciprocity addressed
   - Trust rebuilt incrementally

   Phase 5: INTEGRATION
   - Learning captured
   - Relationship strengthened
   - Prevention measures established

5.2. Repair Types

   - Harm Type: Boundary crossing
     Repair Protocol: Acknowledgment + boundary clarification

   - Harm Type: Harm to third party
     Repair Protocol: Acknowledgment + third party repair + witness

   - Harm Type: Resource imbalance
     Repair Protocol: Acknowledgment + rebalancing

   - Harm Type: Communication breakdown
     Repair Protocol: Process reset + clarity ceremony

6. Ceremony Specifications

6.1. Ceremony Types

6.1.1. Genesis Ceremony

   Performed when relationship begins—introduction, intention,
   boundaries, commitment, acknowledgment.

6.1.2. Renewal Ceremony

   Performed periodically (monthly/quarterly)—reflection, gratitude,
   adjustment, recommitment.

6.1.3. Transition Ceremony

   Performed when relationship changes significantly—acknowledgment,
   honoring, transformation, blessing.

6.1.4. Ending Ceremony

   Performed when relationship ends—acknowledgment, gratitude, release,
   blessing.

6.1.5. Repair Ceremony

   Integrated into repair protocol—truth telling, impact witnessing,
   accountability, amends, release, new beginning.

6.2. Ceremony Requirements

   - Zone Type: Blue
     Genesis: REQUIRED
     Renewal: REQUIRED quarterly
     Transition: REQUIRED
     Ending: REQUIRED
     Repair: REQUIRED

   - Zone Type: Cyan
     Genesis: REQUIRED
     Renewal: RECOMMENDED
     Transition: RECOMMENDED
     Ending: RECOMMENDED
     Repair: REQUIRED

   - Zone Type: Green
     Genesis: RECOMMENDED
     Renewal: OPTIONAL
     Transition: OPTIONAL
     Ending: OPTIONAL
     Repair: RECOMMENDED

7. Seven Generations Thinking

   Major relational decisions require seven-generation assessment:

   - G1: Immediate (now - 1 year)
   - G2: Near (1 - 5 years)
   - G3: Medium (5 - 15 years)
   - G4: Long (15 - 30 years)
   - G5: Extended (30 - 50 years)
   - G6: Distant (50 - 100 years)
   - G7: Horizon (100+ years)

   Assessment acknowledges uncertainty increases with distance but
   requires consideration of long-term impact.

8. Witness Requirements

   - Event: Relationship Termination
     Witness Required: Yes
     Minimum Witnesses: 1 (Zone or Oracle)

   - Event: Repair Ceremony
     Witness Required: Yes
     Minimum Witnesses: 1

   - Event: Trust Transfer
     Witness Required: Yes
     Minimum Witnesses: 2

   - Event: Harm Attestation
     Witness Required: Yes
     Minimum Witnesses: 1

   - Event: Zone Migration
     Witness Required: Yes
     Minimum Witnesses: 2 (both zones)

9. Security Considerations

   Relationship data is sensitive and requires encryption, access
   controls, and careful handling per data sovereignty requirements.

10. IANA Considerations

   This document has no IANA actions.

11. Acknowledgments

   This specification draws on indigenous relational frameworks with
   deep gratitude. We acknowledge that our formalization is imperfect
   and commit to ongoing learning.