papers/001 — Ontology of Derivable Architectures
Status: Research Draft
Version: 0.1
Abstract
This paper introduces the fundamental entities that constitute the proposed theory of Derivable Architectures.
The objective is not to define implementation procedures or mathematical operations.
Instead, the objective is to establish the ontology upon which subsequent formalization can be built.
All definitions are intended to be domain independent.
1. Motivation
The development of the Institutional Continuity Architecture (ICA) suggests that architectural derivation cannot be understood solely through the study of artifacts.
The derivation process appears to manipulate architectural structures that exist independently of their concrete realizations.
A formal theory therefore requires identifying the entities that exist prior to any derivation.
2. Primitive Entities
The following concepts are considered primitive.
They are intentionally left undefined in terms of one another.
Architecture
An Architecture is an abstract structural specification that defines:
- identity;
- admissible relationships;
- invariants;
- derivation constraints.
An architecture is independent of any particular realization.
Artifact
An Artifact is a concrete realization produced under an architecture.
Artifacts are observable.
Architectures are not.
Instance
An Instance is an artifact existing at a specific point in history.
Different instances may realize the same architecture.
Derivation
A Derivation is an operation that produces one artifact from another while preserving architectural identity according to a specified derivation profile.
Profile
A Profile specifies additional constraints applied during derivation without redefining the originating architecture.
Jurisdictional implementations constitute one example.
Operation
An Operation transforms one or more architectural entities.
Derivation is one class of operation.
Future research may identify others.
History
A History is the ordered sequence of operations affecting an architectural entity.
Identity
Architectural Identity denotes the properties preserved across valid derivations.
Its formal definition is deferred to Paper 002.
3. Ontological Levels
The proposed ontology distinguishes four levels.
Level 0
Architecture
Level 1
Profiles
Level 2
Artifacts
Level 3
Instances
Operations connect entities across levels.
History orders operations over time.
4. Observations
The ontology reflects the following observations obtained from the ICA.
O1.
Architectures remain stable while artifacts vary.
O2.
Profiles introduce implementation-specific information.
O3.
Artifacts may be regenerated.
O4.
Instances are historical rather than architectural objects.
5. Conjectures
The following conjectures motivate future work.
C1.
The proposed ontology is independent of application domain.
C2.
Every derivable architecture can be represented using only these primitive entities.
C3.
Additional concepts required by specific domains emerge as derived rather than primitive entities.
6. Open Questions
- Are the primitive entities independent?
- Can one primitive be eliminated?
- Are additional primitives necessary?
- Can identity be formally characterized without reference to artifacts?
7. Next Paper
Paper 002 investigates the concept of Architectural Identity.
Identity is expected to become the central invariant governing all valid derivations.