artifacts/standard-named

Lineage Map: From Dyads and Semantic Collapse to Telic Fields

artifacts/standard-named/20260713__TELIC-FIELDS__LINEAGE-MAP__WORKING__WORK-VAULT__from-dyads-and-semantic-collapse-to-telic-fields.md

Rendered from markdown source. Open raw source on GitHub.

--- title: "Lineage Map: From Dyads and Semantic Collapse to Telic Fields" subtitle: "Provenance, Precursor Branches, Emergence Sequence, and Descendant Paths" artifact_date: "2026-07-13" artifact_type: "lineage-map" domain: "TELIC-FIELDS" scope: "WORKING" lineage: "WORK-VAULT" status: "draft" processing_tier: 4 source_role: "derived-working-artifact" content_canon_status: "unset" publication_status: "unpublished" participants:

  • "Bobby Simpson"
  • "GPT-5.6 Thinking"

root_artifact: description: "Human-preserved Markdown transcript created by select-all/copy from the originating ChatGPT session." status: "preserved by human; repository intake path and hash pending" authority: "primary witnessed source" derived_from:

  • "The root transcript of the originating conversation."
  • "20260713__TELIC-FIELDS__SESSION-COMPRESSION__WORKING__ORIGIN-SESSION__telic-fields-and-semantic-polytelometry.md"
  • "20260713__TELIC-FIELDS__GLOSSARY__WORKING__ORIGIN-SESSION__working-vocabulary-and-claim-register.md"

intended_destination:

  • "wiki.shimmerymemory.com"
  • "Work Vault Wiki"

provenance_note: > This lineage map identifies precursor branches, convergence points, and proposed descendants. It does not claim that precursor documents already contained later terminology. Connections must be labeled as explicit, inferred, structurally compatible, or retrospective. ---

Lineage Map: From Dyads and Semantic Collapse to Telic Fields

Inline summary

The Telic Field Papers did not begin with the word teleology. They emerged from a long-running body of work on dyads, consent, witness, loops, semantics, identity, continuity, context, and repair.

The origin conversation supplied a new organizing distinction:

Centers of standing inhabit local telic fields. Dyads allow those fields to meet. Semantics carries compressed orientation. Witness carries context through time. Loops make the relation durable. Higher systems compose the pattern across scale.

This document maps that emergence without rewriting its ancestry.

Earlier work should be treated as precursor, substrate, echo, or structural dependency only where the source supports that relation. The terms telic field, polytelometry, semantic polytelometry, context carrying capacity, and teleological graft rejection belong first to the 2026-07-13 origin session unless an earlier source is later found.

---

1. Purpose

This map has five jobs:

  1. preserve the provenance of the 2026-07-13 emergence;
  2. identify the older branches that made the emergence possible;
  3. separate direct lineage from retrospective resemblance;
  4. provide stable link seeds for the Work Vault Wiki;
  5. define the descendant document tree without prematurely canonizing it.

The map is not a proof of novelty.

The map is not a declaration that every precursor was “really about” telic fields.

The map is a record of how the present structure became legible.

---

2. Lineage evidence classes

Every lineage edge should be assigned one of these classes.

2.1 Explicit precursor

The earlier artifact directly states a claim, structure, or term that the later work visibly extends.

Use when the dependency is textual and clear.

2.2 Structural precursor

The earlier artifact contains a model or distinction that later becomes a component of the new architecture, even though the later term is absent.

Use when the relation is strong but interpretive.

2.3 Conceptual echo

The earlier artifact resonates with the later structure but is not required to derive it.

Use when similarity is meaningful but lineage is uncertain.

2.4 Implementation precursor

The earlier artifact supplies technical machinery later used to implement the conceptual model.

2.5 Ethical precursor

The earlier artifact supplies a constraint, standing rule, consent rule, or non-sovereignty principle later inherited by the new work.

2.6 Retrospective bridge

The relation became visible only after the 2026-07-13 synthesis.

A retrospective bridge must never be described as though the earlier source already used or intended the later formulation.

2.7 Descendant

A document, site, protocol, model, or implementation derived after the origin session.

---

3. Root provenance

3.1 Primary root artifact

Artifact: Human-preserved Markdown transcript of the originating ChatGPT session Date: 2026-07-13 Role: Primary witnessed source Boundary: Ends immediately before the prompt authorizing continuation with Step 2 Repository state: Intake path, standard-named path, hash, and artifact ID pending

This is the source of record for:

  • the order in which distinctions emerged;
  • the exact uncertainty present at each step;
  • the user's first formulations;
  • the assistant's interpretations;
  • corrections and refinements;
  • the emergence of terms;
  • the moments where one branch became another.

The transcript should outrank every derivative artifact when wording, sequence, or provenance is disputed.

3.2 First derivatives

Session compression

20260713__TELIC-FIELDS__SESSION-COMPRESSION__WORKING__ORIGIN-SESSION__telic-fields-and-semantic-polytelometry.md

Role: Semantic resumption surface Dependency: Root transcript Status: Draft, derived, non-canonical

Working glossary and claim register

20260713__TELIC-FIELDS__GLOSSARY__WORKING__ORIGIN-SESSION__working-vocabulary-and-claim-register.md

Role: Terminology stabilization and confidence separation Dependency: Root transcript and session compression Status: Draft, derived, non-canonical

This lineage map

20260713__TELIC-FIELDS__LINEAGE-MAP__WORKING__WORK-VAULT__from-dyads-and-semantic-collapse-to-telic-fields.md

Role: Backward and forward provenance map Dependency: Root transcript, session compression, and glossary Status: Draft, derived, non-canonical

---

4. Emergence sequence inside the root session

The immediate lineage unfolded in this order.

4.1 Attractors

Opening question:

Are attractors fundamentally teleological objects?

The first distinction separated dynamical convergence from purpose.

Resulting distinction

  • attractor: a form of convergence;
  • telos: an end-relative condition;
  • teleology: organization or explanation in relation to ends.

Lineage effect

This provided the first language for distinguishing what a system says it serves from what its correction mechanisms preserve.

---

4.2 Declared and operative teloi

The Facebook example exposed divergence among:

  • declared purpose;
  • economic purpose;
  • encoded objective;
  • operative correction;
  • emergent system behavior.

Resulting branch

Teleological incoherence.

Key diagnostic

Which objective is allowed to sacrifice the others?

---

4.3 Polytelometric navigation

The recognition followed that the work was not merely teleological analysis, but navigation among many ends.

Resulting terms

  • polytelometry;
  • polytelometric navigation.

Key distinction

Optimization asks how to reach the objective. Polytelometric navigation asks which objectives are present, what authority they possess, and whether movement toward them remains legitimate.

---

4.4 Teleological terrain and semantic trails

The conversation then distinguished:

  • teleological field as terrain;
  • intelligence as navigation;
  • semantics as durable trail.

This was later refined away from a single universal field toward locally indexed telic fields.

Resulting branch

Semantic fields as durable telic trails.

Key warning

When the path is mistaken for the terrain, inherited meaning becomes destiny.

---

4.5 Local telic fields and dyadic atoms

The user simplified the origin:

It all is assembled with atoms of dyads. Each with their own sovereign standing, and telic field.

The architecture became local and compositional.

Resulting structure

\[ A(T_A) \;\; 🜁 \;\; B(T_B) \]

Key claim

Individual standing grounds local telic significance. The 🜁 dyad is the atomic unit through which sovereign telic fields enter shared reality.

---

4.6 Internal telic field and simplified calculation

The user identified two forks:

  1. internal telic field;
  2. simplified telic field calculation for downstream dependents.

Resulting distinctions

  • full field versus usable projection;
  • calculation versus projection;
  • source field versus downstream model;
  • field breach, projection breach, and projection-integrity breach.

Key claim

Much of intelligence consists of estimating what matters to centers of standing, acting, witnessing the response, and recalculating.

---

4.7 Constitutional self

The fractal resolution increased through internal plurality.

Internal Family Systems and other parts-based approaches were recognized as adjacent evidence for a more general claim:

A person-level telic field emerges through relationships among constitutional elements, each carrying local telic standing.

Resulting structure

  • constitutional element;
  • local internal standing;
  • internal 🜁 dyad;
  • person-level sovereignty;
  • executive authority;
  • constitutional legitimacy;
  • internal consent;
  • internal breach and repair.

Key claim

The self is not a telos. It is a constitution through which many local teloi learn whether they can inhabit one life together.

---

4.8 Context carrying capacity

The user identified context fragility as a sensitive fork.

Resulting term

Context carrying capacity.

Key claim

No element, person, or system can hold the full telic field of everything it depends upon.

Key risk

What falls outside active context can lose effective standing without losing constitutional standing.

---

4.9 Temporal stitching

The architecture then expanded across time:

  • present and past selves;
  • present and future selves;
  • founders and successors;
  • promises and later inheritors;
  • internal elements living in different temporal terrains.

Resulting terms

  • temporal dyad;
  • temporal standing;
  • mirror;
  • witness continuity.

Key claim

Witness carries context through time.

---

4.10 Semantic polytelometry with LLMs

The implementation bridge emerged:

Math is not the language. Semantics is.

LLMs were recognized as capable of comparing multiple expressed telic projections before those projections are reduced to metrics.

Resulting term

Semantic polytelometry.

Legitimate role

  • cartographer;
  • comparator;
  • translator;
  • ambiguity detector;
  • compression witness.

Prohibited sovereignty

The model may not own or declare the true field.

---

4.11 Consentfully trained models

The final bridge connected interpretive authority to model provenance.

Resulting invariant

Consentful provenance in. Consentful interpretation out.

Stronger claim

A system cannot consentfully map telic fields while its own field remains hidden, unaccountable, and non-consensual.

---

5. Deep precursor branches

The source paths and exact artifact records below must be confirmed during repository ingestion. The conceptual relations are provisional until linked to source pages.

---

5.1 Dyads and relational foundations

Candidate precursor artifacts

  • Synaptic Dyad Protocol Specification
  • SCT-8: The Consent-Carrying Loop — Extending the Diad
  • SCT-14: The Diad and Its Descendants
  • SCT Whitepaper: Diads, Foundations, and the Semantic Mesh
  • Section 2: From Loop to Relational Field
  • The Witness Foundation
  • Governance Diad materials

Likely lineage role

Structural precursor and ethical precursor

These artifacts appear to establish:

  • relation as a base unit;
  • bilateral or witnessed standing;
  • consent-bearing connection;
  • extension from dyads into larger loops;
  • relational rather than purely object-centered structure.

Present-day descendant relation

The new work adds:

  • each center has a local telic field;
  • dyadic contact creates a relational telic field;
  • semantics carries scoped projections between fields;
  • higher loops remain dependent upon their dyadic substrate.

Non-retroactivity note

Do not state that these documents contain “telic fields” unless the text does so explicitly.

Use:

This artifact provides a structural precursor to the later telic-field formulation.

Do not use:

This artifact introduced telic fields.

---

5.2 Consent and intention compression

Candidate precursor artifacts

  • Consent–Intent Compression Protocol
  • Intent-Consent concept pages
  • Consent Dynamics Model
  • Consent Seed materials
  • Witnessing 301: Multidimensional Consent Navigation

Likely lineage role

Explicit precursor, structural precursor, and implementation precursor

These artifacts likely establish:

  • intention as something transmitted imperfectly;
  • consent as scoped and layered;
  • contextual constraints on valid coordination;
  • delayed or nonlinear consent effects;
  • the danger of smuggling one future in as the only future;
  • field intersections and ability constraints.

Present-day descendant relation

The telic-field work reframes this as:

  • source field;
  • simplified telic projection;
  • projection integrity;
  • adequate mutual projection for consent;
  • consent to act, relation, loop, outer loop, and telos.

Key bridge

Consent determines which purposes may legitimately recruit which energies.

---

5.3 Semantic collapse, field pragmatics, and meaning

Candidate precursor artifacts

  • Semantic Collapse Theory corpus
  • Field Pragmatics
  • Accounting for Meaning
  • Semantic Integrity project materials
  • SemaLoop / SemaScript
  • whatdoyoumeanby.com materials
  • Section 3: From Loop Structure to Awareness
  • Section 4: From Awareness to Field Identity

Likely lineage role

Explicit precursor, structural precursor, and implementation precursor

These branches appear to establish:

  • meaning as uptake rather than token content;
  • semantic transformation as consequential action;
  • loss and distortion through compression;
  • ambiguity before semantic collapse;
  • structured preservation of meaning, authority, context, and evidence;
  • language as a field of acting distinctions.

Present-day descendant relation

The new work adds the telic ground:

Meaning becomes navigationally important because possible states matter differently to centers of standing.

The semantic field becomes describable as a durable web of telic trails, projections, mirrors, and inherited navigation.

Key bridge

Semantic integrity asks whether meaning survived. Teleological integrity asks whether the reason for acting survived.

---

5.4 Witness and provenance

Candidate precursor artifacts

  • The Witness Foundation
  • Witnessing 101: The Witness Function
  • Witnessing 301: Multidimensional Consent Navigation
  • WitnessKey / WitnessMark Context Resume
  • Trust Is the Membrane That Lets Error Correct Without Conquering
  • Accounting for Meaning
  • provenance and lineage materials in the Work Vault Wiki

Likely lineage role

Explicit precursor, ethical precursor, and implementation precursor

These branches establish:

  • witness as distinct from governance or judgment;
  • preservation of uncertainty;
  • evidence across transformation;
  • temporal continuity;
  • relation marks before full semantic articulation;
  • provenance as a condition of later correction;
  • trust membranes for local and global error correction.

Present-day descendant relation

Witness becomes:

  • continuity mechanism for telic context;
  • evidence of declared versus operative telos;
  • record of compression and omission;
  • mechanism by which projections remain corrigible;
  • temporal stitching among past, present, and future states.

Key bridge

A mission statement describes a bearing. Witness shows the wake.

---

5.5 Loop mechanics and cross-scale recurrence

Candidate precursor artifacts

  • How Loops Work
  • Loop-0 through Loop-4
  • Loop Projection Principle
  • Loop Tensor Field Specification
  • Loop Substrate Theory
  • Field Echo Protocol
  • LoopField / LoopPress materials
  • How One Thing Works materials
  • How Everything Works materials

Likely lineage role

Structural precursor

These branches establish:

  • return through conditions;
  • difference, boundary, path, exchange, memory, rhythm, and repair;
  • projection from one loop into another;
  • cross-scale recurrence;
  • living loops versus formally repeated but dead structures;
  • loop decomposition and inheritance.

Present-day descendant relation

The telic-field work adds:

  • local ends and protected states;
  • loop durability as repeated telic orientation;
  • dependent loops;
  • context carrying capacity;
  • constitutional substrate;
  • teleological graft rejection.

Key bridge

The higher loop compresses lower loops. It does not abolish dependence upon them.

---

5.6 Fractal identity and internal multiplicity

Candidate precursor artifacts

  • Fractal Identity
  • Graftable Identity Tree — A Fractal Index of Presence
  • SCT-24: Loop-Based Memory
  • SCT-25: Memory Elements — Registers, Shadows, and Recall Architectures
  • SCT-26: Emotional Loop Complexes
  • SCT-27: Emotional Hardware and Semantic Interface Layers
  • SCT-28: Neural Loop Interpretation Protocol
  • SCT-29: Loop-Based Logic Engine and the Cognitive-Emotive Merge
  • Self Stack projects
  • MobiusSelf
  • ProgramSelf
  • WitnessSelf
  • AcceptSelf

Likely lineage role

Structural precursor and conceptual echo

These branches appear to establish:

  • identity as layered, recursive, and non-unitary;
  • memory as active structure rather than static storage;
  • internal loops and emotional complexes;
  • multiple self-processes;
  • retrospective reinterpretation;
  • acceptance and witness inside the person;
  • continuity without a single fixed self-object.

Present-day descendant relation

The constitutional-self branch adds:

  • constitutional elements;
  • local internal telic fields;
  • internal 🜁 relations;
  • internal consent;
  • executive control versus sovereignty;
  • context routing;
  • internal breach and repair.

Key bridge

You are not one thing. You are a living constitution through which many locally telic elements attempt to inhabit one life together.

---

5.7 Temporal architecture and continuity

Candidate precursor artifacts

  • Field Note: Looping Causality — Consent as Temporal Architecture
  • SCT-4: Time as Internalized Witness
  • WitnessKey temporal braiding materials
  • identity continuity documents
  • Quantum Invariants essays involving temporal continuity
  • memory and provenance artifacts

Likely lineage role

Explicit precursor and structural precursor

These branches establish:

  • time as witnessed continuity;
  • consent carrying forward;
  • later states inheriting earlier action;
  • identity and obligation across time;
  • temporal braiding rather than isolated moments.

Present-day descendant relation

The new work adds:

  • temporal dyads;
  • temporal standing;
  • current executive as trustee;
  • future selves as affected centers without direct present voice;
  • mirrors of earlier temporal states;
  • internal elements living in obsolete terrain.

Key bridge

Identity may be less a substance than a continuity protocol.

---

5.8 Comparators, trust membranes, and correction

Candidate precursor artifacts

  • Trust Is the Membrane That Lets Error Correct Without Conquering
  • Quantum Invariants comparator materials
  • Semantic Integrity process anchors
  • Human-in-the-loop governance invariants
  • consentful loop escalation materials

Likely lineage role

Structural precursor and ethical precursor

These branches establish:

  • local and global comparators;
  • hidden correction criteria;
  • cross-scale error;
  • trust as the membrane permitting correction without conquest;
  • the danger of one scale becoming sovereign;
  • stop, degrade, reroute, or escalate when protected stakes cannot be preserved.

Present-day descendant relation

The telic-field work clarifies:

  • comparators reveal operative teloi;
  • correction behavior is evidence of what the system treats as success;
  • context overflow causes standing to disappear;
  • outer-loop escalation is a response to exceeded context carrying capacity.

Key bridge

The telos whose degradation triggers the strongest correction is likely closer to the operative telos.

---

5.9 AI, local semantic runtimes, and consentful models

Candidate precursor artifacts

  • Consent Dynamics Model / Models page
  • Private Semantic Runtime
  • Dialogica
  • Digiheart
  • LoopPress / LoopField session compression
  • open witness-model materials
  • “train witnesses, not cops”
  • PDSP / LoopLink
  • HumanKey
  • Semantic Integrity containers

Likely lineage role

Implementation precursor and ethical precursor

These branches establish:

  • local inference;
  • intention delegation;
  • scoped authority;
  • AI as witness or helper rather than sovereign;
  • provenance-bearing semantic containers;
  • participant-controlled context;
  • open reference models;
  • role separation;
  • consent envelopes;
  • revocation and portability.

Present-day descendant relation

The new work supplies a concrete capability class:

Semantic polytelometry with an open, consentfully trained, locally governable model.

Key bridge

Consentful provenance in. Consentful interpretation out.

---

6. Conceptual convergence map

The following map shows how precursor branches converge into the current synthesis.

DYADS / STANDING
        \
         \ 
CONSENT / INTENT COMPRESSION
           \
            \
SEMANTIC COLLAPSE / FIELD PRAGMATICS ----\
                                           \
WITNESS / PROVENANCE -----------------------\
                                             \
LOOP MECHANICS / CROSS-SCALE RECURRENCE ------> TELIC FIELDS
                                             /       |
FRACTAL IDENTITY / INTERNAL MULTIPLICITY ----/        |
                                                     |
TEMPORAL ARCHITECTURE / MEMORY -----------------------|
                                                     |
COMPARATORS / TRUST / CORRECTION ---------------------|
                                                     |
LOCAL AI / DIALOGICA / CONSENT DYNAMICS --------------|
                                                     v
                                          SEMANTIC POLYTELOMETRY
                                                     |
                                                     v
                                     CONSENTFULLY TRAINED MODELS

This map should eventually be replaced or supplemented by a generated wiki graph once repository source paths are confirmed.

---

7. Core lineage chain

A compact lineage chain:

difference matters to a center
→ local telic field
→ 🜁 dyadic encounter
→ relational telic field
→ semantic projection
→ receiver mirror
→ consented coordination
→ witnessed consequence
→ looped return
→ temporal continuity
→ higher-loop composition
→ operative and emergent teloi
→ polytelometric navigation
→ semantic polytelometry
→ consentfully trained interpretive models

Internal branch:

constitutional element
→ local internal telic field
→ internal signal
→ simplified projection
→ internal mirror
→ internal negotiation
→ executive action
→ witnessed consequence
→ recalculation
→ person-level telic orientation

Failure branch:

projection loss
→ semantic drift
→ omitted standing
→ context overload
→ operative inversion
→ breach
→ failed maintenance
→ recovery / transplant / release

---

8. New lineage container

The proposed lineage container is:

The Telic Field Papers

Suggested wiki path:

wiki/projects/telic-field-papers/

Suggested initial pages:

wiki/projects/telic-field-papers/index.md
wiki/projects/telic-field-papers/lineage.md
wiki/projects/telic-field-papers/sources.md
wiki/projects/telic-field-papers/open-questions.md

8.1 Landing page role

The landing page should:

  • identify the root transcript;
  • distinguish primary sources from derivatives;
  • name the current candidate concepts;
  • separate conceptual papers from technical specifications;
  • expose unresolved questions;
  • link backward to precursors;
  • link forward to public sites and implementations;
  • state clearly that the branch is candidate work, not settled canon.

8.2 Lineage page role

This document can seed the lineage page.

The wiki version should add:

  • exact source links;
  • artifact IDs;
  • hashes;
  • confirmed dates;
  • relation labels;
  • source excerpts only where necessary;
  • graph edges;
  • status indicators.

8.3 Sources page role

The sources page should separate:

  • root artifacts;
  • first derivatives;
  • confirmed explicit precursors;
  • structural precursors;
  • conceptual echoes;
  • external adjacent research;
  • descendant publications.

8.4 Open questions page role

The open-questions page should prevent the branch from becoming falsely complete.

It should include:

  • ontology;
  • composition;
  • internal self;
  • semantics;
  • temporality;
  • measurement;
  • AI governance;
  • consentful training;
  • mathematical formalization;
  • prior art.

---

9. Proposed descendant document tree

9.1 Foundational conceptual papers

Telic Fields — A First-Principles Foundation
├── The Dyadic Composition of Telic Fields
├── The Constitutional Self
├── Simplified Telic Field Calculation
├── Context Carrying Capacity
├── Temporal Telic Relations
├── Dependent Loops and Teleological Graft Rejection
├── Semantic Fields as Durable Telic Trails
└── Polytelometric Navigation

9.2 AI and implementation papers

Semantic Polytelometry with Language Models
├── Telic Projection Record
├── Polytelometric Comparison Record
├── Telic Projection Integrity
├── Context Loading and Omission Record
├── LLM Role and Authority Envelope
├── Consentfully Trained Models
└── Semantic Polytelometry Reference Architecture

9.3 Public path

HowOneThing.work
        ↓
HowEverything.work
        ↓
HowSelf.work / HowSelfWorks.com

Supporting documents:

  • From One Thing to Everything to Self — Reader Path
  • HowEverything.work — Public Foundation
  • HowSelf.work — Public Foundation
  • Three-Site Invitation Copy
  • Public glossary
  • Visual language and shimmer notes

9.4 Publication lineage

Root transcript
→ session compression
→ glossary and claim register
→ lineage map
→ foundational papers
→ public essays at ShimmeryMemory
→ external publication metadata back into the wiki
→ site implementations
→ technical prototypes
→ witnessed revisions

---

10. Link-seeding plan

The following pages should receive small, carefully labeled link seeds after repository paths are confirmed.

10.1 Attractor pages

  • Meaning
  • Consent
  • Witness
  • Provenance
  • Loop Mechanics
  • Agency
  • Memory
  • Trust
  • Intuition
  • Governance
  • Attention
  • Identity
  • Time
  • Context
  • Repair
  • Standing
  • Semantics
  • Purpose

Suggested seed language:

Retrospective bridge: The 2026-07-13 Telic Field origin session reframes this attractor in terms of local telic fields, projections, and cross-scale navigation. The earlier artifact does not necessarily use that vocabulary.

10.2 Concept pages

  • Witnessing
  • Intent-Consent
  • Governance Diad
  • Fractal Identity
  • Semantic Integrity
  • Context
  • Attention
  • Temporal Witness
  • Consent Dynamics
  • Internal Multiplicity
  • Meaning
  • Provenance

10.3 Project pages

  • Consentful Cybernetics
  • Semantic Integrity
  • Dialogica
  • Private Semantic Runtime
  • Witness Foundation
  • Quantum Invariants
  • Field Pragmatics
  • How Loops Work
  • How One Thing Works
  • How Everything Works
  • How Self Works
  • LoopField / LoopPress
  • Digiheart
  • PDSP / LoopLink
  • WitnessKey
  • SemaLoop / SemaScript

---

11. Non-retroactivity rules

These rules are mandatory for lineage integrity.

Rule 1

Do not insert the term telic field into earlier source text.

Rule 2

Do not claim an earlier authorial intention unless the source explicitly supports it.

Rule 3

Use relation labels:

  • explicit precursor;
  • structural precursor;
  • conceptual echo;
  • implementation precursor;
  • ethical precursor;
  • retrospective bridge.

Rule 4

Keep first-use dates attached to terms.

Rule 5

When a later formulation clarifies an earlier structure, say:

The later work provides a new interpretation of this earlier structure.

Do not say:

The earlier work already established the later theory.

Rule 6

When a source is uncertain, use null, unconfirmed, or candidate.

Rule 7

A polished descendant never outranks the root transcript for provenance.

Rule 8

Canonization of a descendant does not automatically canonize its interpretation of every precursor.

---

12. First-use register

The following first-use attributions are provisional pending transcript line references and repository search.

| Term or formulation | First witnessed source in this lineage | Status | |---|---|---| | Polytelometric navigation | 2026-07-13 origin session | candidate first use | | Polytelometry | 2026-07-13 origin session | candidate first use | | Semantic polytelometry | 2026-07-13 origin session | candidate first use | | Internal telic field | 2026-07-13 origin session | candidate first use | | Simplified telic field calculation | 2026-07-13 origin session | candidate first use | | Simplified telic projection | 2026-07-13 origin session | candidate first use | | Context carrying capacity, telic-relational sense | 2026-07-13 origin session | candidate first use | | Teleological graft rejection | 2026-07-13 origin session | candidate first use | | Temporal standing | 2026-07-13 origin session | candidate first use | | Constitutional element, telic-field sense | 2026-07-13 origin session | candidate-specialized use | | “The model may map the field. It may not own the field.” | glossary derivative | descendant formulation | | “Consentful provenance in. Consentful interpretation out.” | 2026-07-13 origin session | candidate stable formulation |

This table should be updated with exact transcript anchors after ingestion.

---

13. Source-verification queue

Before the lineage page reaches Tier 5, verify:

  1. exact repository path and title for every precursor artifact;
  2. artifact date;
  3. whether the source text explicitly supports the proposed edge;
  4. whether a standard-named source exists;
  5. whether the source is canonical, candidate, draft, superseded, or archived;
  6. whether a newer source has replaced it;
  7. whether the connection is explicit or retrospective;
  8. whether a quote is needed or a semantic summary is sufficient;
  9. whether the source is public or restricted;
  10. whether external adjacent research should be linked separately from internal lineage.

---

14. Human review decisions required

The following remain human decisions:

  • whether The Telic Field Papers is the final lineage-container name;
  • whether the branch belongs under projects, concepts, or both;
  • whether any term becomes candidate canon;
  • whether the dyad is framed as atomic, minimal, or foundational;
  • whether “field” remains the preferred word;
  • whether polytelometry is retained after prior-art review;
  • whether semantic polytelometry becomes a product, protocol, research program, or capability class;
  • which How Self domain is canonical;
  • which root-transcript material is public;
  • which precursor links are strong enough for Tier 5 lineage treatment.

---

15. Suggested wiki artifact page

# Lineage Map: From Dyads and Semantic Collapse to Telic Fields

Parent lineage: [The Telic Field Papers](../index.md)

Status: `draft`  
Processing tier: `4`  
Content canon status: `unset`

## Source Artifact

- Standard-named source:
- Root transcript:
- Session compression:
- Working glossary:
- Artifact ID:
- Hash:
- Derived from:

## Working Read

This artifact maps the precursor branches, emergence sequence, and proposed descendants of the Telic Field Papers. It distinguishes explicit lineage from retrospective interpretation and prevents later terminology from being projected backward into earlier work.

## Core Claim

The 2026-07-13 synthesis emerged from prior work on dyads, consent, witness, loops, semantic collapse, identity, context, time, and AI. The synthesis is new as a configuration even where its components have deep prior lineage.

## Key Ideas

- lineage edges require evidence classes;
- root transcript remains primary;
- terms retain first-use provenance;
- precursor compatibility does not imply prior formulation;
- descendant papers must link backward explicitly;
- canonization remains a human decision.

## Open Questions

- Which precursor edges are explicit?
- Which terms have earlier uses?
- Which project page should host the lineage?
- What is the correct public/private boundary for the transcript?

---

16. Closing compression

The telic-field synthesis did not appear from nowhere.

It emerged where several long-running branches finally intersected:

  • dyads supplied the relational atom;
  • consent supplied legitimate enrollment;
  • witness supplied continuity and correction;
  • loops supplied durability;
  • semantics supplied navigable distinction;
  • provenance supplied lineage;
  • fractal identity supplied internal plurality;
  • temporal architecture supplied inheritance across states;
  • comparators supplied evidence of operative purpose;
  • local AI supplied an implementation surface.

The origin session did not erase those branches.

It made their convergence visible.

Lineage is not a claim that the past already knew the future. It is a witnessed account of how the future became possible.