iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Onturgy proposes making a software system’s hidden assumptions explicit, translating them into architectural constraints, and checking whether the system behaves accordingly under stress. Its central question is not just what a system does, but who can act, decide, refuse, remember, challenge a decision, or leave once the design is in use.
This is a proposed research program, not an established engineering standard. The available account is a DEV Community article by Seyed Alireza Alhosseini, posted October 4, 2026; the underlying paper and its empirical record have not been independently verified.
What does it mean for philosophy to ship code?
Software architecture allocates practical power. A design can determine which actions are possible, whose decisions take precedence, what information persists, and how difficult it is to switch to another service. Those choices express assumptions about people and institutions whether or not a team has written them down as principles.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Onturgy calls undeclared assumptions of this kind “Dark Ontology”: assumptions about what exists, what matters, what can be known, and who holds power that become operational through a system’s design. The program proposes comparing a system’s declared commitments with its behavior when users refuse, incentives conflict, or operating conditions degrade. The difference between the two is its “declared-operational gap.” These are concepts in the article’s framing, not independently validated measurements.
#1 Best Overall
The practical ambition is to make design commitments inspectable and revisable by the people affected by them. That is a useful lens for analyzing systems, but the available account does not establish that Onturgy’s proposed measures or tests have been empirically validated.
How the possibility graph describes a system
Onturgy models a system’s practical possibilities as a graph, written Gₜ = (V, E, c, a). The graph is meant to capture not just features, but the routes people can take through a system and the conditions attached to those routes.
| Symbol | What it represents |
|---|---|
| V | Available capabilities or states |
| E | Transitions between those capabilities or states |
| c(e) | The cost of a transition |
| a(e) | Who can traverse a transition |
A change to the system can then be described as ΔG = Gₜ₊₁ − Gₜ: the difference between the possibility graph before and after a construction or change. The proposal is to examine which states remain reachable within a given budget, whether different actors have different routes, whether transitions can be reversed, and which alternatives have disappeared.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Distinguishing the cost of leaving
The article separates exit cost into two parts. “NaturalLoss” is value inherent in a relationship or service that cannot simply be carried elsewhere. “ArchitecturalBarrier” is friction introduced by design, such as non-portable formats or deliberately difficult exit steps.
Rank #2
This distinction matters because a higher cost of leaving does not, on its own, show that a system is coercive. The proposed analysis asks what creates the cost and whether it reflects an inherent loss or a barrier imposed by architecture. The article offers this as a conceptual distinction, not a validated measurement protocol.
The six commitments the proposed kernel asks about
Onturgy’s kernel starts from the question: what must an architecture make explicit if people affected by it are to revise it? It organizes that inquiry around six dimensions:
| Dimension | Question for a system |
|---|---|
| Agency | Who can initiate, intervene, delegate, refuse, or override? |
| Value | Which criteria define or optimize a successful outcome? |
| Authority | Who has final decision power, and over which decisions? |
| Memory | What persists, what is forgotten, and who controls continuity? |
| Exit | Can participants leave without prohibitive architectural barriers? |
| Contestability | Can people challenge rules and decisions through a process capable of changing them? |
The article adds a capacity layer that asks about materiality—such as infrastructure ownership, blocking power, payment, and maintenance—and labor, including who performs hidden work. Its evaluation layer considers legitimacy and whether another version of the system can be reconstructed.
The framework is explicitly value-laden. The article describes its protection of exit and contestability as a “minimal constitutional-liberal floor,” not as a neutral foundation acceptable under every political or ethical outlook. That makes its values a subject for scrutiny, rather than a reason to treat its categories as universal.
Rank #3
How ONTacture would compare rival architectures
ONTacture is the article’s proposed workflow for turning a commitment into an architecture that can be challenged. The process is:
- Claim: state the commitment the system is meant to honor.
- Compile: translate the commitment into architectural constraints.
- Build rival architectures: create different implementations that embody competing commitments or interpretations.
- Stress: compare them under agreed interventions, such as refusal, conflicting incentives, or degraded conditions.
- Attribute failure: identify what kind of breakdown occurred.
- Assess the negative horizon: examine whether a persistent consequence survives attempts to remove it.
- Revise: name the commitment that would have to change if the consequence cannot be resolved.
- Rebuild: implement the revised commitment and test again.
The comparison is meant to be disciplined: rival designs should face the same interventions, and a reported failure should distinguish an implementation mistake from a problem with the commitment itself.
Six proposed failure classes
| Class | What failed |
|---|---|
| F1: Implementation | The system did not realize the intended encoding. |
| F2: Encoding | The encoding misrepresented the commitment. |
| F3: Parametric | A parameter that was not constitutive of the commitment was wrong. |
| F4: Auxiliary | An assumption used to operationalize the commitment was wrong. |
| F5: Exogenous | Environment, adoption, or incentives explain the outcome. |
| F6: Conceptual | The problem remains after the other explanations have been addressed. |
The “Negative Horizon Rule” is a proposed trigger for reconsideration, not a proof that a theory is false. It identifies a candidate for revision when a theory-faithful implementation produces a reproducible consequence across independent implementations, and that consequence cannot be removed within a pre-registered search budget without changing a constitutive commitment. Any conclusion is relative to that search budget.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Why Onturgy tracks the lineage of ideas, including AI assistance
The program treats a design’s intellectual lineage as a documented dependency graph: concepts and commitments connect to sources and artifacts, with records of whether an idea was adopted, adapted, or rejected. It proposes testing whether differences in documented lineage predict architectural differences beyond field, market, and resource constraints. The article presents this as a hypothesis to investigate, not a demonstrated result.
Rank #4
It also identifies four properties of AI systems that could affect lineage: responsiveness, breadth, weak provenance, and common cause, where many builders consult the same system. From these, it proposes risks such as provenance laundering, dependence, homogenization, and sycophancy. The available account does not report results showing that these risks have occurred at a particular rate.
Making AI involvement auditable
Onturgy proposes treating a system configuration as “AI-owned” when people face practical limits in doing any of four things: reconstructing the reasoning without AI, overriding an AI suggestion, leaving AI assistance while keeping the reasoning record, or attributing which commitments came from people and which came from AI.
A proposed lineage log could record whether a change originated with a human, was AI-suggested, or was co-developed; what role the AI played; what decision the human made; and whether the reasoning can be reconstructed without AI. These are proposed operational tests and record-keeping practices, not reported findings.
Recommended Free Tools
What a proposed Onturgy repository would contain
The article sketches a repository organized around the artifacts needed to trace a commitment through design and testing: a kernel, commitments, encodings, architectures, stress tests, audits, lineage records, results, forks, and a changelog.
A commitment record could capture its statement and status, rival commitments, encoding, audit, observable prediction, search budget, and origin. The proposal also names “generative depth”: how many encodings, architectures, and results change when a commitment changes. This is intended to describe the reach of a commitment across a body of work; the account does not establish it as a validated metric.
What would count against the program?
The article proposes ten conditions that could undermine Onturgy’s usefulness. They are tests the program should face, not results already established:
- Philosophically distinct commitments do not produce meaningful architectural differences.
- Graph footprints prove unreliable outside a narrow class of systems.
- Forked architectures usually become incomparable.
- Proponents routinely reject encodings as unfaithful.
- Independent teams regularly disagree about failure attribution.
- Ablation shows that kernel dimensions are redundant or insufficient.
- Independent auditors fail to agree.
- Lineage explains no variation beyond contextual constraints.
- Shared AI mentors do not reduce commitment diversity.
- Origin tags prove unreliable.
Taken together, these criteria make the proposal more than a vocabulary for discussing values: they describe ways its advocates could discover that its distinctions, records, or tests are not useful. Whether the program can meet those tests remains an open question.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What readers can reasonably conclude
Onturgy offers a way to ask how declared values become operating rules, whose options those rules expand or restrict, and whether a system can be challenged or left. Its distinctive move is to connect philosophical commitments to architectural constraints, rival implementations, stress tests, and documented lineage.
For now, it is best understood as a proposed method and set of concepts. The account available is a secondary article dated October 4, 2026; it does not verify the underlying paper’s publication status, full formal definitions, or empirical validation. Readers evaluating a real system can use the questions as an analysis framework without mistaking the framework itself for proof that a design is fair, revisable, or safe.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
