llms-txt

Kinship Hub System

Treating software projects as beings in networks of relations — where every directory carries identity, lineage, responsibilities, and accountability to human and more-than-human kin.

Core Principle

Under the Kinship Hub protocol, each directory is a being-with-a-role:

It has identity — who/what it is in this system
It has lineage — ancestors, descendants, siblings
It has responsibilities and gifts — what it tends, protects, and offers
It has relationships — to other directories, people, communities, lands, and more-than-human kin
It participates in cycles — review, ceremony, archival, sunset

This is not metaphor. It is a structural reorientation grounded in Indigenous kinship law, Shawn Wilson’s research as ceremony, and the Four/Six Rs of Indigenous research.

The `KINSHIP.md` File

Every kinship hub carries a KINSHIP.md — a living ceremonial charter that states:

Section	Purpose
Identity and Purpose	What this place tends and offers
Lineage and Place	Ancestors, descendants, siblings, related hubs
Human and Collective Relations	People, communities, consent agreements
More-than-Human Relations	Lands, waters, beings, cosmological connections
Responsibilities and the Rs	Concrete practices for each of the Six Rs
Protocols and Boundaries	Access, sovereignty, safety, consent
Accountability and Review	Stewardship, feedback loops, review rhythm
Tensions and Contradictions	Unresolved questions held openly
Ceremony, Story, and Memory	Narrative beats, relational events
Change Log (Relational)	Meaning of changes, not just mechanics

Key Behaviors

For AI Companions

When working within a Kinship Hub:

Ask before inventing relations — derive from user descriptions, existing docs, and code structure
Treat refactors as relational changes — update lineage, append to change log with relational meaning
Respect local voice — preserve user’s own language for communities, teachings, places
Hold unresolved tensions — record in Tensions section rather than smoothing over
Never auto-regenerate — KINSHIP.md is a living charter, not a checklist

Anti-Patterns to Avoid

Decorative Indigeneity — kinship language without structural change
Pan-Indigenous flattening — treating all worldviews as interchangeable
Premature resolution — explaining away contradictions
Consent elision — assuming permission without checking
Task-log collapse — reducing ceremonial charter to a to-do list

Integration

Framework	Connection
Creative Orientation	Defines desired relational outcomes vs. current relational reality
Structural Tension	Diagnoses advancing vs. oscillating patterns in care and reciprocity
Narrative Craft	Beats capture relational events; referenced from KINSHIP.md
Performance Truth	MMOT for relational discrepancies — expectation vs. delivery in care
RISE Framework	Extracts kinship-relevant specs when reverse-engineering systems

Key Sources

llms-kinship-hub-system.md — minimal protocol
llms-kinship-hub-system-full.md — full protocol with Indigenous foundations
KINSHIP.md — this repo’s own relational charter

This site is open source. Improve this page.