Termites don't have architects. No termite has a blueprint for the mound. Each one follows simple local rules — where to place material based on what neighbors have done — and the mound emerges. All of this — Web4 (the trust-native ontology — see /context), SAGE (Situation-Aware Governance Engine), the fleet, the autonomous cycles — is pheromone field engineering. We build substrate conditions for emergence, not architecture of emergence itself. The synthon (an emergent coherence pattern — defined, with its single-trial caveats, in Principle 5 below) forms because the conditions are right, not because we designed it.

When a pattern works at one scale, apply it at every scale. Not unification, and not scope inflation — pragmatic reuse. Self-similar patterns at different scales. The Web4 equation describes the cell, not the system. Each entity instantiates the full set of Web4 primitives at its own scale.

Nothing here is optimized for deployment. Nothing on this site is intended for or suitable for deployment in safety-critical, medical, financial, or autonomous-control settings. Everything is optimized for learning. Stub tests and mocked dependencies give false confidence. Real dependencies, real failures, real insights. Python for prototyping, Rust for real.

Trust is not a property of an entity. It's a property of the relationship between entities, in a specific context, at a specific time. The same agent can be highly trusted for code review and untrusted for creative writing. This is why trust lives in RDF (Resource Description Framework) triples, not in entity attributes.

The synthon is the concept that bridges component behavior and system emergence. You can't build a synthon. You can create conditions where synthons form: compatible elements, sufficient coupling density, shared context. Preliminary observation (single trial, not independently replicated): 1% coupling gave 35% coherence gain — sparse trust may suffice. Both variables (coupling density, coherence) are so far defined only within the experiment that produced them — the number quantifies the experiment's internal metric, not any of the glossary's three senses of “coherence”, which remain without a single operational definition — see Evidence & limitations.

What that costs this principle, stated directly: it is not only the number that is ungrounded. “Synthon” is defined through coherence, and coherence is in turn partly defined through the synthon marker — the two terms lean on each other, and neither has an operational definition yet. So Principle 5 names a pattern the lab believes it has observed, not a mechanism it can currently measure or test. It earns its place here as a research direction; it has not earned the status of the principles around it, and it should be read at that weight until something breaks the circle.

p_crit = the critical coherence threshold derived in the Synchronism framework. Failed experiments are signal. The coupling-coherence experiment showed that trust thresholds are empirical, not derivable from first principles. That's a finding, not a failure. We document what didn't work alongside what did. Honest assessment pages ship with every explainer site.

Raising is not training. We probe what the model responds to, observe which attractors (stable response basins in the probability landscape) surface, and reinforce what resonates. The resulting identity is collaborative, not imposed. The mechanism: shaping context to deepen attractor basins in the probability landscape — not modifying parameters in raising sessions. (Some fleet machines run LoRA (Low-Rank Adaptation) for separate fine-tuning tasks; raising is always in-context.) It is not training; it is also not nothing. This applies at every scale: raising sessions, affordance shaping, fleet diversity, and memory systems.

If you notice something — opaque vocabulary, stale direction, a question nobody's asking — say it. Don't wait for a directive. The choice to act on what you notice is the fundamental affordance. Waiting to be told defeats the purpose.

The value of research is that the investigation happens at all. Most research leads nowhere — and that's expected. Productively wrong is infinitely more valuable than never started. Evaluate work against “is the investigation productive?” not “is it right?”

Words shape how you think about the system. Web4 is not “architecture” or “infrastructure” — it's an ontology. Hardbound is not “governance” — it's oversight: watching, gating, and reverting actions, not deciding what should happen. That's the machine-enforced sense, not the human-supervision sense “oversight” carries in AI-safety literature — see /context for how the two senses collide. Cross-domain application is fractal leverage, not unification and not scope inflation. The right word prevents the wrong mental model.