Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsOnturgy proposes treating software architecture as philosophy made operational: state the commitments a system embodies, translate them into design constraints, then test whether the system’s behavior matches those commitments under stress. It is a research program, not an established engineering standard. The available account is a DEV Community article by Seyed Alireza Alhosseini, posted October 4, 2026; it describes a proposal but does not establish that its measures or tests have been empirically validated.
What does it mean for philosophy to “ship” with code?
Software systems distribute practical power. Their design affects who can act, whose choices count, what information persists, who can challenge a decision, and how difficult it is to leave. Those effects can follow from defaults, permissions, data formats, incentives, or operational dependencies even when a team has never written down the values behind them.
As an Amazon Associate I earn from qualifying purchases.
Onturgy calls such unstated assumptions “Dark Ontology”: ontological, normative, epistemic, and political assumptions that a system puts into practice without declaring. Its proposal is to make those assumptions explicit and compare them with what the system actually does. The article presents this as a way to inspect architecture, not as independent proof that every design choice has a single philosophical meaning.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The key comparison is between declared commitments and operational behavior. A team might say users retain meaningful control, for example, then examine what happens when a user refuses a recommendation, disputes an outcome, or tries to move to another service. The discrepancy, if any, is a declared-operational gap. A system can have a coherent statement of values and still fail to enact it.
#1 Best Overall
How does Onturgy model what a system makes possible?
The proposal represents a system’s practical possibilities as a graph, Gₜ = (V, E, c, a). In this model, V is the set of available capabilities or states, E is the set of transitions between them, c(e) is the cost of a transition, and a(e) identifies who can traverse it. A change’s footprint is written ΔG = Gₜ₊₁ − Gₜ: a comparison of the possibility graph before and after the change.
This framing shifts the question from “What features were added?” to “Whose options changed, and at what cost?” An analysis could ask which states each actor can reach within a given budget, whether a transition can be reversed, which alternatives disappeared, and whether one group can do something another cannot. The article proposes these as questions for analysis; it does not provide a validated measurement protocol for answering them.
Separate the value of a relationship from barriers to leaving
Onturgy distinguishes two proposed sources of exit cost. “NaturalLoss” is value inherent in a relationship or service that may not transfer to an alternative. “ArchitecturalBarrier” is friction created by design, such as a non-portable format or an intentionally difficult exit path.
Rank #2
That distinction matters because a higher exit cost alone does not establish coercion. A person may lose something meaningful when leaving a service, but that is analytically different from a system making departure harder through avoidable barriers. The framework’s aim is to identify the source of the cost rather than treating every cost as equivalent.
What commitments should an architecture make explicit?
Onturgy’s proposed kernel asks six questions about how a system is governed and experienced. The article describes it as value-laden: protecting exit and contestability is a “minimal constitutional-liberal floor,” not a neutral starting point that all philosophies would necessarily accept.
| Dimension | Question for the architecture |
|---|---|
| Agency | Who can initiate, intervene, delegate, refuse, or override? |
| Value | What criteria determine or optimize outcomes? |
| Authority | Who has final decision power, and over what? |
| Memory | What persists, what is forgotten, and who controls continuity? |
| Exit | Can participants leave without prohibitive architectural barriers? |
| Contestability | Can a decision or rule be challenged through a process capable of changing it? |
The article adds two layers around these dimensions. A capacity layer considers materiality—such as infrastructure ownership, blocking power, payment, and maintenance—and labor, including who performs hidden work. An evaluation layer asks whether the system is legitimate and whether another version can be reconstructed.
Rank #3
How would teams turn commitments into tests?
The proposed ONTacture workflow is: Claim → Compile → Build rival architectures → Stress → Attribute failure → Assess negative horizon → Revise → Rebuild. Its central move is translation: a commitment should become an architectural constraint that can be inspected and tested, rather than remaining only a statement of intent.
Recommended Free Tools
- Claim: State a commitment clearly enough that someone could identify what would count as honoring or violating it.
- Compile: Translate the commitment into constraints and an observable prediction. This step is where teams must expose how they interpret the claim.
- Build rival architectures: Implement different ways of satisfying, prioritizing, or rejecting the commitment so the comparison is not limited to one favored design.
- Stress: Apply agreed interventions, including refusal, conflicts of incentive, and degraded conditions, and compare the architectures’ behavior.
- Attribute failure: Identify whether the failure arose in implementation, encoding, parameters, auxiliary assumptions, external conditions, or the underlying concept.
- Assess the negative horizon: Ask whether the consequence persists across independent implementations and within a declared search budget.
- Revise and rebuild: Name the commitment that changed, update the architecture, and test the revised version.
The framework’s six proposed failure classes help keep these explanations distinct:
| Class | Proposed explanation |
|---|---|
| F1: Implementation | The system did not realize the encoding. |
| F2: Encoding | The encoding misrepresented the commitment. |
| F3: Parametric | A parameter that is 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 are addressed. |
The “Negative Horizon Rule” is the proposed threshold for treating a persistent consequence as a reason to consider revising a theory. A candidate consequence would need to recur across independent, theory-faithful implementations and resist elimination within a pre-registered search budget unless a constitutive commitment changes. The result is relative to that search budget: it is a candidate for revision, not an absolute refutation.
Rank #4
Why track the lineage of ideas, including AI assistance?
Onturgy proposes recording a dependency graph of concepts, commitments, sources, and artifacts, with evidence of whether each idea was adopted, adapted, or rejected. It offers a testable hypothesis that documented differences in intellectual lineage may help predict architectural differences beyond field, market, and resource constraints. That is a proposed research question, not a reported finding.
The article identifies four characteristics of AI systems that may affect lineage: responsiveness, breadth, weak provenance, and common cause, where many builders consult the same system. It raises possible risks such as provenance laundering, dependence, homogenization, and sycophancy, but does not report empirical results establishing that these risks occur at a particular rate.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →One proposed operational test for an “AI-owned configuration” is whether people can reconstruct the reasoning without AI, override an AI suggestion, leave for another or no AI while keeping the reasoning record, and attribute which commitments came from the AI or a human. A lineage log could record a commitment’s origin as human, AI-suggested, or co-developed; the AI’s role; the human’s decision; and whether the reasoning can be reconstructed without AI. These are proposed checks, not validated measures of ownership.
What might a repository make inspectable?
The article sketches a repository organized around the work needed to compare commitments with system behavior. It proposes areas for the kernel, commitments, encodings, architectures, stress tests, audits, lineage, results, forks, and a changelog. A commitment record could include its statement and status, rival commitments, encoding, audit, observable prediction, search budget, and origin.
It also proposes “generative depth”: how many encodings, architectures, and results change when a commitment changes. The idea is to make the reach of a philosophical revision traceable through the artifacts it affects, rather than treating a change in principle as an isolated note.
What would count against Onturgy itself?
A research program needs failure conditions that could challenge its usefulness. The article proposes ten:
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 & 11- Philosophically distinct commitments do not produce meaningful architectural differences.
- Graph footprints prove unreliable outside a narrow class of systems.
- Forks are usually incomparable, making meaningful comparison impractical.
- Proponents routinely reject encodings as unfaithful to the commitments they were meant to represent.
- Independent teams regularly disagree about failure attribution.
- Ablation shows the kernel’s dimensions are redundant or insufficient.
- Independent auditors cannot agree on the assessments.
- Lineage explains no variance beyond contextual constraints.
- Shared AI mentors do not reduce commitment diversity.
- Origin tags prove unreliable.
These are proposed tests, not demonstrated shortcomings or results. They make the program more concrete by specifying what its proponents say could weaken its case.
What is established—and what remains open?
The available account supports a clear description of Onturgy’s proposal: make architectural commitments explicit, model changes in practical possibilities, compare rival implementations under stress, and document how ideas move into systems. It also outlines concepts, procedures, and potential failure criteria that could guide a research program.
It does not establish the formal publication status of the underlying paper, provide an independently checked empirical record, or show that the proposed metrics and tests have been validated. Readers should therefore treat Onturgy as a structured proposal for investigating architecture and values, not as a proven method with demonstrated predictive power.
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.
