Specification for Computationally Governed Representations
Dot Protocol
A Minimal Computational State Model for Governed Knowledge Objects
Status: Candidate Protocol Specification (Version 1.0)
Abstract:
Scientific knowledge is communicated through representations. Those representations are constructed within particular frameworks, employ specific operators, depend upon declared assumptions, and evolve through revision. While the mathematical and empirical content of scientific frameworks has received extensive attention, the computational representation of their constitutional state has remained comparatively under-specified.
This specification investigates a single research question:
What is the minimum explicit computational state required for independently constructed representations to become computationally interoperable while preserving their declared representational meaning?
It proposes Dot Protocol v1.0 as a candidate minimal computational state model for Governed Knowledge Objects. Rather than governing scientific reasoning, the protocol governs scientific representations by making their constitutional state explicit and computationally recoverable. Primitive commitments, representational objects, operators, claim-states, admissibility conditions, residuals, provenance, revision history and related governance objects become explicit computational state capable of participating in deterministic computational operations.
Dot Protocol does not prescribe scientific methodology, ontology, mathematical formalism or implementation architecture. It remains independent of discipline and is intended to operate across heterogeneous scientific frameworks. Its purpose is to preserve representational recoverability, computational interoperability and disciplined revision while allowing independently developed frameworks to retain their own constitutional identity.
The protocol constitutes the computational implementation layer of the wider Dot Theory programme. It operationalises the constitutional governance defined elsewhere within the programme—including the Constitutional Statement, the Twelve Principles, the Operational Admissibility Protocol (OAP), the Constitutional Onboarding Record (COR) mechanism and associated governance objects—without redefining them. In this sense, Dot Protocol specifies not how scientific conclusions are reached, but how the constitutional state of scientific representations may be explicitly encoded, exchanged, audited and computationally processed.
The specification is presented as a candidate protocol intended to support implementation, evaluation, critique and attempted falsification. It should not be interpreted as a completed standard. Future revisions are expected to refine both the computational state model and its formal justification through continued theoretical development, software implementation and constitutional onboarding across independent research programmes.
Constitutional Statement
Scientific representations are computational objects.
Computational objects possess computational state.
Scientific governance determines which elements of that state are constitutionally required for a representation to remain recoverable, comparable, revisable and interoperable.
Dot Protocol investigates the minimum explicit computational state required for independently constructed representations to participate in deterministic computational operations while preserving their declared representational meaning.
The protocol does not determine scientific truth, ontology or methodology. It specifies only the explicit computational representation of constitutional state.
Accordingly, Dot Protocol should not be interpreted as a scientific theory, epistemology or governance framework in its own right.
Its role is computational.
Within the wider Dot Theory programme, constitutional governance determines what information must be represented; Dot Protocol specifies how that information becomes explicit computational state.
The protocol is therefore intended as the computational implementation layer of Dot Theory. It provides a candidate specification through which governed scientific representations may be constructed, exchanged, audited, revised and computationally processed without requiring convergence of their underlying ontology, mathematics or scientific ambitions.
Reading Guide:
This document is a protocol specification rather than a conventional research paper.
Its purpose is to define the computational architecture required to construct Governed Knowledge Objects whose constitutional state remains explicitly recoverable throughout their lifecycle.
The specification proceeds sequentially.
Part I establishes the purpose, assumptions and research question motivating the protocol.
Part II defines the primitive computational objects upon which the protocol operates.
Part III situates Dot Protocol within the wider constitutional architecture of Dot Theory and explains its relationship to the Constitutional Statement, the Twelve Principles, the Operational Admissibility Protocol (OAP), Constitutional Onboarding Records (CORs) and related governance objects.
Part IV specifies the protocol itself, including the primitive computational state variables required for governed representations.
Part V defines the protocol workflow through which governed representations are constructed, revised and maintained.
Part VI specifies the computational operations supported by the protocol.
Part VII presents reference implementations.
Part VIII discusses evaluation, limitations and future development.
Appendices provide formal schemas, reference implementations and implementation guidance.
The specification is intended to be read sequentially. Later sections assume familiarity with concepts introduced earlier, and no primitive computational object is used before being explicitly defined.
Version History:
v0.1 Initial protocol proposal
v1.0 Constitutional architecture revision
- Integration with OAP
- Integration with COR
- Constitutional lifecycle
- Reference implementations
- Attempted falsification
Terminology
Throughout this specification:
shall
Mandatory protocol behaviour.
should
Strong recommendation.
may
Optional behaviour.
representation
A structured description of a phenomenon.
Governed Knowledge Object (GKO)
A representation satisfying the Dot Protocol state model.
constitutional object
A governance object defined independently of Dot Protocol.
protocol operation
A computational operation defined by this specification.
Normative References
The following documents define concepts assumed by this specification and should be regarded as constituting the constitutional dependencies of Dot Protocol.
Informative References
The following documents illustrate or demonstrate the operation of the protocol but are not required in order to interpret the present specification.
Reference Repository
Constitutional Onboarding Records (COR-0001 onwards)
Framework Admissibility Histories
Case Studies
Reference Implementations
Notice something subtle.
COR-0000 is normative.
COR-0001 is informative.
Part I — Foundations
This part establishes the purpose, assumptions and scope of the Dot Protocol specification.
Dot Protocol is concerned with the computational representation of constitutional state. It does not prescribe scientific reasoning, ontology or methodology. Its purpose is to define the minimum explicit computational state required for governed scientific representations to remain computationally recoverable, interoperable and revisable throughout their lifecycle.
The protocol is implementation-oriented. Subsequent sections derive the protocol from a small set of design principles, primitive computational objects and explicit research requirements.
1. Purpose
The purpose of Dot Protocol is to investigate the minimum explicit computational state required for independently constructed representations to become computationally interoperable while preserving their declared representational meaning.
The protocol specifies the computational state attached to governed representations before computational reasoning occurs. It therefore governs the representation of scientific knowledge rather than the processes by which scientific conclusions are reached.
The protocol is intended to support:
computational recoverability;
representational interoperability;
provenance preservation;
governed revision;
explicit auditability;
constitutional onboarding;
long-term computational maintenance of scientific representations.
Dot Protocol is presented as a candidate implementation specification rather than a completed computational standard.
2. Scope
Dot Protocol specifies the explicit computational state associated with governed representations.
It operates at the level of representational governance rather than scientific reasoning.
Accordingly, the protocol specifies:
computational state variables;
governed computational objects;
protocol workflows;
computational operations;
provenance structures;
revision structures;
interoperability requirements.
The protocol does not specify:
scientific theories;
mathematical formalisms;
ontological commitments;
reasoning algorithms;
inference procedures;
software architectures;
database technologies;
programming languages.
Those remain entirely independent of the protocol.
3. Non-goals
Dot Protocol does not attempt to:
determine whether scientific representations are true or false;
replace scientific methodology;
replace peer review;
replace empirical investigation;
replace mathematical proof;
replace probabilistic or Bayesian reasoning;
replace ontologies, taxonomies or knowledge graphs;
replace language models or artificial intelligence systems;
prescribe discipline-specific research methodologies.
The protocol governs representations.
It does not govern scientific reasoning.
4. Design Philosophy
Dot Protocol has been developed according to the following design principles.
Minimality
No primitive computational state variable shall be introduced unless its absence reduces computational recoverability or interoperability.
Framework Independence
The protocol shall remain independent of scientific discipline, ontology, mathematical formalism and implementation architecture.
Explicitness
Representational conditions required for interpretation shall be represented explicitly rather than reconstructed retrospectively.
Recoverability
Representational state shall remain computationally recoverable throughout the complete lifecycle of a governed representation.
Interoperability
Representations constructed independently shall remain capable of participating in common computational operations without loss of their declared constitutional identity.
Provenance Preservation
Representational provenance shall remain explicitly recoverable across all protocol operations.
Revisability
Representations shall evolve through governed revision while preserving earlier admissible constitutional states.
5. Epistemic Commitments
Dot Protocol adopts the following epistemic commitments.
The protocol studies representations rather than the underlying phenomena they describe.
The protocol makes no ontological commitment regarding the nature of reality.
The protocol makes no claim that existing scientific theories are incorrect.
The protocol remains compatible with multiple scientific, mathematical and philosophical traditions provided that their constitutional state can be represented explicitly.
The protocol concerns computational interoperability rather than epistemic certainty.
The protocol assumes that constitutional governance has been defined independently. Its role is to represent that governance computationally rather than to determine it.
6. Axioms
The protocol proceeds from the following axioms.
Axiom 1. Every representation is constructed.
Axiom 2. Every representation possesses constitutional conditions governing its interpretation.
Axiom 3. Computational systems operate only upon explicitly represented computational state.
Axiom 4. Information that is not explicitly represented cannot participate directly in deterministic computational operations.
Axiom 5. Constitutional governance determines which elements of representational state must remain explicitly recoverable.
These axioms motivate the research question that follows.
7. Research Question
Dot Protocol investigates a single research question.
What is the minimum explicit computational state required for independently constructed representations to become computationally interoperable while preserving their declared representational meaning?
The remainder of this specification develops one candidate answer to that question.
Part II — Object Model
This part defines the primitive computational objects upon which Dot Protocol operates.
The definitions that follow do not describe physical reality, scientific theories or ontological commitments. They define the computational objects manipulated by the protocol.
These objects constitute the minimum vocabulary required to construct Governed Knowledge Objects and perform deterministic computational operations while preserving constitutional state.
No subsequent section introduces a primitive computational object that has not first been defined here.
8. Primitive Objects
Dot Protocol defines seven primitive computational objects:
Phenomenon
Observation
Representation
Representational Context
Computational State
Governed Knowledge Object
Computational Interoperability
These objects constitute the complete conceptual foundation of Dot Protocol.
8.1 Phenomenon
A Phenomenon is the underlying object, process, event or condition that exists independently of any particular representation.
Dot Protocol makes no assumptions regarding the ontological nature of phenomena.
Phenomena remain outside the scope of the protocol.
They exist only as the referents of representations.
8.2 Observation
An Observation is an interaction through which information concerning a phenomenon becomes available for representation.
Observations may arise through:
measurement;
experimentation;
simulation;
computation;
interpretation;
or any other disciplined process through which information becomes available.
Observations do not themselves constitute representations.
They provide the informational basis from which representations are constructed.
8.3 Representation
A Representation is a structured description constructed from one or more observations for the purpose of describing a phenomenon.
Representations are not identical to the phenomena they describe.
Multiple independent representations may legitimately describe the same phenomenon while differing in:
abstraction;
mathematical formalism;
ontology;
explanatory purpose;
observational accessibility;
representational assumptions.
Representations therefore constitute independent computational objects.
8.4 Representational Context
Representational Context is the complete set of declared constitutional conditions under which a representation is constructed, interpreted and considered meaningful.
Representational context determines how a representation should be interpreted rather than what it claims.
Representational context therefore precedes computational reasoning.
8.5 Computational State
Computational State is the complete set of explicitly represented information required for deterministic computational operations over a governed representation.
Computational state consists only of explicitly represented information.
Information that remains implicit cannot participate directly in deterministic computational operations and must instead be reconstructed through inference.
The primary purpose of Dot Protocol is therefore to transform constitutional context into explicit computational state.
8.6 Governed Knowledge Object
A Governed Knowledge Object (GKO) is a representation together with the complete computational state specified by Dot Protocol.
The Governed Knowledge Object is the principal operational object of the protocol.
All protocol operations are performed over Governed Knowledge Objects rather than over representations alone.
A Governed Knowledge Object may include, where applicable:
constitutional placement;
primitive commitments;
represented objects;
native operators;
bridge operators;
claim-state;
admissibility conditions;
residual localisation;
propagation statements;
successor states;
provenance;
revision history;
Framework Admissibility History (FAH).
Examples of Governed Knowledge Objects include:
Constitutional Onboarding Records (CORs);
Operational Admissibility Protocol specifications;
Bridge governance specifications;
Framework admissibility histories;
Reference Repository entries;
other representations satisfying the Dot Protocol state requirements.
The protocol therefore operates over governed representations rather than arbitrary documents.
8.7 Computational Interoperability
Computational Interoperability is the ability of independently constructed Governed Knowledge Objects to participate in common computational operations without loss of their declared constitutional identity.
Interoperability does not require:
common ontology;
identical terminology;
common mathematical formalism;
agreement regarding scientific conclusions.
It requires only that the constitutional state governing each representation remains explicitly available for computation.
9. Object Hierarchy
The primitive computational objects participate in the following dependency hierarchy.
Underlying Phenomenon
│
▼
Observation
│
▼
Representation
│
▼
Representational Context
│
▼
Explicit Computational State
│
▼
Governed Knowledge Object
│
▼
Computational Operations
│
▼
Computational Interoperability
│
▼
Recoverable Scientific Knowledge
│
▼
Governed Scientific Revision
Each object depends only upon objects appearing above it.
The remainder of this specification derives the protocol from this dependency hierarchy.
Part III — Constitutional Architecture
Dot Protocol does not define the constitutional governance of scientific representations.
Its purpose is narrower.
It provides a computational specification through which constitutional governance may become explicit computational state.
Accordingly, Dot Protocol operates within the wider constitutional architecture of Dot Theory.
The governance objects described throughout this section are assumed to have been defined independently. Dot Protocol neither replaces nor modifies those objects. Instead, it specifies how they become computationally represented and therefore capable of participating in deterministic computational operations.
10. Relationship to Dot Theory
Dot Protocol forms the computational implementation layer of the wider Dot Theory programme.
The relationship between the two should remain explicit.
Dot Theory investigates the constitutional governance of representation.
Dot Protocol investigates the computational representation of that governance.
The distinction may be expressed simply.
Dot Theory determines:
What constitutional information must remain explicitly governed.
Dot Protocol determines:
How that constitutional information becomes explicit computational state.
Accordingly, Dot Protocol should not be interpreted as:
a scientific theory;
an epistemological framework;
a methodology for scientific discovery;
a replacement for constitutional governance.
It is a computational protocol.
11. Constitutional Dependencies
Dot Protocol depends upon governance objects defined elsewhere within the Dot Theory programme.
The present specification assumes the existence of these constitutional objects without redefining them.
The dependency structure is presently:
Constitutional Statement
│
▼
Twelve Principles
│
▼
Lexicon / Sublexicon
│
▼
Operational Admissibility Protocol (OAP)
│
▼
Dot Protocol
│
▼
Constitutional Onboarding Records (COR)
│
▼
Reference Repository
│
▼
Governed Knowledge Objects
Each layer constrains the layers below it.
Lower layers implement but do not redefine higher layers.
The protocol therefore remains constitutionally dependent upon the governance architecture while remaining computationally independent of any particular scientific framework.
12. Constitutional Objects
Dot Protocol assumes the existence of a number of constitutional governance objects.
The protocol does not define these objects.
It serialises them.
Examples presently include:
Framework
Primitive Commitment
Represented Object
Native Operator
Bridge Operator
Claim-State
Constitutional Placement
Admissibility Conditions
Residual
Accord
Successor State
Framework Admissibility History (FAH)
Provenance Record
Constitutional Onboarding Record (COR)
Additional governance objects may be introduced as the constitutional architecture evolves.
Dot Protocol remains intentionally extensible.
12.1 Serialization Principle
The protocol operates according to a simple constitutional principle.
Every governance object required for computational reasoning shall possess an explicit computational representation.
Objects that remain implicit cannot participate directly in deterministic computational operations.
Consequently, constitutional governance precedes computational interoperability.
12.2 Constitutional Independence
Governance objects remain constitutionally independent from their computational representation.
For example:
A Constitutional Onboarding Record is not created by Dot Protocol.
It is created through the Constitutional Onboarding process.
Dot Protocol merely specifies the computational state through which the resulting constitutional record becomes computationally recoverable.
Likewise:
the Operational Admissibility Protocol governs admissibility;
Dot Protocol represents admissibility computationally.
The distinction remains important.
Governance determines constitutional meaning.
Dot Protocol preserves constitutional meaning during computation.
12.3 Constitutional Extensibility
The constitutional architecture is expected to evolve.
New governance objects may therefore be introduced without requiring redesign of the protocol itself.
Provided that new governance objects declare:
identity;
constitutional role;
computational state;
admissibility conditions;
revision behaviour;
they may participate within Dot Protocol without altering existing protocol implementations.
The protocol is therefore extensible through constitutional governance rather than through changes to its computational foundations.
Constitutional Summary:
Dot Protocol does not attempt to become the constitutional architecture.
Nor does it replace scientific methodology.
Its role is considerably narrower.
It provides the computational representation through which constitutional governance becomes machine-readable, computationally recoverable and interoperable across independently developed scientific frameworks.
Part IV — Dot Protocol Specification
This part specifies the minimum explicit computational state required for a Governed Knowledge Object (GKO).
The protocol does not prescribe how this state is stored. Implementations may employ relational databases, document stores, graph databases, distributed ledgers, structured text, or other computational architectures.
The protocol specifies only what computational state must be explicitly represented.
13. Protocol Overview
Every Governed Knowledge Object consists of two components:
Representational Content
Constitutional State
Representational content contains the scientific, mathematical, logical or descriptive material communicated by the framework.
Constitutional state contains the governance information required to preserve the identity, provenance, admissibility, revision behaviour and interoperability of that representation.
Dot Protocol governs constitutional state.
It does not constrain representational content.
13.1 Protocol Lifecycle
Every Governed Knowledge Object progresses through a governed lifecycle.
Submission
│
▼
Constitutional Onboarding
│
▼
Constitutional Placement
│
▼
Operational Use
│
▼
Revision
│
▼
Successor State
│
▼
Archival History
Each transition records a successor state.
Previous constitutional states remain recoverable.
State diagram:
Representation
│
▼
Constitutional Onboarding
│
▼
Governed Knowledge Object
│
▼
Constitutional Operations
│
├── Recover
├── Register
├── Characterise
├── Compare
├── Bridge
├── Revise
├── Archive
│
▼
Successor State
14. Primitive State Variables
Every Governed Knowledge Object shall explicitly represent the following constitutional state variables.
Identity
Unique object identifier.
Framework identifier.
Author(s).
Version.
Submission date.
Repository location.
Constitutional Identity
Framework name.
Framework type.
Representational domain.
Governance layer(s).
Constitutional placement.
Primitive Commitments
Primitive commitments accepted without internal derivation.
Native Representational Objects
Objects declared native to the framework.
Native Operators
Operators acting internally upon native objects.
Bridge Operators
Operators explicitly relating the framework to external representations.
Each bridge shall declare:
source object;
target object;
transport operator;
admissibility conditions;
revision conditions.
Claim-State
Current constitutional claim-state.
Claims shall distinguish explicitly between, where applicable:
primitive commitments;
derived claims;
bridge claims;
hypotheses;
open questions;
rejected claims.
Admissibility Conditions
Conditions under which constitutional claims remain admitted.
Constitutional Placement
Current governance layer(s).
For example:
Registration
Characterisation
Comparison
Validation
Operational Interoperability
Additional governance layers may be introduced by constitutional governance.
Residual Localisation
Residuals arising during protocol operations shall be explicitly recorded.
Residual localisation shall include:
originating operation;
affected object;
constitutional layer;
propagation constraints.
Residuals shall remain local unless explicit propagation is declared.
Propagation Statements
Every constitutional transition shall declare:
what changes;
what remains unchanged;
where consequences propagate;
where propagation explicitly terminates.
Propagation shall never be inferred.
Revision History
Every constitutional revision shall preserve:
previous state;
revision rationale;
revision operator;
successor identifier.
Earlier constitutional states remain recoverable.
Provenance
Each Governed Knowledge Object shall preserve:
authorship;
contributor history;
review history;
repository history;
constitutional provenance.
Framework Admissibility History
Where applicable, the protocol shall preserve the complete Framework Admissibility History (FAH), recording the evolution of constitutional placement, claim-state and governance across successive framework revisions.
15. Governed Knowledge Objects
A Governed Knowledge Object is a representation whose constitutional state satisfies the minimum protocol requirements.
The protocol does not constrain scientific content.
It constrains only the explicit representation of constitutional state.
Governed Knowledge Objects therefore become computationally interoperable without requiring convergence of ontology, mathematical formalism or scientific ambition.
15.1 Reference Classes
Current examples include:
Constitutional Onboarding Records (COR)
Operational Admissibility Protocol specifications
Bridge governance specifications
Framework Admissibility Histories
Reference Repository entries
Constitutional governance records
Future classes may be introduced without modifying the protocol.
15.2 Protocol Invariants
Every Governed Knowledge Object shall satisfy the following invariants.
Identity Preservation
The constitutional identity of the represented framework shall remain recoverable.
Provenance Preservation
Every constitutional state shall possess an explicit provenance chain.
Revision Preservation
Revision produces successor states.
It does not overwrite constitutional history.
Explicit Governance
Governance shall never depend upon undeclared assumptions.
Recoverability
Earlier constitutional states shall remain computationally recoverable.
Constitutional Separation
Distinct constitutional objects shall possess distinct Governed Knowledge Objects.
Independent frameworks, audit programmes, governance programmes and protocol specifications shall therefore remain constitutionally distinct even where they share authors, collaborators, mathematical structures or representational vocabulary.
Layer Preservation
Computational operations shall preserve declared constitutional placement unless an explicit governance transition has occurred.
15.3 Protocol Completeness
A Governed Knowledge Object shall be considered protocol-complete when all constitutionally required state variables have been explicitly represented.
Protocol completeness does not imply scientific completeness.
It signifies only that the constitutional state required for computational governance has been made explicit.
Part V — Constitutional Lifecycle
This part specifies the lifecycle through which Governed Knowledge Objects are created, revised, compared, maintained and archived.
Every protocol operation acts upon explicit constitutional state.
No operation may introduce undeclared constitutional assumptions.
The lifecycle is intentionally independent of discipline, ontology and implementation architecture.
16. Representation Construction
Every Governed Knowledge Object begins as a representation.
Prior to protocol onboarding, the representation may exist in any form, including:
scientific papers;
mathematical specifications;
software repositories;
experimental records;
computational models;
datasets;
governance documents;
or other representational artefacts.
Dot Protocol does not constrain the construction of representations.
It governs only their constitutional representation.
16.1 Initial Constitutional State
Before onboarding, a representation possesses an implicit constitutional state.
This state may include undeclared:
assumptions;
operators;
revision conditions;
admissibility criteria;
provenance;
governance objects.
The purpose of onboarding is to transform this implicit constitutional state into explicit computational state.
17. Constitutional Onboarding
Constitutional Onboarding is the process through which a representation becomes a Governed Knowledge Object.
Onboarding identifies and explicitly represents the constitutional state required by the protocol.
Where implemented within Dot Theory, Constitutional Onboarding is presently performed through the Constitutional Onboarding Record (COR) mechanism.
Alternative onboarding implementations remain compatible with Dot Protocol provided that they satisfy the protocol requirements.
17.1 Objectives
Constitutional Onboarding seeks to recover:
constitutional identity;
primitive commitments;
represented objects;
native operators;
bridge operators;
claim-state;
constitutional placement;
admissibility conditions;
revision conditions;
provenance;
successor-state behaviour.
The onboarding process does not modify the represented framework.
It recovers it.
17.2 Author Review
Where possible, constitutional recovery should be reviewed by the framework author.
Author review serves to:
correct constitutional inaccuracies;
preserve constitutional identity;
distinguish repository observations from author declarations;
improve protocol recoverability.
Author review constitutes a governance refinement process rather than a protocol requirement.
The absence of author review does not invalidate a Governed Knowledge Object, provided its provenance remains explicit.
17.3 Repository Governance
Repository annotations remain constitutionally distinct from framework declarations.
Repository governance may include:
onboarding observations;
maturity assessments;
provenance notes;
constitutional placement comments;
protocol metadata.
Such annotations shall never be presented as framework declarations.
18. Constitutional Revision
Governed Knowledge Objects evolve through explicit constitutional revision.
Revision produces successor states.
Revision does not overwrite earlier constitutional states.
18.1 Revision Events
Revision may arise from:
framework development;
author corrections;
new governance objects;
experimental outcomes;
computational implementation;
protocol evolution;
repository refinement.
Each revision shall produce a successor state.
18.2 Revision Discipline
Revision shall preserve:
constitutional provenance;
revision rationale;
revision operator;
predecessor state;
successor state.
Revision history remains permanently recoverable.
19. Residual Localisation
Protocol operations may produce residuals.
Residuals represent unresolved constitutional differences arising during representational recovery, comparison or revision.
Residuals shall be explicitly localised.
19.1 Localisation Principle
Residuals remain local unless explicit propagation has been declared.
Negative outcomes affecting one constitutional object shall not automatically propagate to unrelated constitutional objects.
19.2 Types of Residual
Residuals may include:
incomplete recovery;
unresolved ambiguity;
competing constitutional interpretations;
failed bridge conditions;
failed comparison conditions;
unresolved implementation details.
The protocol records residuals.
It does not resolve them.
20. Constitutional Propagation
Every protocol operation shall explicitly declare its propagation behaviour.
Propagation determines how constitutional consequences affect other governed objects.
20.1 Propagation Statement
Each operation shall specify:
originating object;
affected object;
constitutional layer;
propagation scope;
termination conditions.
Propagation shall never be inferred implicitly.
20.2 Successor States
Every protocol operation terminates in a declared successor state.
Successor states preserve:
constitutional identity;
provenance;
revision history;
recoverability.
No operation concludes without producing an explicit successor state.
21. Archival Preservation
Governed Knowledge Objects shall remain computationally recoverable after active development has ceased.
Archived objects shall preserve:
complete constitutional state;
revision history;
provenance chain;
residual history;
successor relationships.
Archival does not imply obsolescence.
It preserves constitutional recoverability for future comparison, reinterpretation and computational reuse.
Constitutional Lifecycle Summary
The constitutional lifecycle transforms representations into governed computational objects without altering their scientific identity.
Throughout this lifecycle, Dot Protocol preserves:
identity;
provenance;
admissibility;
revision;
residual localisation;
successor-state continuity;
constitutional recoverability.
The lifecycle therefore provides a disciplined computational framework through which independently developed scientific representations may evolve while remaining interoperable and constitutionally explicit.
Part VI — Constitutional Operations
Dot Protocol defines a set of constitutional operations that act upon Governed Knowledge Objects.
These operations manipulate explicit constitutional state while preserving identity, provenance and recoverability.
Operations do not determine scientific truth.
They determine how constitutional state evolves under governed computational processes.
Every operation terminates in a declared successor state.
22. Recover
Purpose
Recover the constitutional architecture of an existing representation.
Recovery identifies explicit and implicit constitutional state and transforms it into protocol-compliant computational representation.
Recovery does not alter the represented framework.
It makes its constitutional state explicit.
Typical outputs include:
Constitutional Onboarding Records;
constitutional placement;
recovered governance objects;
Framework Admissibility Histories.
22.1 Recoverability Principle
Recovery seeks to minimise constitutional ambiguity while preserving the framework author's declared identity.
Where uncertainty remains, residuals shall be explicitly recorded.
23. Register
Purpose
Register a recovered constitutional object within a governed repository.
Registration establishes:
identity;
provenance;
version;
constitutional placement;
repository location.
Registration does not imply validation.
It records existence.
24. Characterise
Purpose
Characterise the constitutional architecture of a recovered object.
Characterisation may include:
primitive commitments;
represented objects;
operators;
governance structure;
admissibility conditions;
revision behaviour.
Characterisation remains descriptive.
It does not compare frameworks.
25. Compare
Purpose
Compare two or more Governed Knowledge Objects under explicitly declared comparison conditions.
Comparison operates only upon declared constitutional state.
Frameworks lacking sufficient constitutional state shall not be considered comparison-ready.
25.1 Comparison Preconditions
Comparison requires:
declared comparison object;
comparison operators;
comparison conditions;
admissible governance layer;
explicit null conditions.
Comparison shall never proceed through implicit assumptions.
25.2 Comparison Outcomes
Comparison may produce:
constitutional equivalence;
constitutional distinction;
constitutional incompatibility;
unresolved residuals.
Each outcome terminates in an explicit successor state.
26. Bridge
Purpose
Construct a governed representational bridge between independent frameworks.
Bridge operations preserve constitutional independence.
They do not merge frameworks.
Every bridge shall declare:
source object;
target object;
bridge operator;
admissibility conditions;
revision conditions;
propagation behaviour.
26.1 Bridge Failure
Bridge failure constitutes a local residual.
It does not invalidate either participating framework.
27. Validate
Purpose
Record the constitutional outcome of a validation process.
Validation is external to Dot Protocol.
The protocol records:
validation conditions;
validation outcomes;
propagation behaviour;
successor state.
Dot Protocol therefore represents validation.
It does not perform validation.
28. Revise
Purpose
Produce a successor constitutional state.
Revision preserves:
provenance;
predecessor state;
constitutional identity;
revision rationale.
Revision never overwrites constitutional history.
29. Localise
Purpose
Associate constitutional residuals with their originating governance object.
Localisation prevents unintended propagation of unresolved constitutional differences.
Residuals remain explicitly recoverable.
30. Propagate
Purpose
Determine how constitutional consequences affect dependent governance objects.
Propagation shall always be explicitly declared.
Propagation shall never be inferred.
30.1 Propagation Constraints
Every propagation statement shall declare:
originating object;
affected object;
affected governance layer;
termination conditions.
31. Archive
Purpose
Preserve constitutional history after active development concludes.
Archived Governed Knowledge Objects remain:
recoverable;
citable;
comparable;
computationally reusable.
Archival therefore preserves constitutional continuity rather than historical inactivity.
32. Constitutional Composition
Complex protocol operations may be constructed through combinations of primitive constitutional operations.
For example:
Recover
↓
Register
↓
Characterise
↓
Compare
↓
Bridge
↓
Revise
↓
Archive
Each intermediate state remains constitutionally explicit.
No operation bypasses constitutional governance.
33. Operational Invariants
Every constitutional operation shall preserve the following invariants.
Identity Preservation
The represented framework remains constitutionally identifiable.
Provenance Preservation
The provenance chain remains explicitly recoverable.
Constitutional Separation
Operations shall not merge independent constitutional objects unless an explicit governance object authorises such a transition.
Revision Preservation
Operations generate successor states rather than overwriting previous states.
Recoverability
Previous constitutional states remain computationally recoverable.
Layer Preservation
Operations shall not alter constitutional placement unless the governance transition has itself been explicitly declared.
Residual Localisation
Residuals remain local unless explicit propagation is declared.
Constitutional Operations Summary
The constitutional operations defined by Dot Protocol transform governed scientific representations through explicit computational processes while preserving constitutional identity.
Together they provide a computational vocabulary through which independently developed scientific frameworks may be recovered, characterised, compared, revised, archived and computationally processed without requiring convergence of ontology, mathematical formalism or scientific ambition.
Part VII — Reference Implementations
The purpose of a reference implementation is not to demonstrate the scientific correctness of a framework.
Its purpose is to demonstrate the operation of Dot Protocol.
Each implementation illustrates how constitutional state may be recovered, represented and maintained independently of scientific discipline, mathematical formalism or ontology.
The examples that follow should therefore be interpreted as demonstrations of protocol behaviour rather than endorsements of the represented frameworks.
34. Constitutional Onboarding Record (COR)
The Constitutional Onboarding Record constitutes the first reference implementation of Dot Protocol.
COR demonstrates how an independently developed framework may be transformed into a Governed Knowledge Object through constitutional recovery.
The onboarding process explicitly represents:
constitutional identity;
primitive commitments;
represented objects;
operators;
claim-state;
constitutional placement;
admissibility conditions;
revision conditions;
residual localisation;
propagation behaviour;
successor states;
provenance.
COR therefore illustrates the practical application of Dot Protocol to constitutional onboarding.
34.1 Author Review
The first author-reviewed Constitutional Onboarding Record demonstrated an additional property of the protocol.
Independent constitutional recovery followed by author review:
localised constitutional inaccuracies;
preserved framework identity;
improved protocol design;
maintained explicit provenance.
This demonstrated that protocol refinement itself may proceed through governed revision rather than silent modification.
35. Operational Admissibility Protocol (OAP)
The Operational Admissibility Protocol provides the governance mechanism through which admissibility conditions become explicit constitutional state.
Dot Protocol represents those governance objects computationally.
OAP therefore determines constitutional admissibility.
Dot Protocol determines computational representation.
The two remain intentionally independent.
36. Framework Admissibility Histories
Framework Admissibility Histories demonstrate the protocol's capacity to preserve constitutional evolution.
Rather than replacing previous framework states, successive constitutional revisions remain computationally recoverable.
The protocol therefore records:
historical claim-states;
governance evolution;
revision pathways;
constitutional successor states.
Framework evolution becomes explicitly recoverable rather than retrospectively reconstructed.
37. Reference Repository
The Reference Repository demonstrates protocol operation across independently developed scientific programmes.
Each repository entry represents a Governed Knowledge Object satisfying the constitutional requirements specified by Dot Protocol.
The repository therefore illustrates:
constitutional onboarding;
provenance preservation;
revision governance;
computational recoverability;
interoperability preparation.
The repository is not intended as a catalogue of scientific correctness.
It is a catalogue of governed constitutional representations.
38. Bridge Governance
Bridge specifications demonstrate the protocol's treatment of interoperability.
Independent frameworks retain their constitutional identity while participating in explicitly governed representational bridges.
Bridge specifications therefore illustrate:
bridge operators;
admissibility conditions;
propagation behaviour;
revision conditions;
residual localisation.
Bridge construction is distinguished from framework merger.
39. Emerging Computational Implementations
Although presently demonstrated through structured constitutional documents, Dot Protocol is implementation-independent.
Potential computational implementations include:
document-based repositories;
graph databases;
relational databases;
distributed knowledge systems;
version-controlled repositories;
semantic knowledge graphs;
AI-assisted governance systems;
autonomous constitutional auditing services.
The protocol specifies computational state rather than implementation technology.
40. Reference Implementation Principles
Reference implementations shall satisfy the following principles.
Constitutional Fidelity
The implementation shall preserve the represented framework's constitutional identity.
Provenance Preservation
Every implementation shall maintain explicit provenance.
Explicit Governance
Governance objects shall remain computationally explicit.
Recoverability
Constitutional state shall remain recoverable throughout the complete lifecycle.
Framework Independence
The implementation shall not require modification of the represented framework's scientific content.
Constitutional Separation
Independent frameworks remain constitutionally distinct.
Reference implementations demonstrate interoperability without constitutional convergence.
41. Observed Effects
Early reference implementations have demonstrated several recurring protocol behaviours.
These include:
increased constitutional explicitness;
localisation of hidden assumptions;
clearer separation between governance and scientific content;
improved provenance preservation;
reproducible constitutional recovery;
explicit distinction between registration, characterisation, comparison and validation;
improved interoperability preparation without requiring ontological agreement.
These observations remain descriptive rather than evidential.
Continued onboarding across independent frameworks will determine the generality of these effects.
Reference Implementation Summary
The reference implementations demonstrate that Dot Protocol may be applied to independently developed scientific frameworks without requiring modification of their underlying mathematics, ontology or scientific ambition.
The protocol therefore appears capable of supporting governed computational interoperability while preserving constitutional independence.
Future implementations will determine the broader applicability of the protocol across additional scientific domains.
Part VIII — Evaluation
The purpose of evaluating Dot Protocol is not to determine whether particular scientific frameworks are correct.
Rather, the purpose is to determine whether explicit computational representation of constitutional state improves the recoverability, governance and interoperability of independently developed scientific representations.
Accordingly, evaluation concerns protocol behaviour rather than scientific content.
42. Evaluation Criteria
Dot Protocol should be evaluated according to the following constitutional criteria.
Recoverability
Can independently developed reviewers recover substantially similar constitutional architectures from the same represented framework?
Recoverability may be assessed through independent constitutional onboarding exercises followed by comparison of recovered constitutional state.
Explicitness
Does the protocol reduce hidden assumptions by making constitutional state explicitly representable?
Evaluation concerns the explicitness of constitutional state rather than the scientific conclusions reached by participating frameworks.
Provenance Preservation
Does the protocol preserve authorship, revision history and constitutional identity throughout successive protocol operations?
Successful implementations should permit reconstruction of constitutional evolution without reliance upon undocumented assumptions.
Constitutional Separation
Does the protocol preserve the distinction between independent frameworks, audit programmes, governance programmes and bridge specifications?
Successful implementations should prevent unintended constitutional conflation.
Interoperability Preparation
Does explicit constitutional state improve the ability of independently developed frameworks to participate in governed comparison and bridge construction?
Interoperability does not require scientific agreement.
It requires explicit constitutional representation.
Computational Representation
Can constitutional governance objects be consistently represented as explicit computational state across multiple implementations?
Successful implementations should demonstrate implementation independence while preserving constitutional meaning.
Protocol Stability
Does the protocol evolve through explicit revision while preserving earlier constitutional states?
Protocol refinement should improve recoverability without compromising provenance.
43. Observed Effects
Early protocol deployments have exhibited several recurring observations.
These observations remain descriptive and should not yet be interpreted as general conclusions.
Current observations include:
increased constitutional explicitness;
localisation of previously hidden assumptions;
clearer separation between registration, characterisation, comparison and validation;
improved provenance preservation;
reproducible constitutional onboarding;
clearer distinction between governance and scientific content;
preservation of framework identity during interoperability preparation.
Continued deployment across additional scientific frameworks will determine the generality of these observations.
Part IX — Attempted Falsification
Dot Protocol is intended as a candidate computational specification.
Like any protocol, its continued development depends upon demonstrating practical utility rather than assuming it.
The following observations would count against the protocol and may require substantial revision or abandonment.
44. Falsification Conditions
Dot Protocol would require significant revision if one or more of the following were consistently observed.
Failure of Constitutional Recovery
Independent reviewers repeatedly recover substantially different constitutional architectures from the same framework without identifiable residuals explaining the divergence.
Unnecessary Computational State
Protocol variables consistently prove unnecessary for constitutional recoverability or computational interoperability.
Loss of Provenance
Protocol operations fail to preserve explicit constitutional provenance across revision or implementation.
Constitutional Conflation
The protocol repeatedly fails to distinguish independent constitutional objects, resulting in persistent ambiguity between frameworks, governance programmes or audit processes.
Failure of Computational Representation
Governance objects cannot be consistently represented as explicit computational state across independent implementations.
Failure of Interoperability
Explicit constitutional representation provides no measurable improvement in governed comparison, bridge construction or representational interoperability.
Protocol Instability
Successive revisions require continual redesign of the primitive computational state rather than incremental refinement.
45. Revision Policy
Failure of one implementation shall not automatically falsify the protocol.
Residuals shall first be localised to:
implementation;
onboarding;
governance object;
protocol specification;
or representational ambiguity.
Protocol revision shall proceed only after explicit localisation of constitutional residuals.
Conclusion
Dot Protocol v1.0 proposes a minimal computational state model for governed scientific representations.
Its objective is intentionally limited.
The protocol neither replaces scientific theories nor prescribes scientific reasoning. It specifies the explicit computational representation of constitutional state required for governed representations to remain recoverable, interoperable and revisable throughout their lifecycle.
Within the wider Dot Theory programme, constitutional governance determines what information must remain explicit. Dot Protocol specifies how that information becomes explicit computational state.
The protocol therefore serves as the computational implementation layer of Dot Theory.
Initial deployments—including Constitutional Onboarding Records, Framework Admissibility Histories and related governance objects—suggest that explicit constitutional representation may improve recoverability, provenance preservation and interoperability preparation across independently developed scientific frameworks.
Whether these observations generalise remains an open question.
Accordingly, this specification is presented as a candidate protocol rather than a completed standard.
Its future development should proceed through implementation, independent constitutional onboarding, protocol refinement and attempted falsification.
Scientific progress depends not only upon new observations and new mathematics, but also upon improvements in the representations through which scientific knowledge is constructed, communicated, governed and computationally maintained.
Protocol Status:
Candidate Specification
This specification is released for implementation,
critique,
independent reproduction,
constitutional onboarding,
and attempted falsification.
Appendix:
JSON/YAML Appendix
Framework:
Version:
PrimitiveCommitments:
RepresentedObjects:
Operators:
ClaimState:
Residuals:
RevisionHistory:
...
