Lexicon admission
IPI Operational Admissibility Protocol v0.1
Status:
Working methodological and governance document developed in collaboration with participants of the Informational Physics Institute (IPI).
Version 0.1
Operationally constrained.
Non-totalising.
Revisable.
This document does not define ontology, consciousness, reality, or universal semantic closure.
Its purpose is instead to establish procedural admissibility conditions for:
• cross-framework comparison,
• semantic interoperability,
• contextual operational translation,
• residual preservation,
• and bridge-validity discipline.
The protocol therefore functions as:
• a governance layer for the IPI Lexicon,
• an admissibility discipline for cross-framework mapping,
• a semantic stabilisation protocol,
• and a procedural interoperability framework.
This document should not be interpreted as:
• a unifying ontology,
• a framework-ranking system,
• a metaphysical synthesis engine,
• or a replacement for empirical or mathematical work performed within individual frameworks.
The protocol governs the conditions under which frameworks may be compared operationally without forcing equivalence, semantic collapse, or hidden ontology importation.
1. Motivation
As multiple frameworks entered active comparison within IPI discussions, it became increasingly apparent that semantic interoperability itself required formal operational discipline.
The problem is not merely terminological disagreement.
The deeper issue is that:
• frameworks frequently operate at different operational layers,
• preserve different invariants,
• project different structures,
• embed observers differently,
• and maintain distinct admissibility domains.
Without explicit governance, several predictable failure modes emerge:
• semantic drift,
• projection collapse,
• ontology leakage,
• hidden framework assimilation,
• false equivalence claims,
• category collapse between operational layers,
• and irreversible loss of residual structure.
This protocol therefore establishes a minimal operational discipline intended to preserve structured interoperability without forcing total convergence.
The goal is not elimination of disagreement.
The goal is admissible disagreement.
2. Foundational Operational Principle
The protocol adopts the following minimal operational position:
Operational interoperability between frameworks does not require ontological equivalence.
Instead, admissibility depends upon:
• contextual localisation,
• explicit mapping discipline,
• preserved invariants,
• declared residuals,
• operational domain validity,
• and identifiable failure conditions.
Equivalence claims therefore remain:
• local,
• contextual,
• projection-sensitive,
• and operationally constrained.
3. Purpose and Non-Purpose
3.1 Purpose
The protocol exists to:
• preserve operational clarity,
• reduce semantic drift,
• support contextual interoperability,
• localise disagreement,
• preserve residual structure,
• constrain bridge claims,
• and maintain admissibility during cross-framework comparison.
3.2 Non-Purpose
The protocol does not:
• adjudicate ontology,
• define consciousness,
• validate metaphysical claims,
• establish universal semantics,
• force theoretical synthesis,
• or replace empirical science.
No framework entering this protocol is required to:
• abandon its primitives,
• inherit another framework’s ontology,
• or accept global equivalence claims.
4. Admissibility Principles
The following operational principles govern admissible interoperability.
4.1 Contextual Admissibility
All operational claims remain context-sensitive.
A mapping admissible within one operational domain may become inadmissible outside that domain.
Operational validity is therefore local rather than globally assumed.
4.2 Projection Awareness
All projections preserve only partial structure.
Projection may destroy:
• recoverability,
• distinguishability,
• experiential locality,
• or operational invariants.
Equivalent projections do not imply equivalent underlying states.
4.3 Residual Preservation
Residual structure must be explicitly declared whenever mappings occur.
Residuals may include:
• informational loss,
• phenomenological non-transportability,
• observer-local structure,
• scale-dependent divergence,
• or unresolved mechanistic gaps.
Residuals are not automatically interpreted as:
• metaphysical failure,
• proof of incompleteness,
• or hidden ontology.
4.4 Observer Embedding Awareness
Observer participation within an operational domain may constrain:
• accessibility,
• interpretation,
• actualisation,
• and representational legitimacy.
Observer embedding does not automatically imply:
• idealism,
• relativism,
• or observer-created ontology.
4.5 Recoverability Sensitivity
Recoverability must never be assumed.
Lossless translation between frameworks is exceptional rather than default.
Mappings must therefore specify:
• preserved structure,
• unrecoverable structure,
• and projection limits.
4.6 Non-Equivalence Preservation
Operational interoperability does not imply:
• ontological identity,
• semantic identity,
• phenomenological equivalence,
• or mechanistic equivalence.
Framework disagreement remains admissible.
5. Layer Separation Discipline
The protocol distinguishes several operational categories which should not be collapsed into a single undifferentiated framework.
These include:
• semantic structures,
• operational layer taxonomies,
• bridge-validity architectures,
• phenomenological structures,
• representational systems,
• empirical prediction systems,
• and ontology claims.
Failure to preserve these distinctions risks semantic collapse and hidden framework importation.
The current IPI discussions have already demonstrated the importance of maintaining explicit separation between:
• the lexicon itself,
• operational positioning systems,
• and bridge-validity requirements.
For example:
• The lexicon defines admissibility-sensitive terminology.
• OA/L-style operational taxonomies localise where mechanisms operate.
• Bridge-discipline frameworks constrain admissible transformations between frameworks.
These objects should remain operationally distinct.
6. Mapping Discipline Requirements
All bridge claims or interoperability proposals should specify:
6.1 Source Structure
The originating framework, representation, or operational domain.
6.2 Target Structure
The framework or operational domain receiving the mapping.
6.3 Mapping Type
Examples include:
• projection,
• restriction mapping,
• morphism,
• approximation,
• analogy,
• operational equivalence,
• phenomenological correspondence,
• or empirical overlap.
6.4 Preserved Invariants
The structure claimed to remain operationally stable across the mapping.
6.5 Residual Structure
The structure not preserved.
Residuals must be explicitly named wherever possible.
6.6 Operational Domain
The contextual region within which the mapping remains admissible.
6.7 Failure Conditions
Conditions under which:
• the mapping collapses,
• equivalence becomes inadmissible,
• or operational interoperability fails.
7. Governance Discipline
7.1 Term Governance
Proposed additions to the lexicon should include:
• proposed term,
• operational role,
• domain of use,
• preserved invariants,
• admissibility conditions,
• residual or failure conditions,
• overlap analysis,
• notation conflicts,
• and ontology-neutrality declaration.
7.2 Notation Conflict Awareness
Shared notation should not be assumed neutral automatically.
The current discussions have already demonstrated the possibility of:
• notation overlap,
• symbol reuse,
• and operational ambiguity between frameworks.
Notation conflicts should therefore be explicitly identified.
7.3 Provisional Status
All protocol structures remain:
• provisional,
• revisable,
• operationally constrained,
• and subordinate to methodological clarity.
8. Residual Declaration Discipline
The protocol adopts explicit residual declaration as a central methodological requirement.
Whenever frameworks are compared, participants should attempt to specify:
• what survives projection,
• what remains inaccessible,
• what is observer-local,
• what becomes non-recoverable,
• and what remains operationally undecidable.
Residual tracking is treated as a stabilising feature rather than a failure state.
The protocol therefore rejects the assumption that successful interoperability requires elimination of disagreement.
Instead:
structured disagreement may itself remain admissible.
9. Operational Localisation and Vertical Positioning
Several IPI discussions have highlighted the importance of distinguishing between operational layers.
Frameworks may operate primarily within:
• generative domains,
• admissibility or constraint domains,
• representational domains,
• phenomenological domains,
• or realised physical domains.
Operational positioning systems such as:
• OA structures,
• RA structures,
• and related vertical taxonomies,
attempt to localise where mechanisms function without necessarily forcing ontological equivalence.
The protocol does not enforce any single taxonomy.
However, it requires that:
• operational localisation be made explicit,
• layer transitions be identified,
• and bridge claims specify where cross-layer transformations occur.
10. Examples of Admissible Structured Disagreement
The protocol does not attempt to erase disagreement between frameworks.
Instead, it attempts to preserve operational legibility during disagreement.
Several recent IPI exchanges illustrate this behaviour.
10.1 UIFT and FFGFT Scale Divergence
Recent discussion between Onur Teker and Johann Pascher demonstrated:
• mathematical overlap at the thermodynamic level,
• divergence at cosmological scale predictions,
• explicit localisation of disagreement,
• and empirical bridge conditions.
Importantly:
• the frameworks were not collapsed into equivalence,
• residual divergence remained explicit,
• and empirical discriminability was preserved.
This constitutes an example of admissible structured disagreement.
10.2 Semantic Neutrality Concerns
Discussions involving Diana Haskins and Eric Porter highlighted the risk that:
• semantic interoperability systems may unintentionally import hidden commitments,
• notation may cease to remain neutral,
• or interoperability layers may become assimilative.
These concerns are treated within the protocol as stabilising governance constraints rather than obstacles.
10.3 Cross-Layer Localisation
José Guevara Calderon’s operational layer proposal highlighted the need to distinguish between:
• generative structures,
• admissibility structures,
• representational systems,
• phenomenological structures,
• and physical realisation domains.
The protocol treats such separation attempts as admissibility-preserving operational localisation tools rather than ontology claims.
11. Relationship to Existing Frameworks
This protocol does not supersede existing frameworks.
It instead attempts to preserve operational interoperability between partially overlapping systems.
Frameworks presently discussed within IPI include, but are not limited to:
• Dot Theory,
• UIFT,
• FFGFT,
• HPF-related architectures,
• PM-oriented structures,
• recursive epistemic systems,
• informational field proposals,
• contextual admissibility systems,
• and phenomenological architectures.
The protocol does not require these frameworks to:
• share ontology,
• share primitives,
• share semantic closure,
• or share mechanistic commitments.
Instead, it attempts to preserve:
• explicit localisation of agreement,
• explicit localisation of disagreement,
• bridge-validity discipline,
• and operational legibility.
12. Failure Conditions
Operational interoperability becomes inadmissible when:
• frameworks are collapsed into equivalence without declared invariants,
• residual structure is suppressed or ignored,
• ontology claims are silently imported,
• notation ambiguity becomes unresolved,
• operational domains are exceeded,
• projection loss is ignored,
• or empirical distinguishability is erased.
The protocol therefore treats:
• semantic restraint,
• explicit locality,
• and declared incompleteness
as stabilising methodological features.
13. Concluding Statement
This protocol should not be interpreted as an attempt to construct a universal meta-theory.
Its purpose is narrower.
The protocol exists to preserve operational admissibility during comparison between partially overlapping representational systems.
It therefore functions as:
• a governance layer,
• a semantic restraint discipline,
• a contextual interoperability protocol,
• and an admissibility-preserving bridge structure.
The protocol remains:
• provisional,
• revisable,
• non-totalising,
• and subordinate to operational clarity.
In this sense, the protocol is not intended to eliminate disagreement.
It is intended to preserve the conditions under which disagreement may remain operationally meaningful without collapsing into semantic incoherence.
Attribution and Collaborative Status
This document emerged through active discussion and methodological exchange within the Informational Physics Institute community.
The protocol incorporates and responds to operational concerns, distinctions, proposals, and cautions raised across discussions involving multiple contributors, including:
• José Tomas Guevara Calderon,
• Diana Haskins,
• Eric Porter,
• Johann Pascher,
• Onur Teker,
• Peter Austin,
• Boris Kriger,
• and other participating researchers.
The document should therefore be treated as an evolving collaborative methodological effort rather than a closed or authorially finalised system.
