Reference Model Draft

Model Layers: The idea is to enable model representations being equivalent
(containing the same data) to be switched back an forth between layers
representations to be used for the most appropriate task for the
representation.

Index, Naming, Registry Services: Functional APIs MCP Wrappers (servers
resources, tools, prompt templates).

Embeddings: FCA Contexts / Lattices. Each ID instance is unique and
assigned a prime number ID at creation time. ID embeddings contains the
prime numbers of all ID's IDOccurrence occurrence embeddings. IDOccurrence
embeddings (those of an ID occurring in a specific context) contains the
primes of the reified occurring ID embeddings and those of the occurring
ID's context embeddings.

Embeddings similarity: IDs, Occurrences sharing the same primes for their
embeddings in a given context. FCA Concept Lattice Clustering.

REFERENCE MODEL LAYER (Aggregation) PACKAGE:

IDOcurrence : ID
- id : ID
- context : IDOccurrence
- embeddingPrimes : long[]

ID
- primeID
- resource : string
- occurrences (order / dimensions)
- embeddingPrimes : long[]

GRAPH MODEL LAYER (Alignment) PACKAGE:

Statement : IDOccurrence
- subject : IDOccurrence (SubjectKind)
- predicate : IDOccurrence (PredicateKind)
- object : IDOccurrence (ObjectKind)

Type : ID (Same predicates / attributes sets aggregate)

State : ID (Same Type values sets aggregate)

Kind : IDOccurrence / Statement (Property Graph Annotations)
Example: (aSubject, aType, aState) : SubjectKind

Data Statements, Schema (Kinds) Statements.

DOM / ACTOR / ROLE MODEL LAYER (Activation) PACKAGE:

Class : Instance
- string / ID
- fields : <string, Class>
- instances

Instance : IDOccurrence
- string / ID
- attrs : <string, Instance>
- class

Context

Role

Dataflow : Context

Interaction

Actor

Transform : Interaction

Everything is depicted in the last "Implementatîon" section of the attached
document

Regards,
Sebastian.