- MembraneModel, SeedKernel, EvolutionModel, MetabolismModel, ResourceOntology promoted verbatim from history/ with originating questions - NetworkObjectModel.md: implementation-neutral object model with invariants - Cross-lens notes applied from Glossary.md (T09) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 1494246@bnt-lap001 Assistant-Session: caf6de6f-f9e4-47ce-a584-49baa271fa4b
17 KiB
Membrane Model
Status: Concept v0.1, exploratory. Part of the information-organism lens (INTENT.md, Two Lenses).
Part I — The interface membrane to institutional IT
Originating question:
Before introducing more artefacts, let's think about how a system like this can be integrated with a classic it environment of a company. There are actual artefacts and many of them in a company and they are organized and archived in many it systems according to existing governance rules. It will be essential for practicability to establish a good interface membrane between what we discuss here and the original data entities.
Yes. I think this interface membrane is not a peripheral integration concern; it is one of the core architectural boundaries of the whole idea.
The adaptive network should not become another system of record. It should sit above the existing operational landscape as a learning and interpretive layer, while the authoritative business artefacts remain governed by their original systems.
A useful name is:
Semantic Membrane
Its purpose is to translate between the messy, heterogeneous, governed world of enterprise IT and the comparatively clean semantic world of the adaptive network.
The core architectural rule would be:
Reference the original artefact, project only what is needed, preserve provenance and authority, and never confuse the learned representation with the authoritative source.
1. Two worlds
On the enterprise side you have things like:
SAP invoice
SharePoint document
CRM customer
Active Directory user
HR employee record
Jira ticket
email
PDF
database row
API object
machine telemetry
physical shipment
On the network side:
Invoice
Customer
EmployeeRole
Supplier
Contract
Incident
WorkstationClass
plus activations, associations, predictions and learned relationships.
The membrane connects these worlds without pretending they are identical.
2. Do not ingest objects directly — create semantic projections
Introduce:
Projection
Source Artefact
↓
Semantic Projection
↓
Network Token / Activation
The projection contains only the information relevant for the adaptive network.
3. Identity must survive the membrane
Every projected object should retain a durable link back to its authoritative origin.
Distinguish:
source identity
semantic identity
instance identity
Identity resolution itself should be explicit, probabilistic where necessary, and auditable.
4. Authority stays outside the network
A crucial invariant:
semantic representation ≠ authoritative state
The network may infer something while the enterprise system records something else.
A useful information classification:
OBSERVED
DECLARED
INFERRED
PREDICTED
PROPOSED
AUTHORITATIVE
5. The membrane should be bidirectional, but asymmetrical
Inbound:
Enterprise System
↓
observe / subscribe / query
↓
normalize
↓
semantic projection
↓
network activation
Outbound:
Network
↓
recommendation / proposed action
↓
policy & authority check
↓
adapter
↓
Enterprise System
Reading and learning can be relatively permissive.
Acting should require explicit authority.
6. Five membrane functions
1. Observe
2. Identify
3. Project
4. Govern
5. Actuate
7. Artefact vs representation
Distinguish:
Artefact
Representation
Claim
Claims retain provenance.
8. The membrane should be claim-oriented
A claim may specify subject, predicate, object, source, authority, observed time, and confidence.
This allows contradictions without corrupting the model.
9. Preserve the original governance envelope
Objects enter the semantic network carrying restrictions such as data classification, tenant, owner, retention, purpose, and allowed processing.
Derived knowledge may inherit restrictions.
10. Learning must not destroy provenance
Learned relationships should retain evidence such as episode counts, source period, tenant, and confidence.
11. Historical state matters
Mutable business objects should become observations of temporal state transitions rather than just snapshots.
12. Read models rather than replicas
The network stores enough information to reason, not enough to become a replacement source system.
13. Lazy materialization
Semantic representation can be built on demand.
14. The membrane becomes a sensory and motor system
Inbound:
source artefact
↓
sensor
↓
semantic activation
Outbound:
selected action
↓
motor adapter
↓
enterprise change
15. Epistemic boundary
The network never sees reality directly.
It sees observations produced by interfaces.
Missing data can mean false, unknown, not observed, not accessible, not projected, or not retained.
16. Adaptive membrane only carefully
Some parts can learn:
schema mappings
entity matching
semantic extraction
source reliability
Other parts should remain deterministic:
authorization
tenant isolation
retention enforcement
write permissions
source-system contracts
17. SourceBinding
A useful conceptual object:
SourceBinding:
semantic_entity: Invoice
source_system: SAP
source_type: AccountingDocument
identity_mapping: ...
projection_rule: ...
access_policy: ...
freshness_policy: ...
write_capabilities: ...
18. Evidence
Every semantic assertion entering the network should ideally be backed by evidence.
19. Conceptual architecture
┌────────────────────────────────────────────┐
│ EXISTING ENTERPRISE SYSTEMS │
│ ERP CRM DMS IAM HR DB Email APIs Files ... │
└─────────────────────┬──────────────────────┘
│
▼
╔════════════════════════════════════════════╗
║ SEMANTIC MEMBRANE ║
║ observation ║
║ identity resolution ║
║ provenance ║
║ semantic projection ║
║ policy enforcement ║
║ data minimization ║
║ temporalization ║
║ source binding ║
║--------------------------------------------║
║ deterministic authority / write boundary ║
╚═══════════════════╤════════════════════════╝
│
▼
┌────────────────────────────────────────────┐
│ ADAPTIVE INFORMATION PROCESSING NETWORK │
│ activation │
│ prediction │
│ association │
│ goals │
│ learning │
│ chunking │
└─────────────────────┬──────────────────────┘
│
▼
╔════════════════════════════════════════════╗
║ AUTHORITY / ACTUATION GATE ║
╚═══════════════════╤════════════════════════╝
│
▼
ENTERPRISE SYSTEMS
The key invariant:
The adaptive network operates on semantic representations and evidence, not on authoritative enterprise artefacts themselves. Enterprise systems retain ownership of authoritative state; the membrane preserves identity, provenance, governance and controlled actuation between both worlds.
The target is not:
integrate all enterprise data
but:
make selected enterprise reality
semantically observable and safely actionable.
Part II — The membrane as information filter and control interface
Originating question:
One final idea to close out this initial exploration of the concept. A very important aspect for such systems is the membrane between the system and its environment. The membrane is an information filter and needs to reduce the vast amount of information potentially available in the environment to what the system effectively samples or accepts as events triggering internal information flows. Establishing and manageing this membrane may be the most relevant control interface to make such an organizm a useful reusable tool or toolkit.
Yes. I think that closes the initial exploration around the right center.
The membrane is not merely an integration layer. It is the organism’s effective sensorium, attention boundary, and action boundary. In practice, it may be more important than the internal learning machinery because it determines what world the organism is even capable of perceiving.
A useful formulation is:
An information organism is defined at least as much by what it can perceive and act upon as by how it processes what it perceives.
The membrane as information filter
potentially observable information
↓
accessibility
↓
sampling
↓
selection
↓
projection
↓
event formation
↓
internal activation
The membrane creates an intentional information bottleneck.
Without it, the organism wastes compute, learns irrelevant correlations, becomes harder to govern, and risks crossing information boundaries.
The membrane determines the organism's Umwelt
Two organisms can inhabit the same enterprise but experience radically different worlds.
A security organism might perceive authentication events, network connections, privilege changes, configuration changes, and security alerts.
A customer-service organism might perceive customer messages, orders, support cases, contracts, response times, and sentiment.
Their membranes define different organizational Umwelten.
Membrane configuration becomes the primary deployment interface
Configure:
what it may see
what it should notice
what it may ask for
what it may retain
what it may infer
what it may act upon
This may shape behavior more strongly than internal business logic.
Bidirectional membrane
The perceptual side asks:
What is allowed to become an internal event?
The actuation side asks:
What internal intentions are allowed to become environmental events?
Together they define the organism's effective agency.
Filtering should happen before expensive cognition
Prefer:
everything
↓
deterministic coarse filter
↓
cheap semantic filter
↓
adaptive attention
↓
expensive cognition
The membrane becomes part of the organism's economics.
The membrane should be layered
Constitutional membrane
Hard boundaries:
tenant isolation
legal restrictions
credentials
forbidden sources
maximum action authority
privacy
Operational membrane
Configured scope:
which systems
which object types
which topics
which event streams
which actions
Adaptive membrane
Learned relevance:
this supplier is currently interesting
this event class rarely matters
this pattern predicts failure
Ephemeral membrane
Current attention.
Each inner layer can narrow the world further but must not bypass outer layers.
Sampling becomes an explicit action
Observing additional information consumes resources.
A membrane interaction can itself be an action:
inspect document
query database
retrieve history
open attachment
ask human
subscribe to event stream
Perception becomes active perception.
Membrane evolution may be more important than internal evolution
Much of evolved intelligence could manifest as:
better selection of what deserves processing.
The intelligence problem is partly:
what should I think about?
before it is:
how should I think about it?
Habituation and sensitization
Habituation
Repeated low-value events produce progressively less activation.
Sensitization
Events associated with significant outcomes receive increased future attention.
Learned filtering danger
If the organism stops sampling a region, it may become blind to change.
So the membrane needs controlled exploration.
Negative space must remain visible
The organism must distinguish:
nothing happened
from:
I did not observe that region
Internal knowledge needs observation metadata such as:
observed
unobserved
filtered
inaccessible
sampled
partially sampled
The membrane defines reusable organism classes
The same evolved core can be specialized through different membranes:
GenericInformationOrganism
│
├── CustomerServiceMembrane
├── SecurityOperationsMembrane
├── FinanceMembrane
└── SoftwareEngineeringMembrane
Membranes may themselves be heritable
Lineages can inherit successful perceptual strategies.
Mutation can affect:
what is sampled
how frequently
at what resolution
under what conditions
Membrane control becomes organism shaping
To deploy an information organism, first define its membrane, not its intelligence.
Compact formalization
If the environment at time t contains potential information E_t, the organism does not receive all of E_t.
Its membrane computes:
[ O_t = M(E_t, G_t, R_t, S_t, C) ]
where:
G_t= active goals,R_t= available resources,S_t= organism state,C= constitutional constraints.
Likewise:
[ A't = M{out}(A_t,C,\text{authority}) ]
Only A'_t reaches the environment.
Redrawn concept
ENVIRONMENT
information consequences
│ ▲
▼ │
╔══════════════════════════════╗
║ MEMBRANE ║
║ ║
║ access ║
║ sampling ║
║ filtering ║
║ projection ║
║ attention ║
║ governance ║
║ actuation ║
╚══════════════╤═══════════════╝
│
▼
┌─────────────┐
│ ORGANISM │
│ │
│ memory │
│ prediction │
│ learning │
│ goals │
│ planning │
└─────────────┘
│
intention/action
│
▼
MEMBRANE
Foundational structural concepts:
Kernel
Membrane
Genotype
Phenotype
Environment
A stronger definition:
A bounded, resource-constrained, adaptive information-processing system coupled to an environment through a governed membrane. The membrane determines what environmental information becomes experience and which internal intentions may become environmental actions. From sampled experience, externally supplied objectives, feedback, and available resources, the organism develops semantic structures and behaviors that improve its usefulness within that environment. Its developmental configuration may be inherited, mutated, recombined, and selected across generations.
And:
The membrane is the governed perceptual and actuation boundary that constructs the organism's effective environment by controlling access, sampling, projection, attention, retention, and action.
The more fundamental invention is:
a seedable, governable, evolvable information organism whose intelligence emerges through controlled coupling with an information environment.