An ontological framework for action, observation, and record.
This repository contains the canonical, versioned publication of The System: a human-designed ontological framework for representing observation and transmutation in environments where agency is external, observability is partial, and authority cannot be assumed.
The System is not software, a protocol, or a platform. It is a framework for thinking, modeling, and representing observation—applicable within and beyond digital tools.
This repository is a distribution and documentation vehicle for The System.
It provides:
- Authoritative written definitions of the ontology
- Architectural observations and constraints
- Versioned snapshots of conceptual state
- Licensing and contribution boundaries
The repository itself is not The System. It is one medium through which The System is published, revised, and referenced.
At its core, The System defines a minimal ontological structure built around two actions:
- Observe
- Transmute
It enforces a strict separation between:
- Action
- Observation
- Record
The System makes no assumptions about:
- Completeness of observation
- Accuracy of records
- Truthfulness of data
- Authority of actors
- Quality or meaning of transmuted artifacts
Any such semantics must be introduced deliberately by an operator (the Alchemist) through explicit Elements, Properties, Rules, or Extensions.
The System is not:
- A documentation guarantee
- A truth or validation mechanism
- A workflow or monitoring engine
- A governance or enforcement model
- A schema, database, or API
Implementations may add these properties, but they do so by choice, not by implication of the ontology.
This repository is organized to support clarity, versioning, and long-term evolution:
artifacts/ Version-specific or build-related artifacts (may be empty)
docs/ Authoritative documentation of the ontology and its rules
src/ Reserved for future reference implementations (may be empty)
LICENSE.md Project license (GPLv3)
VERSION.md Current version identifier and release-specific notes
README.md Gateway introduction (this document)
Not all directories are populated in every version. Empty directories are intentional and semantically meaningful.
./src/ is reserved for reference and example implementations. Any content here is optional and non-normative: it may be used to support experimentation or demonstration, but it is not required to use or understand The System, and it does not define the ontology.
If you are new to the project, the recommended reading order is:
-
docs/ABSTRACT.mdNarrative overview of intent, origin, and purpose. -
docs/ARCHITECTURE.mdFormal design observations and ontological constraints. -
docs/VERSIONING.mdHow versions are defined, interpreted, and released. -
docs/CONTRIBUTING.mdHow (and how not) to engage with the project. -
docs/RELEASING.mdThe release discipline governing published versions.
This project follows Semantic Versioning 2.0.0, with explicit lifecycle phases.
Early versions (Pre-Alpha) represent immutable conceptual snapshots, not incremental releases. Breaking changes are expected until architectural stabilization.
See docs/VERSIONING.md for authoritative rules.
This project is licensed under GPLv3.
In brief:
- You may implement the ontology freely, including in proprietary systems.
- Implementations are not derivative works unless they incorporate or modify this repository’s source material.
- Modifications or redistributions of the framework itself must remain GPLv3.
See LICENSE.md and docs/CONTRIBUTING.md for full context and intent.
This is not a high-velocity or code-centric project.
Most meaningful engagement is expected to occur through:
- Independent implementations
- Adapters and extensions published separately
- Conceptual exploration and critique
- Forks with divergent interpretations
Direct pull requests to this repository are expected to be rare and deliberate.
See docs/CONTRIBUTING.md before opening issues or proposing changes.
The System is designed to be used, adapted, extended, or ignored.
It does not require belief. It does not enforce compliance. It does not promise certainty.
This repository exists to make the framework legible, referencable, and versioned—not to constrain how it is applied.