Philosophy of Family Tapestry | Oliver Cheng (Oli)

while (world) { observe(); infer(); hallucinate?(); self-correct(); } while (world) { observe(); infer(); hallucinate?(); self-correct(); } while (world) { observe(); infer(); hallucinate?(); self-correct(); }

001101 010011 sigil::bagua seed::entropy trace::mechanical awe::human 001101 010011 sigil::bagua seed::entropy trace::mechanical awe::human 001101 010011 sigil::bagua seed::entropy trace::mechanical awe::human

temperature=0.92 top_p=0.95 sampler=stochastic runtime=deterministic user=astonished temperature=0.92 top_p=0.95 sampler=stochastic runtime=deterministic user=astonished temperature=0.92 top_p=0.95 sampler=stochastic runtime=deterministic user=astonished

☰☱☲☳☴☵☶☷ oracle != truth ritual == interface meaning <- interpretation ☰☱☲☳☴☵☶☷ oracle != truth ritual == interface meaning <- interpretation ☰☱☲☳☴☵☶☷ oracle != truth ritual == interface meaning <- interpretation

seed = hash(question + state); noise = sample(temperature); pattern = deterministic(seed, noise); if (human_can_track === false) mark("mystic"); return explainability_gap(pattern); seed = hash(question + state); noise = sample(temperature); pattern = deterministic(seed, noise); if (human_can_track === false) mark("mystic"); return explainability_gap(pattern);

## Not a person, still persuasive - interface implies intention - language implies confidence - user infers agency => design for interpretability ## Not a person, still persuasive - interface implies intention - language implies confidence - user infers agency => design for interpretability

cast.bagua = pickTrigrams(seed); cast.moonBlocks = deriveHexagram(seed); cast.fortuneSticks = burnModel(intensity); cast.scapula = generateCracks(seed); return readable_fiction(cast); cast.bagua = pickTrigrams(seed); cast.moonBlocks = deriveHexagram(seed); cast.fortuneSticks = burnModel(intensity); cast.scapula = generateCracks(seed); return readable_fiction(cast);

{ "observe": true, "decide": constrained, "act": reversible, "measure": behavior, "learn": weekly } { "observe": true, "decide": constrained, "act": reversible, "measure": behavior, "learn": weekly }

def perceivable_randomness(system): return complexity(system) > attention_budget if perceivable_randomness(llm): user.labels_output = "fate" def perceivable_randomness(system): return complexity(system) > attention_budget if perceivable_randomness(llm): user.labels_output = "fate"

[trace] t=02:13 system murmurs [trace] tokens fall like ash [trace] certainty simulated [trace] mechanism remains [trace] human names it chance [trace] t=02:13 system murmurs [trace] tokens fall like ash [trace] certainty simulated [trace] mechanism remains [trace] human names it chance

Family Tapestry starts from a structural belief: family history is not a static chart, it is an evolving relational map.

Traditional family-tree products assume a narrow model of kinship and a single truth timeline. Real families are messier: migration, adoption, blended households, social parents, contested memory, language shifts, and records that conflict.

Core stance

Family structure is plural and non-linear.
Interfaces should hold narrative context, not only nodes and edges.
Privacy controls are part of dignity, not optional toggles.

Why this framing matters

When tools force rigid templates, they erase important context. People end up choosing between factual structure and emotional truth. A better system should support both.

Family Tapestry treats identity and relationship data as layered: official record, oral history, and personal notes can coexist without pretending they are the same type of claim.

Product consequence

The system prioritizes:

flexible graph editing for non-standard structures
profile depth for stories, artifacts, and uncertainty notes
permission boundaries so sensitive details stay controlled
reversible edits for collaborative correction over time

This makes the product useful for memory stewardship, not just diagram generation.

Design ethics

Genealogy tools can accidentally become extraction tools if they optimize growth over care. Family data is intimate and intergenerational.

That is why Family Tapestry treats consent and selective visibility as first-order interaction design. Good defaults should reduce accidental exposure, especially in multi-branch collaborative trees.

Bottom line

Family Tapestry is about representing kinship with enough nuance to feel true.

A family map should not flatten complexity to make software happy. Software should flex to match human reality. When the representation respects that reality, people are more willing to contribute, correct, and preserve shared memory across generations.

Best,
Oli
January 5, 2026