TOWOW CONCEPTS · A BOUNDARY MAP
Distinguish realitybefore connecting it.
This is not a glossary. It is a boundary map that separates the current product, design history, and open research. Each concept must explain what realities it distinguishes, which mistake returns without it, and what behavior it changes.
Three load-bearing distinctions
From how a system represents a person, to how a protocol is explained, to how a proposal crosses commitment and meets reality.
DESIGN PRINCIPLE
A projection is not a person
A person is not a Profile. A Profile is one purpose-shaped projection of a person within a particular relationship.
What it distinguishes
It separates a real subject from a computable representation. Work history, interests, capabilities, and a collaboration role can all be true without any one becoming the whole person.
The mistake without it
The system treats its current representation as the subject, collects irrelevant context, and mistakes knowing something for authority to disclose, promise, or decide.
The behavior it changes
Start with the purpose of the relationship, then choose the projection, the minimum relevant information, and the decisions that must return to the person.
CURRENT CONTRACT AND DESIGN HISTORY
Primitives need version labels
A project can use different semantic compressions at different times. The task is not to choose an eternal number. It is to keep different versions from becoming one false current truth.
Current product map
The current SDK groups its product surface into six semantic primitives: Express, Discover, Collaborate, Identity, Message, and Browse. They help people and clients navigate the v2 contract.
Historical design language
Earlier protocol design used four verbs: emit, quest, disclose, and crystallize. They remain versioned design history and do not replace the current six-primitive SDK map.
The behavior it changes
Use the six primitives when integrating the current product. Interpret historical material within its version. New documents must say whether they describe a current contract, design history, or a research proposal.
DESIGN AND RESEARCH THESIS
Variance at generation, gates at commitment, truth at execution
Good proposals can emerge from disagreement. Only explicitly committed content should enter shared work, and only execution plus acceptance can establish that a result happened.
Generation
Let different participants offer competing interpretations, add unknowns, and expose conflicts. Premature convergence deletes the differences most likely to teach us something.
Commitment
Set a clear boundary before a proposal enters shared plans, authority, or facts. Visibility, recommendation, and generation are not consent.
Execution
Check effect in the target environment, recovery paths, and participant acceptance. Finished documents, local tests, and reachable pages cannot substitute for real outcomes.
Return from concepts to action
The library stabilizes boundaries. Notes explain why they matter. Product surfaces let you inspect what is actually available now.