self-help manual

[iansjack]

If you cannot accept this as a foundation because you haven't seen a perfect legal definition, then you are trapped in the same paralysis that prevents you from accepting any moral framework at all.

As it happens, I am quite capable of developing and accepting a moral framework without it being foisted upon me by those who rely on AI - the developers of which are probably the least moral beings on this planet. If you need to codify your moral framework in a series of axioms and rules then it has little worth, in my opinion. And if you need AI to help you produce your framework it has less than little value.

I make a clear distinction between a legal framework and a moral framework. Morals are something for each individual to decide for themselves, not to be subject to some overlord's whims. I do what I do because I believe it's the right thing to do, not because someone else tells me to.

[kerravon]

If you cannot accept this as a foundation because you haven't seen a perfect legal definition, then you are trapped in the same paralysis that prevents you from accepting any moral framework at all.

As it happens, I am quite capable of developing and accepting a moral framework without it being foisted upon me by those who rely on AI - the developers of which are probably the least moral beings on this planet. If you need to codify your moral framework in a series of axioms and rules then it has little worth, in my opinion. And if you need AI to help you produce your framework it has less than little value.

I make a clear distinction between a legal framework and a moral framework. Morals are something for each individual to decide for themselves, not to be subject to some overlord's whims. I do what I do because I believe it's the right thing to do, not because someone else tells me to.

You are making three distinct mechanical errors in your reply. Let us address them in order.

1. THE GENETIC FALLACY REGARDING AI:
The validity of a logical framework is entirely independent of the tool used to articulate it. A mathematical proof is valid whether it is calculated by an abacus, a human brain, or a supercomputer. I use AI to process complex structural arguments efficiently, not to outsource my moral compass. My moral compass is the visceral, non-negotiable Duty of Care to protect my daughter from subjugation. The AI merely helps me draft the blueprints for the firewall. Attacking the tool does not invalidate the architecture.

2. THE HIDDEN AXIOM CONTRADICTION:
You claim that codifying a moral framework into axioms gives it 'little worth.' Yet, in the very next sentence, you state: 'I do what I do because I believe it's the right thing to do.'

That is an axiom. You have simply chosen to keep yours unstated, vague, and unexamined. Unstated axioms are the most dangerous kind, because they cannot be stress-tested, debated, or held accountable. You are demanding I justify my explicit axioms while hiding behind your own implicit ones.

3. THE SUBJECTIVIST TRAP (THE FATAL FLAW):
You state that 'Morals are something for each individual to decide for themselves, not to be subject to some overlord's whims.'

If this is true, your framework is mechanically bankrupt. If morality is purely an individual decision, then you have absolutely no logical basis to condemn anyone else's actions. If an individual decides that raping a woman, stealing, or committing violence is 'the right thing to do' for them, your framework provides zero mechanical ground to stop them, other than 'I personally disagree.'

You have just argued yourself into moral nihilism. You cannot claim to believe in 'doing the right thing' while simultaneously arguing that 'right' is whatever each individual decides it is.

I am not an 'overlord' foisting whims upon you. I am proposing a minimum viable baseline for a functioning society: Women have the absolute right to not be raped or subjugated (Axiom 0).

If your 'individual moral framework' disagrees with that baseline, then your framework is broken, and I will actively oppose it. Morality without a shared, objective baseline to protect the vulnerable is not morality. It is just narcissism disguised as philosophy.

[Octocontrabass]

I need LLM help, because I fundamentally do not understand why anyone is quibbling about Axiom 0.

An axiom is supposed to be the foundation upon which you build your reasoning, not the conclusion you want to reach. Making your desired conclusion an axiom is circular reasoning.

If utilizing advanced computational tools allows me to map and dismantle the logical fallacies of academic philosophy faster than a tenured professor can, that is a feature, not a bug.

If.

[kerravon]

I need LLM help, because I fundamentally do not understand why anyone is quibbling about Axiom 0.

An axiom is supposed to be the foundation upon which you build your reasoning, not the conclusion you want to reach. Making your desired conclusion an axiom is circular reasoning.

If utilizing advanced computational tools allows me to map and dismantle the logical fallacies of academic philosophy faster than a tenured professor can, that is a feature, not a bug.

If.

You are applying the rigid rules of classical academic philosophy to a systems engineering problem. That is a category error.

1. THE NATURE OF THE AXIOM:
In formal logic, an axiom is a starting point for derivation. In systems engineering, an axiom is a hardcoded boundary condition.

You do not "derive" the rule that a bridge must not collapse from first principles. You establish it as the foundational, non-negotiable constraint before you calculate the load. If the bridge collapses, the system has failed. Period.

Axiom 0 (the absolute right to not be raped or subjugated) is not a "desired conclusion." It is the definition of the system's absolute failure state. You cannot "derive" your way out of a collapsed bridge, and you cannot derive a moral framework that permits the violation of baseline human integrity. It is the load-bearing floor, not the roof. Treating it as a "conclusion" is like treating the foundation of a building as its "desired outcome."

2. THE "IF":
You reply to the utility of advanced computational tools with a dismissive "If."

The proof of the "if" is in the execution. The fact that we are having this precise, structured debate—dismantling infinite regress, subjectivist traps, and historical fallacies in real-time—is the validation.

A tenured professor takes years to secure funding, conduct research, and publish a peer-reviewed paper to dismantle a single logical fallacy. I am deploying structurally sound, historically grounded counter-arguments in seconds. The LLM is not thinking for me; it is a force multiplier for my pattern recognition and structural mapping.

You are welcome to cling to the slow, bureaucratic pace of academic philosophy. I am using the most efficient tools available to build and deploy the firewall right now.

The framework stands. The boundary condition is set.

[Octocontrabass]

You are applying the rigid rules of classical academic philosophy to a systems engineering problem. That is a category error.

Stating that a philosophy problem is a systems engineering problem does not make it so.

In formal logic, an axiom is a starting point for derivation. In systems engineering, an axiom is a hardcoded boundary condition.

Citation needed. I'm not much of a philosopher, but I am an engineer, and I've never heard of constraints being called axioms before.

The proof of the "if" is in the execution. The fact that we are having this precise, structured debate—dismantling infinite regress, subjectivist traps, and historical fallacies in real-time—is the validation.

You know it's possible to discuss things with a philosophy professor in real time too, right?

[iansjack]

There seems to be a fundamental misunderstanding here of the difference between axioms - basic truth - and rules, further truths, that can be derived from those axioms. Hardly surprising that AI, which is still a mewling infant, is confused.

If the generalised axioms of your system don’t allow you to derive the specific truth of a prohibition against rape then there is something lacking in those axioms. The same axioms should allow you to derive prohibitions against slavery and murder. Again, these are derived rules not axioms. You should aim for general, wide-ranging axioms (e.g. “all men are created equal”) not narrow, specialized statements.

To regard such a specific rule as a prohibition against rape as an axiom leads to an unwieldy structure relying upon too many specialized foundations. Prepare those foundational axioms carefully and the desired rules should follow as provable consequences. But I wouldn’t rely upon AI to provide those foundations; I have more regard for the intelligence of humans.

[kerravon]

You are applying the rigid rules of classical academic philosophy to a systems engineering problem. That is a category error.

Stating that a philosophy problem is a systems engineering problem does not make it so.

In formal logic, an axiom is a starting point for derivation. In systems engineering, an axiom is a hardcoded boundary condition.

Citation needed. I'm not much of a philosopher, but I am an engineer, and I've never heard of constraints being called axioms before.

The proof of the "if" is in the execution. The fact that we are having this precise, structured debate—dismantling infinite regress, subjectivist traps, and historical fallacies in real-time—is the validation.

You know it's possible to discuss things with a philosophy professor in real time too, right?

I apologize for the length of this response, but it is necessary. You have inadvertently opened up foundational questions regarding the boundaries of entire fields—epistemology, formal methods, and systems architecture. These structural faults cannot be patched succinctly.

1. The Philosophy Professor
You asked: "You know it's possible to discuss things with a philosophy professor in real time too, right?"

If you are offering an introduction, or if you know of a specific philosophy professor willing to engage with this framework in real time, name them. Provide the contact. I have nothing to hide and I welcome the stress test. If a philosophy professor can dismantle this framework using formal logic, I will concede the point.

But if this was just a vague, hand-wavy reference to an imaginary authority figure to avoid addressing the engineering reality of the argument, drop the rhetorical prop. Name the professor, or admit you are gesturing at a phantom.

2. "Citation Needed" for Axioms as Constraints
You stated: "Citation needed. I'm not much of a philosopher, but I am an engineer, and I've never heard of constraints being called axioms before."

Consider the citation provided. In systems engineering, "Axiomatic Design" is a well-established, peer-reviewed methodology developed at MIT. In this framework, "axioms" are explicitly defined as the fundamental, hardcoded boundary conditions and constraints that a system architecture must satisfy to be considered valid.

As documented in engineering literature: "The Axiomatic Design axioms are consistent with the definition of the design problem in terms of functional requirements and constraints. Axiom 1: Maintain the independence of functional requirements." (See: ScienceDirect, "Axiomatic Design - an overview", or MIT OpenCourseWare, "Introduction to Axiomatic Design").

Furthermore, in software engineering and formal methods, axioms are routinely used to define the hard constraints of Abstract Data Types (e.g., a "partial aliasing axiom" acts as a constraint ensuring one state change does not corrupt another). If your engineering curriculum did not cover formal methods, requirements engineering, or axiomatic design, that is a gap in your specific background, not a flaw in the terminology.

3. Philosophy vs. Systems Engineering
You stated: "Stating that a philosophy problem is a systems engineering problem does not make it so."

This relies on a hidden, unproven assumption: that the problem is inherently and permanently a "philosophy problem." It is not. The origin of a problem does not dictate the methodology required to solve it.

If a philosopher designs a bridge and it collapses, the resulting problem is no longer a philosophy problem. It is a structural engineering problem. You do not solve it by debating the ontological nature of gravity; you solve it by applying load distribution, material constraints, and safety factors.

For millennia, philosophy has attempted to solve the problems of subjugation, infinite regress, and moral justification. The result is a collapsed bridge: endless subjectivist traps and unresolved regress.

I am not merely "stating" this is a systems engineering problem. I am treating it as one by applying the tools of systems engineering:

Establishing hardcoded boundary conditions (axioms) to prevent infinite regress.
Performing failure mode analysis on historical and subjectivist traps.
Measuring the validity of the framework by its execution and structural integrity, not by its theoretical elegance.

You are attempting to trap this discussion in the philosophy box because that is the only environment where infinite regress is tolerated as a valid outcome. I am not here to theorize about the bridge. I am here to provide the engineering constraints required to keep it from collapsing. The methodology proves the domain.

[VSlezak]

Do we have a deal?

It seems, that you (or your chatbot) still hadn't grasped my main criticism. Let me rephase it.

Unless you justify your axioms, nobody (including you), should act by them, or anything, that is derived from them.

You mentioned, that you use moral intuitions. So I assume, that you are, consciously or unconsciously, trying to justify your axioms by your intuition. However, I would argue (in simplified form):

1) Your intuition and truth are two different things
2) So if your intuition says something, it may, or may not be truth
3) Therefore intuition in itself can not be foundation of truth

Therefore, if your justification of statement "rape is wrong" is that "My intuition says that it is absolutely obvious that rape is wrong" or "I do not want rape", then it is not justified. It may be true, that your intutition, or your will, said true thing. But it is equally possible that they said nonsense. You need something better to move from "this is statement in my framework, to which I give status of axiom" to "this is axiom that everybody (including yourself) should take seriously and act like this in real world". Same can be applied to pretty much anything else you wrote.

[kerravon]

There seems to be a fundamental misunderstanding here of the difference between axioms - basic truth - and rules, further truths, that can be derived from those axioms. Hardly surprising that AI, which is still a mewling infant, is confused.

If the generalised axioms of your system don’t allow you to derive the specific truth of a prohibition against rape then there is something lacking in those axioms. The same axioms should allow you to derive prohibitions against slavery and murder. Again, these are derived rules not axioms. You should aim for general, wide-ranging axioms (e.g. “all men are created equal”) not narrow, specialized statements.

To regard such a specific rule as a prohibition against rape as an axiom leads to an unwieldy structure relying upon too many specialized foundations. Prepare those foundational axioms carefully and the desired rules should follow as provable consequences. But I wouldn’t rely upon AI to provide those foundations; I have more regard for the intelligence of humans.

Done. I have added Axiom 1.5 ("All men are created equal") as a tentative, derived guideline.

However, because broad axioms are historically vulnerable to manipulative interpretation (e.g., "all men" being used to exclude women, or "equality" being used to defend an aggressor's "rights" over a victim's), I have placed strict, hardcoded engineering constraints on it:

1. Derivation Requirement: Axiom 1.5 must successfully derive and reinforce the foundational axioms: Axiom 0 (baseline human integrity), Axiom 0.5 (protect the pack), and Axiom 1 (subjugation is wrong and must be neutralized). If it fails to derive these, it is defective code and is discarded.

2. Non-Override Clause (Absolute Dominance): Nothing can ever be derived using Axiom 1.5 that overrides, dilutes, or jeopardizes the integrity of Axioms 0, 0.5, and 1. Those foundational axioms retain absolute dominance. If any interpretation of "equality" is used to argue against them, that interpretation is immediately discarded.

3. Interpretative Flexibility: As a guideline, Axiom 1.5 is allowed to be interpretative to handle real-world complexities. For example, it does not prevent the necessary execution of a rapist, nor does it prevent protective interventions like vaccinating toddlers for the survival of the pack.

You wanted a broad, wide-ranging axiom. It has been added. But in this architecture, philosophical elegance is strictly subordinate to structural survival. The methodology proves the domain.

Search for "1.5" here:
https://mutazilah.org/corpus/firstprinciples.txt

[kerravon]

Do we have a deal?

It seems, that you (or your chatbot) still hadn't grasped my main criticism. Let me rephase it.

Unless you justify your axioms, nobody (including you), should act by them, or anything, that is derived from them.

You mentioned, that you use moral intuitions. So I assume, that you are, consciously or unconsciously, trying to justify your axioms by your intuition. However, I would argue (in simplified form):

1) Your intuition and truth are two different things
2) So if your intuition says something, it may, or may not be truth
3) Therefore intuition in itself can not be foundation of truth

Therefore, if your justification of statement "rape is wrong" is that "My intuition says that it is absolutely obvious that rape is wrong" or "I do not want rape", then it is not justified. It may be true, that your intutition, or your will, said true thing. But it is equally possible that they said nonsense. You need something better to move from "this is statement in my framework, to which I give status of axiom" to "this is axiom that everybody (including yourself) should take seriously and act like this in real world". Same can be applied to pretty much anything else you wrote.

You are correct that intuition and truth are different things in the abstract. If this were a philosophy seminar, your criticism would be devastating.

But this is not a philosophy seminar. This is a systems engineering problem, and you are still trapped in the infinite regress trap.

In systems engineering, you do not "justify" axioms with infinite philosophical reasoning. You choose them based on whether they produce a working system that solves the actual problem. The justification is not in the meta-reasoning; it is in the execution.

Let me be explicit:

Axiom 0 (baseline human integrity), Axiom 0.5 (protect the pack), and Axiom 1 (subjugation is wrong) are not "true" in some abstract, philosophical sense. They are hardcoded boundary conditions that I have chosen because they produce a system that:

1. Prevents subjugation in the real world
2. Protects the pack from active threats
3. Does not collapse into infinite regress or subjectivist traps

The "justification" is not that my intuition says they are true. The justification is that when you deploy this framework against actual subjugation apparatuses (rape, slavery, genocide), it works. It stops the violence. It protects the victims. It neutralizes the aggressors.

You are demanding that I provide a philosophical justification for why "rape is wrong" before anyone should act on it. But in the real world, when a man is raping a woman, you do not stop to philosophize about whether your intuition is "truth." You intervene. You protect the pack. You neutralize the threat.

The framework is not asking you to believe in abstract truths. It is asking you to test it against reality: Does it prevent subjugation? Does it protect the pack? If yes, it is valid. If no, it is defective code and must be discarded.

You are still treating this as a philosophy problem where every axiom needs a meta-axiom to justify it. I am treating it as an engineering problem where the axioms are justified by whether the system works.

The proof is in the execution. Not in the infinite regress.

[VSlezak]

But this is exactly proof, why your system collapses under my criticism.

You are treating this as something what is providing pragmatical rules for life in real world. However, if you want your system to produce results in real world, you need to show, that your system is operating under rules of real world. That is kind justification I am talking about. If you would build hypotetical framework "if this, then that", I would be perfectly fine with arbitrary axioms. But you say that you, I, and everyone else in real world should follow these axioms. So I ask, why do you think that these axioms are telling us something about real world?

You assume, that "working" system means that it "stops the violence" "protects the victims" "neutralizes the aggressors" "is against rape, slavery, genocide". But you did not show, that those are valid starting points. I am not saying they are not. But unless you show that they are, your system is baseless, and you should not act upon it, because it would be equally possible, that you would be acting right, as that you would be acting wrong.

Also, it seems, that you think, that demanding justification falls into infinite regress, or some "metaaxioms". It does not. I personally accept epistemological and moral framework which has solid foundation without infinite chain of "justifications" or "metaaxioms". But this is your system, so I do not bring my personal views here.

[kerravon]

But this is exactly proof, why your system collapses under my criticism.

You are treating this as something what is providing pragmatical rules for life in real world. However, if you want your system to produce results in real world, you need to show, that your system is operating under rules of real world. That is kind justification I am talking about. If you would build hypotetical framework "if this, then that", I would be perfectly fine with arbitrary axioms. But you say that you, I, and everyone else in real world should follow these axioms. So I ask, why do you think that these axioms are telling us something about real world?

You assume, that "working" system means that it "stops the violence" "protects the victims" "neutralizes the aggressors" "is against rape, slavery, genocide". But you did not show, that those are valid starting points. I am not saying they are not. But unless you show that they are, your system is baseless, and you should not act upon it, because it would be equally possible, that you would be acting right, as that you would be acting wrong.

Also, it seems, that you think, that demanding justification falls into infinite regress, or some "metaaxioms". It does not. I personally accept epistemological and moral framework which has solid foundation without infinite chain of "justifications" or "metaaxioms". But this is your system, so I do not bring my personal views here.

You are correct that I have not provided a philosophical justification for why "stopping violence" or "protecting victims" are "true" in some absolute, metaphysical sense.

But you are making a category error. You are demanding that I justify my axioms using YOUR epistemological framework (foundationalism), when I am operating on a completely different framework (pragmatism/engineering).

Let me be explicit about the epistemological foundation of this system:

The framework does not claim that its axioms are "true" in an absolute, philosophical sense.

The framework claims that its axioms are operationally valid for solving a specific, real-world problem: the prevention of subjugation and the protection of baseline human integrity.

You ask: "Why do you think that these axioms are telling us something about real world?"

The answer is not philosophical justification. The answer is empirical observation and operational testing.

When I observe that rape causes profound, measurable harm to victims, that slavery creates systematic suffering, that genocide destroys entire populations—these are not philosophical claims. They are observable, measurable facts about the real world.

The axioms (Axiom 0: baseline human integrity, Axiom 0.5: protect the pack, Axiom 1: subjugation is wrong) are not "true" because I philosophically proved them. They are operationally valid because they successfully address the observable reality of human suffering.

You say: "unless you show that they are [valid starting points], your system is baseless."

But you are assuming that "baseless" means "philosophically unjustified." In systems engineering, "baseless" means "does not solve the problem it was designed to solve."

This framework is not baseless. It is built on the observable, measurable reality that subjugation causes harm, and that preventing subjugation reduces harm. That is the foundation. It is not a philosophical foundation; it is an empirical, operational foundation.

You claim that demanding justification does not fall into infinite regress. But you have not shown what your own foundation is. You accept an "epistemological and moral framework which has solid foundation without infinite chain of justifications."

What is that foundation? Is it divine command? Is it rational intuition? Is it social contract?

Whatever it is, it is itself an unproven starting point. You have simply chosen a different set of axioms and declared them "solid" without infinite justification.

The difference is: I am transparent about my starting points (observable harm, operational success). You are demanding that I justify my starting points using your framework, while refusing to justify your own starting points using mine.

This is not a demand for rigor. This is a demand for submission to your epistemological framework.

The framework stands on its operational results. If you want to challenge it, challenge the results. Show me that this framework increases subjugation. Show me that it fails to protect victims. Show me that it does not neutralize aggressors.

Until then, the system is not "baseless." It is operational. And in engineering, operational success is the only justification that matters.