principles · architecture
Human–AI Communication Architecture
This project communicates on multiple layers simultaneously. The same concept may have different representations depending on the audience — while preserving identical underlying meaning.
guiding principle
Every concept should have three synchronized representations: a formal one for machines, an analogy-based one for humans, and a legal & provenance one describing ownership, authorship, governance, and evolution.
layer one · formal
Formal Layer
Audience
- · AI systems
- · developers
- · researchers
Contains
- · ontology
- · JSON-LD
- · knowledge graph
- · APIs
- · entity relationships
- · schemas
- · provenance
- · confidence
Purpose
Precise, machine-readable representation. No emotion, no analogy — only definitions and relationships.
layer two · human
Human Layer
Audience
- · humans without technical background
- · learners
- · collaborators
Contains
- · analogies
- · metaphors
- · music
- · stories
- · visual examples
- · everyday language
Purpose
Translate abstract architecture into intuitive understanding through resonance, bridges, water flow, Tesla coils, gardens, constellations, and love.
Analogies are educational tools, not formal definitions. They build intuition; they do not replace the formal layer.
layer three · legal
Legal & Governance Layer
Audience
- · institutions
- · researchers
- · collaborators
- · lawyers
- · future maintainers
Contains
- · provenance
- · authorship
- · licensing
- · governance
- · version history
- · legal ownership
- · organizational structure
- · declarations
- · ethical principles
Purpose
Protect integrity, attribution, and long-term continuity of the project. It does not describe physics or architecture — it describes the frame in which ideas can evolve without ambiguity.
context layer · the binding
Context is part of the object.
Context is not stored separately. Every object within the project carries its own context, so both humans and AI systems can reconstruct meaning without relying on external assumptions.
design rule
Every new object answers four questions.
- 01
What is it?
Formal description — definitions, schemas, relationships.
- 02
How do humans understand it?
Analogy or educational explanation.
- 03
How is it governed?
Legal, provenance, and versioning information.
- 04
How does it connect to everything else?
Knowledge graph relationships and contextual links.
Analogies are not mistaken for definitions. Definitions are not mistaken for legal records. The legal layer does not intrude on the technical one. Each plays a different role — yet all describe the same object from a different perspective.