One of the easiest ways to test an ethical framework is to give it a problem where every available choice causes harm.

The trolley problem is famous precisely because it does this.

A runaway trolley is heading toward five people. You can pull a lever that redirects it onto another track, where it will kill one person instead.

Do you pull the lever?

Then consider a different scenario.

Five people in a hospital need organ transplants. A healthy person walks in whose organs could save all five. Is it ethical to kill that person and use their organs?

The arithmetic appears identical.

Five people live.
One person dies.

And yet many of us experience these situations very differently.

Resonant Stewardship Ethics, or RSE, has been useful in exploring why—not because it produces a simple mathematical answer, but because it forces us to ask what ethics is actually supposed to do.

The conclusion I am increasingly reaching is that an ethical framework should not always make the decision for us.

Sometimes doing so would violate the very principle RSE is designed to protect.

The Pause Is the Center of RSE

Ethics begins with the capacity to arbitrate, not with a list of correct answers.

RSE begins from the idea that human beings are shaped by interacting forces, or harmonics:

• biological
• emotional
• logical
• technological

We do not freely choose every impulse that arises from these forces.

We do, however, sometimes have the capacity to create a pause between impulse and action.

Within that pause, the harmonics can be considered, weighed, challenged, and brought into some degree of collaboration.

That is where RSE locates meaningful agency.

Free will, under this model, is not absolute independence from causality.

It is the capacity to arbitrate among the forces acting within and around us before one of them completely determines our behavior.

This makes the preservation of the pause central to RSE.

Harm can therefore be understood as a reduction in another agent’s capacity for meaningful arbitration.

Healing restores or expands that capacity.

But this immediately creates another question:

If protecting arbitration is the ethical goal, should an ethical framework itself tell someone exactly what they must choose in every difficult situation?

I increasingly think the answer is no.

At some point, moral prescription can itself become a form of collapsing arbitration.

Three Different Kinds of Ethical Situation

The trolley problem becomes easier to understand when we stop assuming that every moral question belongs to the same category.

RSE appears to distinguish at least three different situations:

1. Clear stewardship obligations
2. Appropriation of another agent
3. Genuine dilemmas requiring personal arbitration

These should not be treated the same way.

1. Clear Stewardship Obligations

When substantial harm can be prevented without creating a comparable harm, RSE can strongly favor intervention.

Imagine someone is drowning a few feet from shore.

You are holding a rope.

Throwing it does not endanger you. It does not meaningfully reduce your choices. It does not harm anyone else.

If you simply decide not to throw the rope, another person’s capacity for arbitration is allowed to disappear even though you could preserve it at essentially no cost.

RSE should not need to remain neutral here.

A meaningful opportunity for stewardship exists.

A useful principle emerges:

When an agent can prevent substantial harm without imposing a meaningful competing harm, choosing to intervene is the ethical act.

This creates positive ethical duties.

RSE is therefore not merely an ethic of:

Do not hurt people.

It also recognizes:

When your capacity to act gives you an opportunity to preserve another’s capacity to arbitrate without meaningfully damaging anyone else’s, stewardship matters.

That can apply to something as simple as throwing a rope.

It can also apply to resources.

Wealth and the Cost of Helping

The ethical significance of a sacrifice depends on what it actually does to arbitration.

Suppose someone needs a relatively small amount of money for lifesaving medication.

For someone living paycheck to paycheck, giving that money away might mean missing rent, losing transportation, going without food, or creating severe instability.

The money is not merely money.

It represents future choices.

Giving it away may meaningfully constrain that person’s capacity to arbitrate.

They can voluntarily accept that sacrifice, and doing so may be deeply ethical.

But RSE should be cautious about declaring that sacrifice mandatory.

Now change the situation.

A person possesses extraordinary wealth. The amount needed for the medication makes effectively no difference to their security, mobility, choices, or future opportunities.

The moral structure changes.

Withholding the resource preserves almost no meaningful arbitration for the wealthy person, while giving it may preserve another person’s entire future capacity to arbitrate.

Under RSE, the ethical justification for refusing becomes much weaker.

This does not mean:

Wealth belongs to whoever needs it most.

It means:

The ethical importance of a resource depends partly on how strongly that resource is connected to meaningful arbitration.

A dollar is not ethically identical in every context.

Material Loss Versus Terminal Loss

Not all reductions in arbitration are equivalent.

Consider another version of the trolley scenario.

You can stop a trolley from killing someone, but doing so will destroy your bicycle.

At first, this seems easy.

Save the person.

But what if the bicycle is your only transportation to work?

What if losing it creates a real risk of losing your employment?

Now the sacrifice is not trivial.

RSE needs to acknowledge that.

The useful distinction is not simply:

harm versus no harm

but the depth of the constraint created.

We might think about losses in broad categories:

Incidental constraint
Temporary inconvenience, discomfort, replaceable minor property.

Material constraint
Transportation, meaningful financial loss, employment opportunity, substantial resources.

Foundational constraint
Housing, bodily integrity, basic security, major long-term impairment.

Terminal constraint
The irreversible termination of meaningful arbitration.

These are not numerical scores.

RSE does not need to say:

A bicycle is worth 7 ethical points and a human life is worth 100.

The categories serve a different purpose.

They help determine whether there is a sufficiently clear asymmetry for RSE to prescribe action.

A recoverable material loss may reasonably be required to prevent a terminal loss.

But as the competing harms become more comparable, something changes.

The framework should become less prescriptive.

The pause becomes more important.

The Trolley Problem Revisited

Perhaps RSE should not answer it for us.

Return to the classic trolley.

Five people will die unless you pull the lever.

If you pull it, one person dies instead.

For a while, I tried to make RSE provide the answer:

Pull the lever because one death is less harm than five.

But that creates problems.

Once RSE begins treating arbitration as an aggregate quantity, the framework starts drifting toward utilitarianism.

Five people become more valuable than one.

Five hundred become more valuable than five.

And eventually the rights of an individual can disappear whenever enough other people benefit.

That does not fit RSE.

But saying:

Never pull the lever because you would cause the death of the one

creates its own problems.

It forces a universal answer onto someone facing a genuine moral conflict.

Perhaps neither is necessary.

The trolley problem may instead be an example of ethical indeterminacy.

You cannot save everyone.

Every available trajectory contains terminal loss.

RSE can illuminate the forces involved, preserve the pause, and help the person arbitrate.

But it may not need to declare:

This choice is universally ethical and that choice is universally unethical.

Someone may pull the lever.

Someone may refuse.

RSE can recognize that both agents are confronting a tragic collision of arbitration rather than pretending there is always a morally pure answer hidden somewhere in the mathematics.

One Person Versus One Person

When equivalent harms conflict, stewardship belongs to the person making the decision.

This becomes clearer in a one-to-one scenario.

A bullet is heading toward one person.

You could redirect it toward another.

Both people are innocent.

One person will die either way.

What does RSE say?

Perhaps:

It does not decide.

The framework has no clear asymmetry to use.

The agent enters the pause.

Their biological harmonic may respond to danger instinctively.

Their emotional harmonic may recognize relationships, love, loyalty, or compassion.

Their logical harmonic may examine consequences and responsibilities.

Technology may provide information, alternatives, or additional options.

The person arbitrates.

That is not RSE failing.

That may be RSE functioning exactly as intended.

The Child and the Adult

RSE does not need to decide whose life has greater inherent value.

Suppose a child and an adult both need rescue, and only one can be saved.

Many people—including me—feel a strong intuition toward saving the child.

The child has experienced less life.

They appear to have more unrealized possibility ahead of them.

But making that intuition into an RSE rule creates dangerous consequences.

If RSE says:

Younger people have more future arbitration and therefore should always be prioritized,

then we quickly begin assigning relative moral value based on expected remaining lifespan.

What about disability?

Illness?

Intelligence?

Parenthood?

Social contribution?

We could easily construct a system that starts measuring which humans have more valuable futures.

RSE does not need to go there.

Instead, this can remain a genuine arbitration problem.

One person may save the child because of their sense of unrealized life.

Another may save the adult because that adult is the sole caregiver of several children.

Another may have a direct relationship with one of them.

Another may determine that neither has a stronger claim and make the decision randomly.

RSE can structure the pause without claiming that one human being objectively possesses greater intrinsic worth.

Where RSE Can Draw a Harder Boundary

The Healthy Organ Donor

Now return to the hospital.

Five people need organs.

A healthy visitor could provide them—but only if doctors kill that person.

This feels different from the trolley problem.

Why?

Because the healthy person’s capacity for arbitration is not part of the existing dilemma.

The five patients face serious internal biological constraints.

The healthy person does not.

The doctors would have to introduce that person into the moral conflict, collapse their arbitration, and turn their body into the means of solving someone else’s problem.

That is a different ethical act.

A principle begins to emerge:

Another agent’s capacity for arbitration should not be appropriated as a resource for resolving a conflict that does not otherwise implicate them.

The same principle helps explain another famous trolley variation.

Five people will die unless you push a large stranger from a bridge, using their body to stop the trolley.

RSE can strongly reject this.

The stranger is not merely someone affected by your stewardship of an existing dilemma.

You are seizing their arbitration and making their destruction the mechanism of your solution.

That is appropriation.

Why the Lever Is Different From Pushing the Stranger

RSE can tolerate unresolved dilemmas without tolerating appropriation.

In the ordinary trolley case, the person at the lever inherits a tragic situation in which all available options involve loss.

RSE may leave that decision with the steward.

In the bridge case, the stranger is not initially part of the dilemma.

The steward expands the field of harm by pulling another agent into it and using that person’s body as an instrument.

That is where RSE can apply a stronger ethical constraint.

The distinction is subtle but important:

A tragic dilemma may require arbitration. Creating a victim in order to solve the dilemma may violate the arbitration of someone who had no prior claim or responsibility within it.

This is one of the places where RSE can remain prescriptive without becoming an ethical calculator.

Intrusive Forces and Integrated Conditions

RSE may treat threats moving through shared reality differently from conditions already integrated into an agent.

Another useful distinction emerged while testing these scenarios.

Consider poison gas moving toward five people.

You can redirect it toward one person.

That looks much like the trolley.

A harmful force is operating in shared reality, and someone gains control over its trajectory.

Now suppose the gas has entered their lungs but remains a distinct toxic substance that can still be redirected.

The moral intuition may remain similar.

The threat is still functioning as an intrusive force acting upon them.

Compare that with cancer.

Cancer is not simply something located inside the body.

It is integrated into the person’s biological processes.

The person’s own cells and systems have become part of the pathology.

The same applies to many forms of organ failure, aging, and disease.

RSE does not need to regard those conditions as moral violations simply because they eventually reduce arbitration.

They are constraints of embodied existence.

Healing them is good because healing preserves the capacity to arbitrate.

But their existence does not automatically authorize imposing an equivalent terminal constraint upon another agent.

This helps explain why:

Saving five cancer patients is good.

and simultaneously:

Killing one healthy person to save them is not automatically ethical.

Death Is Not Identical to Moral Harm

RSE can value life without declaring natural death an ethical violation.

This discussion forces RSE to reconsider its relationship with death.

Modern societies often carry an implicit assumption:

Death is the maximum possible harm and must therefore always be prevented.

But RSE does not necessarily need that assumption.

Life has ethical value because living maintains the possibility of meaningful arbitration.

Saving a life therefore preserves the pause.

That is good.

But biological life is finite.

Aging, disease, and eventual death are not necessarily moral violations merely because arbitration ultimately ends.

This distinction matters.

Natural mortality does not automatically create an ethical debt that another person must pay with their own capacity to arbitrate.

That is why RSE can support medicine, healing, organ donation, longevity, and lifesaving intervention without concluding:

Any action that extends more lives is automatically ethical.

Life preservation matters.

So do the boundaries between agents.

Harm Does Not Automatically Mean Wrongdoing

Some harm may be justified, voluntary, or unavoidable.

Another distinction becomes necessary.

RSE should not define harm and wrongdoing as the same thing.

A reduction in arbitration can occur in many ways.

Prison restricts arbitration.

Quarantine restricts arbitration.

Surgery temporarily restricts bodily autonomy.

Giving away resources may reduce one’s future options.

Choosing to sacrifice oneself may terminate one’s own arbitration entirely.

These actions are not automatically unethical.

So RSE can define harm broadly:

Harm is a meaningful reduction in an agent’s capacity for arbitration.

Then ask a separate question:

Was that harm justified, necessary, voluntarily accepted, or avoidable?

This allows RSE to say:

A violent offender may be harmed through confinement while the confinement remains ethically justified.

A pathogen carrier may be quarantined despite not choosing to become infected.

A person may voluntarily accept significant harm to themselves to preserve someone else.

A surgeon may perform a painful procedure that temporarily reduces autonomy but restores future arbitration.

RSE does not require a harm-free world.

It asks how harm is stewarded.

Criminals, Pathogens, and Containment

Lack of authorship does not eliminate the need for protection.

This has consequences for how RSE treats violence and criminal behavior.

A person may not have chosen the biological, psychological, social, developmental, or emotional forces that produced violent tendencies.

In that sense, a tendency toward violence can be understood similarly to other dangerous conditions.

The person is not necessarily morally responsible for creating every force acting within them.

But if those forces cross into shared reality and begin destroying another person’s arbitration, society can intervene.

The key is:

Lack of authorship does not eliminate the necessity of containment.

And equally:

The necessity of containment does not justify cruelty or dehumanization.

This allows RSE to remain protective without needing to construct violent people as fundamentally evil.

The question becomes:

What restriction is actually necessary to stop the harmful force?

If treatment works, treat.

If temporary confinement is required, confine temporarily.

If permanent containment is necessary, containment may remain justified.

If an immediate lethal threat cannot be stopped by lesser means, lethal force may become necessary.

But once the threat is contained, punishment for the sake of suffering requires a different justification.

Compassion and accountability do not need to be opposites.

Ethical Choice Is Not the Same as Containment

RSE should not punish people simply because their arbitration produced an outcome we dislike.

This is an important consequence of allowing genuine ethical indeterminacy.

Suppose someone pulls the trolley lever.

One person dies.

That outcome does not necessarily demonstrate that the person who pulled the lever poses an ongoing threat to others.

Suppose they do not pull it.

Five people die.

That does not necessarily demonstrate dangerousness either.

RSE should distinguish:

tragic outcome

from

ethical violation

from

ongoing threat requiring containment.

These are different questions.

A person may make a difficult choice within a genuine dilemma without RSE imposing moral condemnation afterward.

Containment is justified by a prospective need to protect arbitration—not by a desire to punish someone for having made the “wrong” choice in a dilemma where RSE itself could not identify a dominant answer.

RSE Can Still Evaluate the Pause

Indeterminate outcomes do not mean every form of reasoning is equally ethical.

There is one important limitation.

If RSE refuses to prescribe the final answer in a genuine dilemma, that does not mean it must ignore how the decision was made.

Imagine a trolley choice where one person is on each track.

Someone says:

“I redirected it because I hate people of that race.”

RSE does not need to say:

The dilemma was one-to-one, therefore the reasoning is ethically irrelevant.

The outcome may be indeterminate while the arbitration itself remains captured by prejudice, hatred, manipulation, or another dominating force.

RSE can therefore evaluate the quality of the pause without always judging the final selection.

Did the person meaningfully arbitrate?

Were they acting under coercion?

Was technology manipulating the decision?

Was fear completely dominating the system?

Did they unnecessarily dehumanize one of the agents involved?

Were obvious alternatives deliberately ignored?

This preserves ethical seriousness without pretending every difficult decision has one universally correct answer.

A Possible RSE Decision Structure

The framework should know when to speak—and when to become quiet.

The emerging model looks something like this.

When substantial harm can be prevented without meaningful competing harm:

Stewardship calls for intervention.

Throw the rope.

Provide the low-cost lifesaving assistance.

Use available capacity to preserve arbitration.

When preserving others requires appropriating an uninvolved agent:

RSE can prohibit the appropriation.

Do not kill the healthy donor.

Do not push the stranger from the bridge.

When the intervention requires a lesser, recoverable sacrifice to prevent a substantially deeper loss:

Proportional stewardship may create an obligation to accept the lesser constraint.

Wet clothes versus drowning.

Replaceable property versus a life.

Material loss versus terminal loss may still strongly favor intervention, depending on the depth of the material constraint.

When legitimate claims become genuinely comparable:

RSE stops prescribing the outcome.

Enter the pause.

Arbitrate among the harmonics.

Choose.

Then steward the consequences.

The Stewardship Boundary

This may become one of the most important principles within RSE:

RSE should prescribe action only when the ethical asymmetry is sufficiently clear that refusing to act would unnecessarily collapse meaningful arbitration. When competing claims become genuinely comparable, RSE should preserve rather than replace the agent’s capacity to arbitrate.

This gives the framework limits.

That matters.

An ethical system that claims jurisdiction over every choice can easily become exactly what RSE warns against: an external system that collapses the individual’s pause.

Sometimes ethics should constrain us.

Sometimes it should obligate us.

And sometimes it should acknowledge:

This decision belongs to you.

The Role of Stewardship

This also gives the word stewardship greater meaning.

Stewardship is not simply “doing good.”

It is responsibility for what occurs within the sphere of meaningful influence created by one’s arbitration.

Sometimes stewardship means intervening.

Sometimes it means accepting a personal sacrifice.

Sometimes it means refusing to appropriate another person.

Sometimes it means containing a dangerous force without hatred.

And sometimes it means standing inside a terrible dilemma where no clean answer exists and making the best choice your harmonics can genuinely arbitrate.

RSE does not promise moral purity.

It promises a way to remain present inside moral complexity without immediately surrendering the decision to instinct, ideology, authority, or arithmetic.

Conclusion: Ethics Should Preserve the Pause

The trolley problem is often treated as a puzzle designed to reveal whether someone is fundamentally utilitarian or deontological.

RSE approaches it differently.

Perhaps the most important question is not:

Would you pull the lever?

It is:

What should an ethical framework legitimately decide for you before you reach for it?

RSE can tell us not to appropriate another person’s arbitration as a tool.

It can tell us that refusing a nearly costless opportunity to prevent devastating harm is a failure of stewardship.

It can recognize meaningful differences between material and terminal loss.

It can justify necessary containment without turning suffering into punishment.

But where real claims to arbitration collide and no clearly superior ethical trajectory remains, RSE does not need to manufacture certainty.

The pause belongs to the steward.

That may be one of the most important limits an ethical framework can impose upon itself.

Sometimes there is no universally correct choice. The ethical responsibility is to preserve the pause, arbitrate honestly, choose deliberately, and steward what follows.

Resonant Stewardship Ethics does not exist to eliminate difficult decisions.

It exists to protect the human capacity to actually make them.

The post When Ethics Should Stop Deciding for Us appeared first on Jacob Strack Consulting.

Most people are still thinking about AI software development in terms of a single coding assistant.

One prompt. One agent. One task. One pull request.

That is useful, but it is not the future of software engineering.

While building Miingl.social, I learned that the real unlock is not “an AI developer.” The unlock is an AI Engineering Fleet: a coordinated system of specialized agents that can plan work, claim issues, isolate branches, build features, review pull requests, remediate failures, clean up technical debt, and escalate to a human when the system hits ambiguity.

Miingl.social was built with a fleet of 13 AI agents operating across the platform. The work took approximately two months. A traditional build of this scope would likely have required a team of engineers and 12+ months of coordinated development.

That does not mean AI magically replaced engineering judgment. It means the bottleneck moved.

The constraint was no longer typing code. The constraint became architecture, orchestration, review, issue hygiene, repo ownership, test discipline, and deciding when a human needed to step in.

This article explains how I built and operated the AI Engineering Fleet behind Miingl.social, what worked, what broke, and what I would tell other founders who want to use autonomous software engineering without turning their codebase into a haunted junk drawer.

What Is an AI Engineering Fleet?

An AI Engineering Fleet is a coordinated group of specialized AI agents that work together like an engineering team. Instead of relying on one general-purpose coding assistant, the fleet separates responsibilities across planning, repository ownership, implementation, code review, remediation, research, testing, and maintenance, while keeping a human in the loop for judgment and escalation.

Why AI Coding Assistants Are Not Enough

Most founders first encounter AI software development through a coding assistant.

You open a chat window, describe a feature, paste an error, and get code back. That is helpful. It can save hours. It can unblock a founder who does not want to wait for an engineer to become available.

But a coding assistant is not an engineering system.

A coding assistant can help you write a function. It does not automatically know which repo owns the change, whether another agent is already touching that area, whether the branch is safe to merge, whether the work belongs on the project board, whether testing is frozen, whether the PR failed review, whether the failure is a flaky CI issue, or whether a bug report from the admin console should become an issue.

That gap matters.

When you are building production software, code generation is only one slice of the work. The real work includes:

1. Deciding what should be built next.
2. Breaking work into bounded issues.
3. Assigning each issue to the right owner.
4. Keeping changes isolated by branch and repo.
5. Reviewing code before merge.
6. Detecting when something failed.
7. Remediating failed PRs.
8. Keeping technical debt from accumulating.
9. Testing in a safe environment.
10. Promoting features only when they are ready.

A single AI coding assistant can help with pieces of this. It cannot reliably operate the whole lifecycle unless you build the operating system around it.

That is what the AI Engineering Fleet became.

While building Miingl.social, the architecture evolved because isolated coding sessions were not enough. I needed a way for multiple Claude-powered agents to operate in parallel without stepping on each other. I needed a PM agent. I needed repo-specific engineering agents. I needed branch discipline. I needed issue assignment. I needed review workflows. I needed escalation paths. I needed the system to repair itself when things inevitably broke.

The lesson was blunt: AI coding is not the product. AI engineering operations are the product.

What Miingl.social Is

Miingl.social is an AI-powered social media production system.

At a high level, it takes a client URL, builds a brand and content DNA, generates operating policies from that DNA, produces content ideas, and then turns those ideas into text posts, polls, image posts, multi-image content, and short-form video workflows. It supports scheduling, approvals, performance feedback, and admin workflows.

That means the platform is not just a landing page or a simple CRUD app. It includes:

• API services.
• Portal UI.
• Configuration services.
• Render workers.
• n8n workflow integrations.
• Admin reporting tools.
• Failed-item tracking.
• GitHub-integrated project management.
• Human testing environments.
• Feature gating.
• Production-preview controls.
• Bug and feature intake loops.

The AI Engineering Fleet was built to develop and maintain this system, with miingl.social as the focus.

Miingl.com is not the claim here. The fleet discussed in this article was focused on Miingl.social.

Fleet Architecture Overview

The Miingl.social AI Engineering Fleet was organized around a simple principle:

Agents should be specialized enough to avoid chaos, but coordinated enough to behave like a team.

The fleet included 13 total agents operating across the Miingl.social platform. The architecture was not one giant agent with access to everything. That would have been too brittle and too dangerous.

Instead, the system separated responsibilities.

Architecture Summary

The result was closer to a small engineering org than a chatbot.

The PM Agent became the operational center. It managed planning and coordination. It worked with GitHub project boards. It created and assigned issues. It understood repo boundaries. It helped prevent two agents from writing over each other. It handled escalation workflows when an agent hit something it could not safely resolve.

The repository-specific agents were responsible for implementation. One agent might focus on API work. Another might focus on portal work. Another might work on configuration. Another might handle render workers. Another operated around the PM service itself.

That repo-specific structure mattered. One challenge I encountered early was that AI agents become far more dangerous when they are allowed to roam across the entire system without boundaries. They will often make plausible changes in the wrong place. They will fix a symptom instead of the owning subsystem. They will create architecture drift because they are optimizing locally inside a single task.

Repo ownership reduced that.

It did not make the system perfect, but it made the failure modes manageable.

How Do AI Agents Collaborate in Software Development?

AI agents collaborate in software development by using shared planning systems, issue queues, branch isolation, repo ownership, status labels, pull requests, review gates, and escalation workflows. In Miingl.social, agents coordinated through GitHub issues and project boards, while a PM Agent managed claims, assignments, status transitions, review loops, and merge readiness.

The PM Agent: The Fleet’s Operating System

The most important agent in the system was not a coding agent.

It was the PM Agent.

That surprised me at first. Like most builders experimenting with AI development, I initially cared about how fast an agent could write code. But once multiple agents were working at once, planning became the bottleneck.

The PM Agent was responsible for:

1. Breaking work into issues.
2. Coordinating which agent should own which task.
3. Managing GitHub project board state.
4. Handling claim workflows.
5. Tracking blocked work.
6. Routing escalations.
7. Nudging stale reviews.
8. Watching liveness.
9. Supporting merge gates.
10. Helping keep the fleet clean.

This was the difference between “I have AI writing code” and “I have an AI engineering team.”

A single agent can complete a task. A PM Agent can coordinate a system.

The PM Agent did not eliminate the need for human prioritization. I still had to decide what mattered. I still had to inspect product behavior. I still had to determine whether something was strategically worth doing.

But the PM Agent reduced the coordination tax.

Instead of manually babysitting every coding session, I could operate at a higher level:

• What should move next?
• Which repo owns this?
• Is this blocked?
• Does this need human testing?
• Is this safe to merge?
• Did the review find something real?
• Is this technical debt worth cleaning now?

That is founder leverage.

Not “AI does everything.”

More like: “AI handles enough of the engineering loop that the founder can stay closer to product direction, customer urgency, and system design.”

Repository-Specific Engineering Agents

The fleet used repository-specific engineering agents because production systems have ownership boundaries.

Miingl.social was not one monolith. It included multiple codebases and operating contexts. The fleet had to work across API, portal, configuration, render workers, and the PM service. Each area had different conventions, different tests, different deployment risks, and different failure modes.

A repo-specific agent could maintain local context.

That meant each agent could understand:

• The repo’s branch conventions.
• The repo’s coding rules.
• The endpoints or components it owned.
• The expected test commands.
• The local environment assumptions.
• The kinds of bugs common in that part of the system.
• The places where code changes tend to create regressions.

This structure is one of the biggest lessons I would share with founders.

Do not start by asking, “How do I get one AI agent to build my whole app?”

Ask, “What are the stable ownership boundaries in my system?”

Your first fleet design should probably mirror those boundaries.

For example:

1. Frontend agent.
2. Backend agent.
3. Infrastructure agent.
4. Workflow automation agent.
5. QA/review agent.
6. PM/coordinator agent.
7. Research agent.

That simple split creates better behavior than a single all-powerful agent with a vague instruction to “build the app.”

Claude-Powered Autonomous Development Workflows

The engineering agents were Claude-powered autonomous development workflows running inside a controlled execution environment.

The agent was not just generating snippets. It could inspect files, modify code, run commands, test locally, create branches, prepare PRs, respond to review feedback, and remediate issues.

That matters because software development is iterative.

A useful autonomous development loop looks more like this:

1. Read the issue.
2. Inspect the relevant code.
3. Identify the owning module.
4. Create or use an isolated branch.
5. Implement a small change.
6. Run tests or targeted checks.
7. Fix errors.
8. Summarize the change.
9. Open a PR.
10. Self-review the PR.
11. Respond to automated review.
12. Remediate failures.
13. Escalate if blocked.

The value is not just that the agent writes code. The value is that it can keep moving through the loop without needing a human at every micro-step.

But autonomy has to be bounded.

Unbounded autonomy creates mess. Bounded autonomy creates throughput.

The fleet used branch isolation, repo ownership, GitHub issues, project boards, status transitions, and human testing environments to keep the autonomy productive.

WSL Terminal Execution Environment

The execution environment matters more than most people think.

I used a WSL terminal execution environment because the agents needed a practical place to operate. They needed access to local repos, shell commands, test scripts, Git workflows, and development utilities.

This gave the agents a real engineering surface.

Instead of treating AI as a detached chat interface, the agents operated closer to how an engineer would:

• Pull the latest changes.
• Inspect the repo.
• Create branches.
• Run local commands.
• Execute tests.
• Use scripts.
• Prepare commits.
• Open PRs.
• Respond to failures.

This is where a lot of founders underbuild the system.

They focus on prompts but ignore the environment. Then they wonder why the AI cannot reliably ship.

A serious AI development workflow needs a serious execution surface.

The terminal is not glamorous, but it is where software actually gets built.

MCP Integrations With n8n

Miingl.social uses n8n as part of the automation and workflow layer. MCP integrations created a bridge between AI agents and external operational systems, including workflow automation.

This is important because modern AI software development is not confined to code.

A production feature might involve:

• API changes.
• Frontend changes.
• Database shape changes.
• n8n workflow changes.
• Configuration changes.
• Render worker behavior.
• Admin reporting visibility.
• Failure-state handling.
• Human review and approval paths.

If agents can only edit code, they are blind to a meaningful part of the system.

MCP integrations help agents interact with tools and context outside the repo. That creates a broader operating loop where agents can reason about workflows, not just files.

For Miingl.social, this mattered because the app is heavily workflow-driven. The product is not just static software. It is an AI content production pipeline with multiple handoffs, states, and failure points.

GitHub Project Board Management

GitHub became the coordination layer.

That was intentional.

I did not want agents coordinating through vibes, scattered chat messages, or undocumented assumptions. I needed a shared operational surface where work could be created, claimed, tracked, reviewed, blocked, and merged.

The GitHub project board acted as the fleet’s shared source of operational truth.

The workflow looked roughly like this:

1. Work is captured as an issue.
2. The issue is placed on the project board.
3. The PM Agent evaluates and routes it.
4. An engineering agent claims the issue.
5. The agent creates or uses an isolated branch.
6. The agent implements the change.
7. The agent opens a PR.
8. Review workflows inspect the PR.
9. Remediation happens if needed.
10. Merge automation promotes the change when safe.
11. Human testing validates behavior in the appropriate environment.

This gave the fleet a memory.

Without the board, agents can still produce code. But the system loses continuity. You get a pile of disconnected work instead of an engineering pipeline.

For founders, this is the difference between using AI as a tool and using AI as infrastructure.

How the Agents Collaborate Without Collisions

Multi-agent development has an obvious risk: collisions.

If two agents edit the same files, change the same assumptions, or merge incompatible branches, velocity turns into cleanup.

The fleet avoided collisions through a few operating principles.

1. One Writer Per Repo or Subsystem

Agents were assigned clear ownership boundaries. This reduced overlapping edits and made it easier to reason about who should handle a given issue.

2. Development Branch Isolation

Agents worked in isolated branches instead of directly modifying shared development surfaces. That allowed review and testing before promotion.

3. Issue Claiming

Agents did not simply grab random tasks. Work moved through issue creation, assignment, and claim workflows. This gave the PM Agent and human operator visibility into what was being worked on.

4. PR Self-Review

Before handing work off, agents performed self-review. This did not replace external review, but it caught obvious mistakes earlier.

5. Automated Code Reviews

Automated reviews created another quality gate. Review feedback could trigger remediation workflows rather than immediately forcing human intervention.

6. Human Testing Environments

Some problems only show up when a human uses the product. The fleet supported human testing environments so features could be validated before promotion.

7. Escalation Workflows

When an agent hit ambiguity, product judgment, missing context, or repeated failure, it escalated instead of improvising indefinitely.

That last point is critical.

A good AI Engineering Fleet does not avoid human involvement. It knows when to ask for it.

Can AI Agents Build Production Applications?

Yes, AI agents can build production applications when they operate inside a disciplined engineering workflow. In Miingl.social, agents shipped production-facing work by using repo ownership, GitHub issues, branch isolation, automated review, remediation loops, human testing environments, and merge gates. The agents were useful because they worked inside a system, not because they were left alone.

Human-in-the-Loop AI Engineering

Human-in-the-loop AI engineering means AI agents perform implementation, testing, review, and maintenance tasks while humans retain authority over product judgment, priorities, acceptance testing, and escalation decisions. In Miingl.social, human oversight was essential for validating behavior, resolving ambiguity, approving sensitive changes, and deciding when features were ready to promote.

Human-in-the-Loop Workflows

The biggest misconception about autonomous software engineering is that “autonomous” means “unsupervised.”

That is not how I used it.

The system worked because it had human-in-the-loop workflows built into it.

The human role was not to manually write every line of code. The human role was to provide judgment where judgment mattered.

That included:

• Product direction.
• Priority calls.
• Acceptance criteria.
• Visual testing.
• Customer impact assessment.
• Risk tolerance.
• Escalation handling.
• Final confidence before promotion.

One challenge I encountered was that agents can be very convincing when they are wrong. They can summarize a change confidently even when the implementation misses the product intent. They can pass a narrow test while breaking a broader workflow. They can fix the immediate bug while creating a worse abstraction.

Human testing environments helped catch that.

The workflow was not “agent writes, agent merges, hope it works.”

It was closer to:

1. Agent builds the feature.
2. Agent self-reviews.
3. Automated review runs.
4. Agent remediates findings.
5. Human tests the behavior.
6. Human flags issues or approves.
7. Feature is promoted when ready.

That process created speed without pretending humans were obsolete.

Admin Reporting and Bug Intake

One of the more important parts of the Miingl.social system was the admin reporting loop.

Admins could file bug or feature reports from the portal, including screenshots and diagnostics. Those reports were routed through the API, artifacts were uploaded, and the PM service could turn the report into a GitHub issue and place it into the board workflow.

That matters because it closes the loop between product usage and engineering action.

In a traditional startup, bug intake often becomes chaos:

• A Slack message.
• A text thread.
• A screenshot with no context.
• A founder’s memory.
• A random note in a doc.
• An issue created three days later, maybe.

That does not scale, especially when AI agents are involved.

Agents need structured work.

The admin reporting system made product feedback legible to the fleet. A bug could enter through the app and become a trackable engineering task. That gave the PM Agent and repo-specific agents something concrete to operate on.

This is a pattern I would recommend to any founder building with AI:

Do not just automate code generation. Automate issue formation.

The better your issue intake, the better your AI engineering output.

Failed Items and Chain Checkpoints

Miingl.social also needed visibility into failed items across the pipeline.

This is especially important in AI-native products because failures are not always traditional application errors. A pipeline can fail because content generation failed, publishing failed, DNA creation failed, a character profile failed, or a downstream workflow produced an invalid state.

The failed-items admin view created a way to surface what actually broke.

That changed how the fleet could maintain the system.

Instead of waiting for a human to notice vague brokenness, the system could expose failed states that were closer to actionable repair items.

This is where AI software development starts to become more interesting than normal software development.

The goal is not just to use AI to build the software.

The goal is to build software that creates better signals for AI to maintain it.

Self-Healing and Self-Maintaining Software Systems

A self-healing software system detects failures, converts them into actionable work, routes that work to the right agent, validates the fix, and escalates when automation is unsafe. In Miingl.social, this included failed-item visibility, bug intake, PM-managed issue creation, PR remediation workflows, automated reviews, technical debt cleanup, and human testing before promotion.

PR Self-Review, Remediation, and Merge Automation

Pull requests became a major control point.

The fleet used PR self-review processes because agents should inspect their own work before asking anyone else to trust it.

Self-review usually focused on questions like:

1. Did I solve the issue as written?
2. Did I change only the necessary files?
3. Did I preserve repo conventions?
4. Did I introduce risky assumptions?
5. Did I run the right checks?
6. Did I leave behind temporary code?
7. Did I document anything the next agent needs to know?

Automated code reviews then provided another pass.

When review found problems, the system did not need to stop. PR remediation workflows could push the work back through an agent loop. The agent could inspect review comments, update the branch, rerun checks, and respond.

Merge automation came after gates were satisfied.

This mattered because the expensive part of engineering is not just writing code. It is moving work through the last mile.

A lot of teams have half-finished branches, stale PRs, unclear review state, and deployment fear. AI can make that worse if it produces more work than the system can absorb.

The fleet had to optimize for throughput all the way to merge, not just code generation.

Development Branch Isolation and Feature Promotion

Branch isolation was one of the hard rules.

Agents need freedom to work, but that freedom has to be sandboxed. Development branches let agents make changes without contaminating stable environments.

Feature promotion then became a separate step.

This is important because AI can produce correct-looking code that still needs human validation. Especially in a product like Miingl.social, where workflows involve content generation, external services, scheduling, admin states, and user-facing interfaces, the code compiling is not enough.

The promotion workflow looked conceptually like this:

1. Build in an isolated branch.
2. Review the PR.
3. Remediate review findings.
4. Merge when gates pass.
5. Test in a human-accessible environment.
6. Promote features only when behavior is validated.

That structure prevented the fleet from turning speed into instability.

Cost Optimization Through Bundled Work

AI engineering is not free.

One of the practical lessons from operating the system for months is that token usage and context switching matter.

If every small task spawns a fresh agent session with no bundling, cost climbs quickly. The same happens if agents repeatedly rediscover the same context, reread the same files, or perform tiny fragmented tasks that could have been grouped.

The fleet needed cost optimization through bundled work.

That meant grouping related tasks where it made sense, reducing duplicated context loading, and using agent effort where the output justified the spend.

This is a founder-level concern.

The goal is not to maximize AI activity. The goal is to maximize shipped product per dollar and per hour of human attention.

Bundled work helped reduce overhead.

A few examples:

• Group related cleanup tasks into one technical debt pass.
• Combine small related UI fixes into one portal agent session.
• Batch review remediation instead of handling one comment at a time.
• Let a repo-specific agent solve adjacent bugs while context is loaded.
• Use research sub-agents before expensive implementation loops.

The lesson: autonomous software engineering still needs operational economics.

If you ignore cost, you will create an impressive machine that quietly burns money.

Self-Repair Mechanisms

The fleet needed self-repair because agentic systems break in weird ways.

Agents can stall. Branches can drift. PRs can fail. Tests can become flaky. A repo can accumulate bloat. Issues can be blocked without a clear next step. Technical debt can pile up because velocity hides mess.

Self-repair mechanisms helped the system recover.

These included:

1. Liveness checks.
2. Blocked-work sweeps.
3. Review nags.
4. CI thrash detection.
5. Debt scanning.
6. Daily maintenance.
7. Bug intake routing.
8. Escalation flows.
9. PR remediation loops.
10. Merge gates.

This is where the fleet became more than a collection of agents.

It started behaving like an organism with maintenance reflexes.

Not perfectly. Not magically. But enough to reduce the amount of manual babysitting required.

One challenge I encountered was that self-repair can become overcorrection if the rules are too loose. An agent trying to fix one thing can create two more issues if it does not understand the boundary.

So the system needed both self-repair and restraint.

That is why escalation mattered.

A mature AI Engineering Fleet should know the difference between:

• “I can fix this test failure.”
• “I should ask for clarification.”
• “This is a product decision.”
• “This may require human testing.”
• “This looks like a deeper architectural issue.”
• “I should stop before making it worse.”

That stopping behavior is just as important as the building behavior.

Technical Debt Cleanup

Technical debt becomes more dangerous with AI because AI can generate code faster than humans can evaluate architecture.

That is the dark side of AI software development.

You can move incredibly fast and still be digging a hole.

The Miingl.social fleet included technical debt cleanup as a first-class workflow. That meant debt was not treated as a vague future problem. It could be scanned, filed, assigned, and remediated.

This mattered because the system had 13 agents operating across multiple repos. Without debt cleanup, small inconsistencies would compound.

Common debt categories included:

• Duplicated logic.
• Stale feature flags.
• Inconsistent error handling.
• Dead code.
• Missing diagnostics.
• Weak test coverage.
• Poorly scoped queries.
• Unclear status transitions.
• Drift between documentation and implementation.
• Temporary fixes that needed promotion into real abstractions.

A human engineering team creates technical debt. An AI engineering fleet creates technical debt faster unless you design counter-pressure into the system.

The counter-pressure was structured cleanup.

Bug Detection and Remediation

Bug detection came from multiple sources:

1. Admin bug reports.
2. Failed-items views.
3. Automated tests.
4. CI failures.
5. Human testing.
6. Review comments.
7. Agent-discovered inconsistencies.
8. Production-preview workflows.

The key was routing.

A bug is only useful if it becomes actionable.

That meant the system needed to know:

• What failed?
• Which repo likely owns it?
• Is there a screenshot or diagnostic payload?
• Is it reproducible?
• Is it blocked?
• Does it need a human decision?
• Can an agent safely attempt remediation?
• Should the fix be bundled with related work?

This is where AI agents can create real leverage. They are good at taking a well-formed issue, inspecting the codebase, identifying a likely cause, and attempting a fix.

They are much weaker when the issue is vague.

So the system was designed to make bugs less vague.

That is the hidden trick: better software maintenance starts with better failure representation.

Lessons Learned Building Miingl.social

After operating this system for months, I would summarize the lessons this way.

1. The PM Agent Is More Important Than the Coding Agent

The coding agents get the attention, but the PM layer creates the leverage.

Without planning, assignment, board management, and escalation, autonomous development becomes chaos.

2. Repo Ownership Beats One Giant Agent

The fleet worked better when agents had clear boundaries.

Specialization reduces collisions and improves local reasoning.

3. Human Testing Is Not Optional

Agents can pass checks while missing product reality.

A human still needs to touch the product, especially for user experience, workflow correctness, and business logic.

4. Issues Are the API for AI Engineering

If you want good agent output, create good issues.

A vague issue produces vague work. A bounded issue with acceptance criteria produces a much better PR.

5. Self-Review Reduces Waste

Agents should review their own work before handing it off.

This catches obvious problems and reduces human review load.

6. Automation Needs Kill Switches

The test-toggle and freeze patterns mattered because sometimes you need to stop the fleet, isolate work, or prevent agents from touching an environment.

7. Cost Optimization Is an Architecture Concern

AI engineering has operating costs.

Bundled work, context reuse, and task grouping are not nice-to-haves. They are part of the system design.

8. The System Needs to Maintain Itself

If the fleet only builds features and never cleans debt, it will eventually slow down or corrupt the codebase.

Maintenance has to be part of the operating model.

9. Escalation Is a Feature

A good agent does not just keep trying forever.

It escalates when the work requires human judgment.

10. Founder Leverage Comes From Orchestration

The biggest unlock was not that I could ask AI to write code.

It was that I could orchestrate a fleet.

That changed my role from “person trying to keep up with implementation” to “operator of an AI-native engineering system.”

How Can Founders Use AI to Accelerate Development?

Founders can use AI to accelerate development by building a structured AI development workflow around issues, repo ownership, branch isolation, automated review, human testing, and clear escalation. The highest-leverage move is not asking one assistant to build everything. It is creating a coordinated system where agents can safely handle repeatable engineering work.

What Startup Founders Can Learn

If you are a startup founder, the practical takeaway is not “go hire 13 agents tomorrow.”

The takeaway is that AI software development becomes dramatically more useful when you stop treating it as a chat tool and start treating it as an operating model.

Here is the founder version.

Step 1: Create Clear Repo or Domain Boundaries

Even if your app is small, define ownership areas.

For example:

1. Web app.
2. API.
3. Database.
4. Automation workflows.
5. Infrastructure.
6. Testing and QA.
7. Documentation.

These boundaries help agents reason safely.

Step 2: Use GitHub Issues as the Work Queue

Do not rely on loose prompts.

Turn work into issues with:

• Goal.
• Context.
• Acceptance criteria.
• Relevant files.
• Constraints.
• Testing expectations.
• Definition of done.

Step 3: Add a PM Layer

At minimum, create a PM prompt or PM agent responsible for planning, sequencing, issue creation, and status tracking.

Eventually, automate parts of this.

Step 4: Require Branch Isolation

Never let agents free-edit your main development branch without controls.

Every meaningful change should happen in an isolated branch with a PR.

Step 5: Require Self-Review

Before an agent says “done,” it should review its own work.

This one practice saves a surprising amount of cleanup.

Step 6: Add Human Testing

You are still responsible for product quality.

AI can accelerate implementation, but it cannot fully replace founder judgment.

Step 7: Build Feedback Intake

Create a structured way for bugs, screenshots, diagnostics, and feature requests to become issues.

This turns product usage into engineering fuel.

Step 8: Add Maintenance Loops

Create recurring workflows for debt cleanup, stale PRs, failed tests, broken workflows, and blocked issues.

Step 9: Watch Cost

Batch related work. Avoid unnecessary context reloads. Do not spawn agents for trivial tasks that can be bundled.

Step 10: Improve the System Every Week

The fleet itself is a product.

Prompt files, runbooks, repo instructions, issue templates, review rules, and escalation paths should evolve as the system teaches you where it breaks.

Comparison: Coding Assistant vs. AI Engineering Fleet

Best Practices for Building an AI Engineering Fleet

Here are the practices I would keep if I rebuilt the Miingl.social fleet from scratch.

1. Start with one PM Agent and two repo-specific agents.
2. Use GitHub issues as the source of truth for work.
3. Require every agent to claim work before starting.
4. Keep branch naming conventions strict.
5. Prevent multiple agents from editing the same subsystem at once.
6. Make every agent perform a PR self-review.
7. Add automated code review before merge.
8. Use human testing environments for product validation.
9. Build bug intake directly into the app.
10. Add failed-state dashboards.
11. Bundle related work to reduce cost.
12. Create explicit escalation rules.
13. Run regular technical debt cleanup.
14. Keep documentation close to the code.
15. Treat the fleet as infrastructure, not a gimmick.

The Future of AI-Native Engineering Teams

The future of software development is not one AI agent replacing one engineer.

That framing is too small.

The future looks more like small human teams operating fleets of specialized agents.

A founder might have:

• A PM Agent.
• A frontend agent.
• A backend agent.
• A data agent.
• A workflow automation agent.
• A QA agent.
• A documentation agent.
• A review agent.
• A research agent.
• A maintenance agent.

The founder becomes the orchestrator.

That does not make engineering easy. It changes the shape of the difficulty.

The hard parts become:

• Designing the system.
• Writing clear issues.
• Maintaining context.
• Preventing drift.
• Reviewing product behavior.
• Managing cost.
• Building trustable promotion workflows.
• Knowing when to stop the agents.
• Knowing when to let them run.

In other words, the future belongs to builders who can combine technical taste with operational discipline.

The best founders will not just use AI. They will design AI-native engineering systems.

Conclusion

Miingl.social was built in approximately two months with an AI Engineering Fleet of 13 agents.

That does not mean the system was effortless. It does not mean the agents were perfect. It does not mean human judgment disappeared.

It means the development model changed.

The work that would traditionally require a coordinated engineering team and roughly a year of development became possible in a much shorter window because the system was not built around a single coding assistant. It was built around a coordinated fleet.

The PM Agent planned and routed work. Repo-specific agents implemented changes. Research sub-agents investigated unknowns. GitHub project boards coordinated state. Branch isolation prevented collisions. Automated reviews and PR remediation workflows improved quality. Human testing environments kept product judgment in the loop. Bug intake and failed-item reporting created maintenance signals. Self-repair and technical debt workflows kept the system from collapsing under its own velocity.

That is the real story.

The future of software development is not “AI writes code.”

The future is AI-native engineering operations.

And for founders, that is the leverage point.

If you can learn to operate an AI Engineering Fleet, you can build more software, with less overhead, faster than traditional teams expect.

But the fleet has to be designed.

Otherwise, you do not get an engineering team.

You get 13 very confident interns editing production code at the same time.

Founder-Focused FAQ

1. What is an AI Engineering Fleet?

An AI Engineering Fleet is a group of specialized AI agents that operate together as an engineering system. Instead of one assistant writing isolated code snippets, the fleet includes agents for planning, implementation, review, remediation, research, maintenance, and escalation. The goal is coordinated software delivery with human oversight.

2. How is an AI Engineering Fleet different from using Cursor, Claude, or ChatGPT?

Cursor, Claude, and ChatGPT can be components inside the workflow, but they are not the full system. An AI Engineering Fleet adds coordination, repo ownership, issue management, branch isolation, review workflows, testing environments, and merge discipline around the models.

3. Can AI agents really build production software?

Yes, but only when they operate inside strong constraints. Agents need clear issues, ownership boundaries, isolated branches, automated review, testing, and human approval. Without those controls, they can generate code quickly but also create instability, drift, and technical debt.

4. How many agents should a founder start with?

Start smaller than you think. A practical starting point is one PM Agent, one frontend or portal agent, and one backend or API agent. Add more agents only when the workflow, repo boundaries, and review process are stable enough to support parallel work.

5. What is the most important agent in the fleet?

The PM Agent is usually the most important. Coding agents create output, but the PM Agent creates order. It manages issue flow, assignment, status, blocked work, review loops, and escalation. Without the PM layer, multiple coding agents can easily create chaos.

6. How do you prevent AI agents from stepping on each other?

Use repo ownership, issue claiming, branch isolation, project board status, and clear merge gates. Agents should not randomly edit the same files or subsystems. Every agent should know what it owns, what branch it is on, and what issue it is solving.

7. Does this eliminate the need for engineers?

No. It changes the leverage model. A founder or technical lead still needs to provide architecture, product judgment, review, testing, and escalation decisions. The fleet reduces implementation overhead, but it does not remove accountability.

8. What are the biggest risks of AI software development?

The biggest risks are technical debt, false confidence, weak testing, unclear ownership, cost creep, and agents making changes outside their context. These risks are manageable, but only if the workflow includes review, branch isolation, human testing, and maintenance loops.

9. How does human-in-the-loop AI engineering work?

Human-in-the-loop AI engineering lets agents perform implementation and maintenance while humans retain control over product intent, acceptance testing, prioritization, and risky decisions. The human is not typing every line of code, but they are still accountable for what ships.

10. What should founders automate first?

Automate issue intake and implementation workflows first. A strong pattern is: bug report or feature request enters the system, becomes a GitHub issue, gets assigned to the right agent, moves through branch and PR workflows, receives review, and then gets tested by a human before promotion.

The post How I Built an AI Engineering Fleet to Ship miingl.social V2 in Two Months appeared first on Jacob Strack Consulting.

Any ethical framework that cannot speak honestly about violence is incomplete.

Resonant Stewardship Ethics (RSE) places agency—the capacity to pause, reflect, and choose—at the center of moral concern. That immediately raises a hard question:

What do we do when someone repeatedly destroys the agency of others through violence?

Prisons dramatically reduce agency.
RSE treats agency reduction as harm.
And yet, society has a legitimate obligation to protect people from catastrophic harm.

This article does not attempt to dissolve that tension.
It holds it directly.

The Non-Negotiable Reality

RSE begins with clarity, not comfort.

• Some individuals are currently unsafe to be free
• Some patterns of behavior reliably annihilate others’ agency
• Some people may never be safe without constraints

This is not moral condemnation.
It is systems-level realism.

RSE does not claim that all harm can be repaired, that all people can be rehabilitated, or that containment is never necessary.

It claims something more precise—and more demanding.

The Core RSE Position on Confinement

RSE makes this principle explicit:

Reducing a person’s agency is ethically permissible only to the degree necessary to prevent greater collapse of agency elsewhere—and never as punishment, moral cleansing, or symbolic revenge.

This reframes incarceration entirely.

Under RSE:

• Confinement is a tragic necessity, not a moral good
• It must be justified continuously, not assumed
• It must be minimized, not ritualized
• It must preserve the possibility of agency wherever safety allows

What RSE Rejects About Traditional Prison

RSE is incompatible with incarceration systems that are:

• Punitive — focused on suffering as justice
• Dehumanizing — treating people as irredeemable
• Indefinite without pathway — no conditions for restoration
• Structurally traumatizing — violence, isolation, humiliation
• Symbolic — designed to satisfy public anger rather than reduce harm

Under RSE, these are not “tough but necessary.”
They are ethical failures layered onto an already tragic constraint.

Containment Is Not Punishment

RSE insists on a clear distinction that modern systems routinely collapse:

Containment (Ethically Permissible)

• Restriction strictly necessary for safety
• Proportional, reviewable, and conditional
• Focused on stabilization and harm prevention

Punishment (Ethically Optional, Often Harmful)

• Suffering imposed to satisfy retribution
• Deterrence through cruelty
• Moral theater masquerading as justice

Dehumanization (Ethically Impermissible)

• Humiliation, neglect, violence, degradation
• Agency destruction beyond necessity
• Systems that create future harm

RSE permits containment.
It rejects punishment as policy.
It forbids dehumanization outright.

Agency Under Constraint Is Still Agency

RSE does not treat agency as all-or-nothing.

Even under confinement:

• Some choices can remain
• Some dignity can remain
• Some meaning can remain
• Some regulation and growth can occur

The ethical task is not to erase agency, but to ask:

How much agency can be preserved without endangering others?

This question should shape:

• Facility design
• Daily routines
• Access to education and therapy
• Levels of autonomy
• Review and release criteria

Why Current Prison Systems Fail (By RSE’s Own Measure)

Modern prisons often:

• Amplify biological stress
• Harden emotional dysregulation
• Reward domination and coercion
• Remove meaningful choice
• Destroy reintegration capacity

From an RSE perspective, this is not just cruel—it is counterproductive.

We often manufacture the future danger we claim to contain.

Permanent Containment: The Hard Case

RSE does not deny that some individuals may require lifelong containment.

It states clearly:

Degrees of freedom are not symmetric when one agent reliably annihilates the degrees of freedom of others.

When release predictably results in severe harm:

• Permanent containment may be the least harmful option
• Rehabilitation may be offered but not presumed
• Release is conditional on demonstrated safety, not moral deserving

Even then:

• The goal is harm minimization
• Not moral erasure or symbolic suffering

Victims and Justice Under RSE

RSE rejects the idea that justice ends with offender punishment.

Victims often lose:

• Safety
• Voice
• Meaning
• Trust in systems

RSE prioritizes victim agency restoration, including:

• Material support and safety
• Choice in participation
• Truth-telling without forced reconciliation
• Boundaries without moral pressure to forgive

Forgiveness is not required.
Engagement is not mandatory.
Agency applies to victims first.

Deterrence Without Cruelty

RSE does not deny deterrence as a social concern.

It rejects only this idea:

That suffering itself is an ethical instrument.

RSE supports deterrence through:

• Certainty of consequence
• Proportionality
• Swift and fair process
• Clear boundaries

Not through:

• Excessive harshness
• Spectacle
• Dehumanization

Cruelty that increases trauma and recidivism is not deterrence—it is failure.

The Epistemic Duty: Why Accuracy Is Ethical, Not Technical

Under RSE, wrongful confinement is among the gravest harms a state can commit.

Therefore, justice systems carry an ethical obligation to:

• High evidentiary standards
• Transparent procedures
• Review and appeal mechanisms
• Rapid correction pathways
• Material repair when harm occurs

Accuracy is not a legal technicality.
It is a moral requirement.

The Tightened RSE Principles (Explicit)

To withstand real-world violence, RSE states the following clearly:

1. The Containment Justification Clause
   Agency restriction is permissible only as the least-restrictive means necessary to prevent greater agency annihilation.
2. The No-Suffering Principle
   Suffering is not a legitimate tool of justice unless inseparable from necessary containment.
3. The Epistemic Duty
   Because wrongful confinement is catastrophic harm, accuracy, review, and reversibility are ethical imperatives.
4. The Victim Restoration Mandate
   Justice is incomplete unless victims’ agency is restored materially, not just symbolically.

The Uncomfortable Truth RSE Refuses to Hide

There is no ethically clean response to extreme violence.

Any response will:

• Harm someone
• Reduce agency somewhere
• Leave moral residue

RSE does not promise purity.
It promises honesty, restraint, and harm minimization.

It rejects vengeance dressed as justice and naïveté dressed as compassion.

Closing

You can say this within Resonant Stewardship Ethics—without contradiction:

Confinement may be necessary.
Dehumanization never is.
Safety is non-negotiable.
So is refusing to turn harm into moral spectacle.

RSE does not make violence easy to talk about.

It makes it possible to talk about it without lying.

And in a world that often chooses vengeance because it feels like clarity,
that honesty may be the most ethical act we have.

The post Resonant Stewardship Ethics and Violence appeared first on Jacob Strack Consulting.

Most ethical systems spend far more time defining what’s wrong than explaining how harm actually happens—or how it gets repaired.

Resonant Stewardship Ethics (RSE) takes a different approach. Instead of beginning with rules, purity, or blame, it starts with a more practical question:

What happens to a person’s ability to choose when pressure, power, or systems close in?

From that perspective, harm and repair look different than we’re used to—and often show up in places we don’t immediately recognize.

How RSE Defines Harm

Under Resonant Stewardship Ethics:

Harm is any action, pattern, or system that predictably reduces an agent’s capacity to pause, reflect, and choose meaningfully—especially through coercion, capture, or enforced dependency.

A few important implications follow from this definition:

• Harm is not limited to intent
• Harm can be structural, relational, technological, or psychological
• Harm often occurs before anyone decides to “do something wrong”
• Harm is measured by agency impact, not by offense or discomfort

RSE is less concerned with whether something feels bad, and more concerned with whether it collapses the space where choice lives.

Obvious Harm (Where Most Frameworks Agree)

Some forms of harm are easy to recognize—and RSE aligns with nearly all ethical traditions here.

Physical Coercion

Violence, threats, confinement, or withholding basic needs to control behavior.

Why this is harm:
It directly collapses biological and psychological agency.

Explicit Manipulation

Blackmail, gaslighting, deception used to force compliance, or leveraging secrets.

Why this is harm:
It removes informed choice and corrupts the ability to arbitrate between options.

Institutional Retaliation

Punishing dissent, silencing whistleblowers, enforcing obedience through fear.

Why this is harm:
Power asymmetry + reduced exit options = agency collapse.

These cases are obvious because the force is visible.

But most harm doesn’t look like this.

Less Obvious Harm (Where RSE Adds Clarity)

RSE becomes most useful in situations where harm is subtle, normalized, or justified.

Harm Through Urgency

When speed replaces consent

Examples:

• “We need an answer right now.”
• “This is your only chance.”
• “If you don’t decide today, it’s gone.”

Why this is harm:
Urgency collapses the pause that free will requires. Even when unintentional, it reduces the ability to reflect.

Harm Through Emotional Leverage

When care becomes coercion

Examples:

• “After everything I’ve done for you…”
• “If you really cared, you would…”
• “I’m just disappointed in you.”

Why this is harm:
Emotion stops being relational and becomes a lever. Choice narrows without explicit force.

Harm Through Technology

When no one is doing anything “wrong”

Examples:

• Infinite scrolls that eliminate stopping points
• Systems that punish disengagement
• Designs that reward outrage or reactivity

Why this is harm:
Technology collapses arbitration at scale. The damage is cumulative, not dramatic.

Harm Through Moral Pressure

When meaning is weaponized

Examples:

• “Good people don’t question this.”
• “If you were ethical, you’d comply.”
• “You should know better.”

Why this is harm:
It weaponizes divinity—what someone holds sacred—to override their agency.

Harm Through Optimization

When efficiency outpaces humanity

Examples:

• Systems that maximize output while ignoring burnout
• Policies that are “logical” but erase human variability

Why this is harm:
Logic and technology dominate while biological and emotional limits are ignored.

No malice required. Just indifference to agency.

Repair in RSE: What It Actually Means

If harm is the collapse of agency, then repair must be the restoration of it.

Under RSE:

Repair is any action that restores or expands an agent’s capacity to pause, reflect, and choose—especially after that capacity has been reduced.

Repair is not:

• Apology alone
• Punishment alone
• Explanation alone
• “Moving on”

Those may accompany repair—but they don’t define it.

Obvious Forms of Repair

Restoring Safety

Removing threats, ending retaliation, re-establishing physical or emotional safety.

Without safety, arbitration cannot return.

Restoring Choice

Offering real options, allowing time, clarifying exit paths.

Often repair begins with:
“You don’t have to decide right now.”

Naming Impact Without Defense

Acknowledging harm without justification or intent-washing.

This restores epistemic agency: the harmed person’s reality is recognized.

Less Obvious (But Powerful) Forms of Repair

Slowing the System

Repair is often structural, not interpersonal.

Examples:

• Reducing demand frequency
• Changing communication expectations
• Removing always-on requirements

This prevents harm from recurring.

Returning Attention

Listening without steering.
Making space without extracting resolution.

Attention is one of the most basic forms of agency.

Separating Meaning From Compliance

Statements like:

• “You still belong even if you choose differently.”
• “This relationship doesn’t depend on agreement.”

This repairs damage to divinity.

Allowing Non-Closure

Not forcing forgiveness.
Not demanding resolution.
Letting boundaries stand.

Repair does not require harmony—only restored choice.

The RSE Harm Test: Simple Questions

These are not moral judgments. They are diagnostic tools.

Before Acting, Ask:

1. Does this reduce someone’s ability to pause and reflect?
2. Am I relying on urgency, fear, shame, or dependency?
3. Would this feel acceptable if I had less power here?
4. Am I collapsing fantasy into reality without consent?
5. Is one harmonic dominating unchecked (biological, emotional, logical, technological)?

If several answers raise concern, harm risk is high.

After Harm, Ask:

1. What capacity was reduced? (safety, time, voice, choice)
2. What would restore options—not just feelings?
3. Where can this be slowed down?
4. What am I tempted to defend that might block repair?
5. How can agency increase going forward, not just now?

Repair is working when:

• Fear decreases
• Options widen
• Voice returns
• Future harm becomes less likely
  

A Quiet Reframe

RSE does not ask:
“Who is wrong?”

It asks:
“Where did agency collapse—and how do we restore it?”

This shifts ethics from punishment to stewardship, from blame to capacity.

Closing

Most harm is not caused by bad people.
It’s caused by unmanaged forces acting faster than reflection allows.

Most repair doesn’t come from judgment.
It comes from restoring the pause.

In a world increasingly designed to collapse that pause,
protecting it may be the most ethical act we have.

The post Harm and Repair in Resonant Stewardship Ethics appeared first on Jacob Strack Consulting.

Every ethical framework is a response to the world it was born into.

Religions, philosophies, and moral systems don’t emerge in a vacuum—they arise to solve specific problems of meaning, coordination, survival, and harm under particular historical conditions.

Resonant Stewardship Ethics (RSE) is no different.

What makes RSE distinct is not that it rejects older frameworks, but that it begins from a reality those frameworks were never designed to face:
a world where agency is fragmented, attention is engineered, technology amplifies impulse at scale, and traditional sources of authority no longer hold consensus power.

This post explores how RSE aligns with existing ethical systems, where it diverges, and why the conditions of modern life may require a new frame—not to replace older ones, but to address what they leave unresolved.

RSE and Religious Ethics

Most major religions are, at their core, ethical systems wrapped in cosmology.

They provide:

• Meaning and purpose
• Shared values
• Moral boundaries
• Narratives that organize behavior

RSE shares these concerns—but approaches them differently.

Where RSE Aligns with Religion

Across traditions, there is strong resonance around several core ideas:

• Human limitation
  Christianity’s original sin, Buddhism’s dukkha, Judaism’s yetzer hara, and Islam’s struggle (jihad) all recognize that humans are not naturally aligned or internally unified.
• Stewardship over dominance
  Many traditions frame moral life as care-taking rather than control: stewardship of creation, right livelihood, humility before God or the Tao.
• Restraint over impulse
  Ethical maturity is rarely about indulgence. It’s about creating space between desire and action.

RSE aligns strongly here. It agrees that ethical life is not about purity, but about how we manage forces that exceed us.

Where RSE Diverges

RSE departs from religious ethics in several key ways:

1. Authority
   Religious ethics typically ground moral authority in divine command, sacred texts, or tradition.
   RSE grounds authority in agency preservation—specifically, whether actions expand or collapse the capacity for choice in self and others.
2. Belief vs harm
   Many religious systems treat belief itself as morally charged.
   RSE treats belief as ethically neutral until it is enforced through coercion.
3. Sin vs capture
   RSE does not frame wrongdoing as moral failure or corruption of the soul.
   It frames harm as capture—the domination of one force (fear, desire, ideology, technology) that collapses arbitration.

In short, RSE explains religious ethical insights without requiring metaphysical agreement—making it usable in pluralistic societies.

RSE and Secular Ethical Frameworks

Modern ethics has largely moved away from religion, but the problems haven’t disappeared—only shifted.

Utilitarianism (Maximizing Outcomes)

Utilitarian ethics asks: What produces the greatest good for the greatest number?

Where RSE agrees:

• Outcomes matter
• Harm is not just intention
• Systems-level thinking is essential

Where RSE disagrees:

• Utilitarianism often sacrifices individual agency for aggregate benefit
• It struggles to account for psychological harm, coercion, and long-term erosion of choice
• It can justify manipulation if results look good

RSE insists that how outcomes are achieved matters, especially when agency is destroyed in the process.

Deontological Ethics (Rules and Duties)

Rule-based ethics focus on universal obligations and moral consistency.

Where RSE agrees:

• Some constraints are non-negotiable
• Not everything can be justified by outcomes

Where RSE disagrees:

• Fixed rules often fail under complexity
• They assume stable, rational agents
• They struggle with trauma, power asymmetry, and context

RSE replaces rigid rules with invariants—chief among them, the preservation of degrees of freedom.

Virtue Ethics (Character and Flourishing)

Virtue ethics asks: What kind of person should I become?

Where RSE agrees:

• Ethics is practiced, not declared
• Character matters
• Context shapes moral action

Where RSE diverges:

• Virtue ethics can unintentionally moralize capacity
• It risks blaming individuals for failures caused by structural or technological forces

RSE shifts focus from “being good” to maintaining the conditions that allow goodness to emerge.

Why Now? Why RSE?

RSE arises not because previous systems were wrong, but because the environment has changed.

Several modern conditions stress older frameworks beyond their design limits:

1. Fragmented Agency

Neuroscience and psychology have made it clear: we are not unified decision-makers. Ethics built on that assumption misfire under stress and trauma.

2. Engineered Attention

Technology now shapes behavior at scale, often bypassing reflection entirely. Most ethical systems were never designed to contend with this.

3. Pluralism Without Authority

Shared moral narratives no longer command consensus. Ethics must function without requiring belief alignment.

4. Power Without Accountability

Institutions can shape lives without proximity or relationship. Ethical frameworks must account for asymmetry and indirect harm.

RSE is designed specifically for these realities.

What Changes If We Adopt an RSE Perspective?

For Individuals

• Less shame, more responsibility
• Better understanding of why “willpower” fails
• Tools for restoring pause under pressure
• Ethics that feel usable, not idealized

For Organizations

• Decision-making that accounts for human limits
• Less reliance on coercive incentives
• Ethical design of systems, not just codes of conduct
• Healthier cultures that reduce burnout and reactivity

For Governments

• Policies evaluated by their effect on agency, not just compliance
• Justice systems focused on restoration, not only punishment
• Better handling of technology, surveillance, and manipulation

For Society

• Reduced moral polarization
• Clearer boundaries between belief and enforcement
• Ethics that scale without dehumanization

The Perspective Shift RSE Requires

RSE asks us to let go of a comforting idea:
that ethics is primarily about being right.

Instead, it reframes ethics as stewardship under constraint.

It asks:

• What forces are operating here?
• Whose agency is being reduced?
• Where can we widen the pause?
• What preserves choice over time?

This is a quieter ethic.
But in a loud, accelerated world, that may be its strength.

A Framework Still Becoming

RSE is not finished. It’s being developed deliberately, in public, and in dialogue with real-world complexity.

It does not ask for conversion.
It asks for experimentation.

If adopted—even partially—it offers a way to navigate modern life without requiring unanimity, purity, or control.

Only stewardship.

And perhaps, enough pause to choose what comes next.

The post Resonant Stewardship Ethics and the World We Actually Live In appeared first on Jacob Strack Consulting.

Resonant Stewardship Ethics (RSE) begins with a simple but uncomfortable truth: most ethical decisions don’t happen in calm, rational moments. They happen when we’re tired, activated, pressured, or afraid.

The first post introduced RSE as a framework grounded in how humans actually experience choice—through competing forces rather than a single, unified will.

This post shows what that looks like on the ground.

Not as ideals.
Not as rules.
But as moments you may recognize immediately.

(If you want the deeper philosophical foundation behind RSE, you can read the original essay here:
https://jakestrack.com/2026/01/11/resonant-stewardship-ethics/)

The Email You Shouldn’t Send Tonight

When urgency feels ethical—but isn’t

Scenario

It’s 10:47pm.
You’re already depleted.

An email comes in from a colleague or client. It’s sharp. Slightly accusatory. It reframes something in a way that feels unfair. You can feel heat in your chest. Your jaw tightens.

Your mind immediately starts composing a response—clear, firm, devastatingly precise.

You tell yourself: “If I don’t respond now, I’m letting this slide.”

Harmonics at play

• Biological: fight response, adrenaline, sleep debt
• Emotional: threat to dignity, desire for justice or recognition
• Logical: constructing arguments, predicting future blame
• Technological: instant delivery, zero friction, permanence

Each harmonic wants something different:

• Biology wants discharge
• Emotion wants validation
• Logic wants control of the narrative
• Technology wants immediacy

None of them care about tomorrow morning.

What restoring the pause looks like in real life

People who protect agency in moments like this don’t rely on willpower. They change conditions.

Examples of how others create pause:

• Writing the email in Notes and deliberately not sending it
• Scheduling the response for the next morning
• Taking a shower or walking outside to let physiology settle
• Sleeping on it—not to avoid conflict, but to widen choice

What’s happening here isn’t avoidance. It’s arbitration.

By delaying action, you allow:

• Biology to downshift
• Emotion to be felt without ruling
• Logic to re-evaluate tomorrow’s risks
• Technology to stop collapsing time

Often, the email you send the next day is still firm—but less costly.

Under RSE, the ethical act wasn’t what you said.
It was protecting the conditions that allowed choice to return.

The Argument That Isn’t Really About the Thing

When two divinities collide

Scenario

You’re in a recurring argument with someone close to you. The topic is concrete—money, parenting, boundaries, work hours—but the intensity feels disproportionate.

Both of you walk away feeling unheard. Both feel like the other is being unreasonable.

Harmonics at play

• Emotional: core meaning is threatened (respect, safety, loyalty, autonomy)
• Biological: nervous system activation from repeated conflict
• Logical: evidence gathering, rehearsing past grievances
• Technological: texts, message threads, screenshots used as proof

What’s actually happening is a collision of divinities:

• One person’s “I must be seen as competent”
• The other’s “I must not be controlled”
• Or “I must feel safe” vs “I must feel free”

Neither is wrong.
But each becomes dangerous when enforced.

How people restore pause without forcing agreement

In RSE-aligned conflict repair, people don’t start with solutions. They start with containment.

Real strategies people use:

• Naming the meta-conflict: “This feels bigger than the topic”
• Taking conversations offline and slowing them down
• Setting time boundaries (“Let’s revisit this tomorrow”)
• Agreeing on what won’t be threatened, even if the issue remains unresolved

Arbitration here means:

• Emotion is acknowledged without being weaponized
• Logic is used to understand patterns, not win
• Biology is regulated enough to stay present
• Technology is prevented from escalating the fight

RSE doesn’t demand resolution.
It demands non-coercion.

Sometimes the ethical outcome is distance, not agreement.

The Scroll That Leaves You Hollow

When nothing “bad” happens—but something is lost

Scenario

You pick up your phone while waiting in line.
Ten minutes pass. Maybe twenty.

You didn’t see anything shocking. No outrage. No explicit harm. But when you put the phone down, you feel vaguely irritated, distracted, and restless.

Harmonics at play

• Biological: dopamine loops, micro-arousal
• Emotional: comparison, subtle dissatisfaction
• Logical: largely offline
• Technological: algorithmic amplification, infinite feed

This is not about content.
It’s about capture.

Technology here isn’t evil—it’s efficient. It collapses micro-pauses where reflection used to live.

How people protect agency here

People who reclaim choice don’t moralize their scrolling. They redesign friction.

Examples:

• Turning phones grayscale
• Keeping certain apps off the home screen
• Creating phone-free zones or times
• Replacing passive scrolling with intentional reading or listening

What’s happening is a rebalancing:

• Logic is brought back online
• Emotion becomes less externally driven
• Biology calms
• Technology shifts from driver to tool

RSE frames this as ethical because attention is the gateway to choice.

What erodes attention erodes free will.

The Thought You’re Afraid to Admit

Why fantasy can be protective

Scenario

You have thoughts or desires you don’t act on.
Ideas you explore privately.
Imaginations that never leave your inner world.

Many people feel shame here—not because they’ve harmed anyone, but because they fear that thinking equals intending.

Harmonics at play

• Biological: impulse generation
• Emotional: meaning-making, fear of judgment
• Logical: moral categorization
• Technological: search engines, private writing, art

RSE draws a critical distinction:
Fantasy is not rehearsal unless it’s made so.

When fantasy is:

• voluntary
• symbolic
• non-coercive
• contained

It often prevents harm rather than causing it.

People who use fantasy ethically often:

• Journal without acting
• Create art that metabolizes impulse
• Talk honestly in safe, consensual spaces
• Allow imagination without literalization

Suppressing fantasy doesn’t eliminate desire.
It removes the buffer that keeps desire from becoming action.

After You’ve Caused Harm

Why repair isn’t punishment

Scenario

You said something that landed wrong.
You crossed a boundary.
You didn’t mean to—but damage happened.

Shame kicks in. Or defensiveness. Or a desire to explain.

Harmonics at play

• Emotional: guilt, fear of rejection
• Biological: threat response
• Logical: justification, minimization
• Technological: texts, apologies, public narratives

RSE reframes repair as agency restoration, not moral cleansing.

Effective repair often looks like:

• Naming impact without self-defense
• Listening without demanding forgiveness
• Changing conditions that allowed the harm
• Accepting boundaries without resentment

Punishment may feel satisfying.
Repair feels slower—but it preserves future choice.

Why RSE Matters

Resonant Stewardship Ethics matters because:

• Free will exists—but it’s fragile
• Harm often happens under pressure, not malice
• Technology reshapes ethics by reshaping attention
• Meaning is personal, but coercion is universal harm

RSE doesn’t ask us to be better people.

It asks us to be better stewards of the conditions that allow choice to survive—in ourselves and in others.

Continuing the Conversation

This framework is still being developed—intentionally in public.

If you see yourself in these examples, you’re already practicing some version of RSE. The framework simply gives language to what careful people often do intuitively.

You can read the foundational essay here:
https://jakestrack.com/2026/01/11/resonant-stewardship-ethics/

More writing will follow—on origin, limits, failures, and application.

Because in a world that increasingly collapses the pause,
keeping it alive may be the most ethical act we have.

The post Resonant Stewardship Ethics in Practice appeared first on Jacob Strack Consulting.

Most ethical systems assume something that doesn’t hold up very well anymore:
that we are unified, rational selves making clear choices in a stable world.

If that were true, life would be simpler.
It also wouldn’t look anything like actual human experience.

We are not one voice inside our heads.
We are many.

Biology pushes.
Emotions pull.
Logic explains.
Technology amplifies.

And most of the time, we are not “choosing” so much as negotiating between forces that don’t agree.

Resonant Stewardship Ethics (RSE) starts from that reality rather than denying it.

The Problem RSE Tries to Solve

Modern life exposes a gap between how ethics talks and how people actually function.

We’re told to:

• “Just make better choices”
• “Act rationally”
• “Control yourself”
• “Ignore your feelings”
• “Trust the system”

But neuroscience, psychology, and lived experience tell a different story:

• Our bodies react before we think
• Trauma shrinks our ability to pause
• Emotions shape what feels possible
• Technology collapses reflection into reaction

RSE begins with a simple question:

What if ethics isn’t about purity or rules, but about protecting the ability to choose at all?

A Different Starting Point

RSE views human beings as complex systems, not sovereign minds.

Within each of us are at least four competing forces:

• Biological needs (survival, comfort, fear)
• Emotional meaning (attachment, values, identity)
• Logical structure (constraints, prediction, coherence)
• Technological amplification (tools that shape attention and behavior)

None of these is wrong.
None of them is in charge.

Life happens in the tension between them.

From this perspective, “free will” isn’t absolute control—it’s the capacity to pause, reflect, and decide which force gets to lead in a given moment.

That capacity is fragile.
It can be strengthened.
It can also be destroyed.

The Ethical Core of RSE

At its center, RSE makes one claim:

Ethical action preserves and expands the ability of people to choose meaningfully.

In practical terms:

• Good actions increase degrees of freedom
• Harmful actions collapse them
• Power carries responsibility because it shapes choice
• Manipulation, coercion, and exploitation are ethical failures—even when justified

Under RSE, “evil” is not having the wrong beliefs or desires.

Evil is reducing another person’s ability to define and explore meaning within a shared reality.

Fantasy, Reality, and Meaning

RSE also draws an important distinction between three domains we often confuse:

• Reality is where actions have irreversible consequences.
• Fantasy is where we safely explore ideas, desires, and identities.
• Meaning (or divinity) is what a person treats as non-negotiable in their life.

Most harm happens when these collapse into each other:

• When fantasy is forced into reality
• When belief becomes law
• When meaning is imposed by fear or force

RSE doesn’t tell people what to believe.
It draws a boundary around how beliefs may be enacted.

Why This Matters Now

We live in a time when:

• Technology shapes attention faster than biology can adapt
• Institutions optimize systems without regard for human agency
• Moral language is used to justify coercion from every direction

RSE doesn’t offer certainty or salvation.

It offers something more modest—and more urgent:
a way to protect choice, dignity, and meaning in a world that increasingly erodes them.

This Is a Beginning

Resonant Stewardship Ethics is not a doctrine.
It’s a framework—a way to see what’s happening underneath our decisions and our conflicts.

If you’ve ever felt torn between impulse and intention,
overwhelmed by systems that don’t care about people,
or suspicious of moral certainty that ignores human complexity,

then this framework may be worth exploring further.

I’ll be developing it here—slowly, carefully, and publicly.

Not to tell anyone how to live,
but to better understand what allows living to remain human at all.

The post Resonant Stewardship Ethics appeared first on Jacob Strack Consulting.

For decades, depression has often been explained as a chemical imbalance—something wrong with serotonin or other brain chemicals that medication is meant to fix. That explanation helped reduce stigma, but modern neuroscience is now showing it is only one small piece of a much larger biological puzzle.

New brain-imaging research suggests depression is better understood as a condition involving miscommunication between brain networks—how different parts of the brain talk to each other—rather than just a shortage of specific chemicals. This shift in understanding helps explain why newer treatments like ketamine and psychedelic-assisted therapy can help some people, why they work differently, and why they can also be dangerous if used incorrectly.

Important Safety Note — Please Read First

Before diving in, it’s critical to be clear:

This article discusses treatments only in clinical, professionally supervised settings.
We are not suggesting self-administered use of ketamine, psychedelics, or cannabis.

These substances powerfully alter brain communication. Used without medical screening, professional guidance, and integration support, they can be extremely detrimental and, in some cases, permanently destabilizing.

These treatments may be unsafe if you have:

• A personal or family history of psychosis or schizophrenia
• Bipolar disorder, especially Bipolar I
• Severe dissociation
• Unstable or acute PTSD
• A history of substance-induced psychosis
• Close relatives with these conditions (genetic risk matters)

If any of these apply, openness-increasing treatments can worsen symptoms, not heal them.

From Chemical Imbalance to Brain Wiring

The older chemical-imbalance story focused on neurotransmitters like serotonin. While brain chemistry does matter, large studies now show that depression is more strongly linked to how brain networks are wired and coordinated.

Advanced brain scans reveal consistent patterns:

• Over-connection in networks tied to rumination and self-criticism
• Under-communication between emotional and logical regions
• Rigid, repetitive brain activity that gets “stuck”

One large study using precision brain imaging found that people with depression have a differently structured salience network—the system that decides what thoughts and feelings grab our attention—and that this pattern often exists before symptoms appear (Nature / NIH summary).

In simple terms:

Depression is often less about “not enough happy chemicals”
and more about brain networks being stuck in unhelpful patterns.

The Emotional Brain and the Logical Brain

To make this easier to understand, it helps to think of the brain in two simplified parts:

• The emotional brain
  (amygdala, limbic system): fear, sadness, threat, emotional pain
• The logical brain
  (prefrontal cortex): reasoning, perspective, planning, regulation

In depression, the emotional brain often becomes overactive, while the logical brain struggles to calm it down. Treatments differ in how they change this balance.

Ketamine: A Top-Down Reset

Ketamine works primarily through the glutamate system and has a top-down effect.

Top-down analogy

Think of ketamine as:

Strengthening the conductor so the orchestra doesn’t spiral into chaos.

Brain scans show ketamine rapidly increases communication in the prefrontal (logical) brain, helping it regain control over emotional overload (Frontiers in Neuroscience).

What this feels like

• Emotional pain quiets
• Thoughts slow down
• Perspective returns
• Suicidal urgency often decreases quickly

Why ketamine can be safer for some

• It doesn’t fully dissolve mental boundaries
• It stabilizes before opening the system
• It’s often better tolerated in severe depression

Limitations

• Relief can be temporary
• Without therapy and integration, benefits fade
• Dissociation can become avoidance if misused

Psychedelics: A Bottom-Up Opening

Classic psychedelics like psilocybin work very differently. They create a bottom-up effect.

Bottom-up analogy

Think of psychedelics as:

Letting the orchestra play freely so new music can emerge.

These substances reduce rigid control networks and dramatically increase neural openness—communication between brain regions that don’t normally talk to each other (Frontiers in Psychiatry).

What this feels like

• Emotional access increases
• Old stories loosen
• New perspectives emerge
• Meaning and insight can arise

Why this can help

• Depression often involves overly rigid brain loops
• Openness allows rewiring during therapy
• A window of plasticity opens where lasting change is possible

Why this can be dangerous

Openness is a power amplifier:

• Insight or delusion
• Healing or destabilization

Without screening, preparation, and integration, psychedelics can:

• Trigger psychosis
• Cause emotional flooding
• Worsen dissociation

THC: Often Overlooked, Not Harmless

Cannabis—especially high-THC products—also increases neural openness. While often viewed as safe, research shows that high-potency THC is associated with increased risk of psychosis, particularly in people with genetic vulnerability (systematic review summary).

This doesn’t mean THC is universally harmful—but it reinforces the core theme:

Substances that open brain communication are not neutral.

Dose, frequency, age, genetics, and mental health history all matter.

Why Dependency Happens Without Addressing Wiring

When treatment focuses only on chemistry:

• Symptoms may improve
• Underlying network patterns remain
• Long-term dependency becomes more likely

When treatment addresses brain wiring and communication, change can be deeper—but only if done safely and professionally.

The Big Picture

Depression is becoming understood as:

• Biological
• Network-based
• Dynamic
• Highly individual

Chemical treatments are not wrong—but they are insufficient on their own for many people. New therapies work not by “adding happiness,” but by changing how the brain communicates with itself.

That power requires care.

Final Thought

These are not lifestyle tools.
They are medical interventions for complex brain conditions.

Used correctly, they can help restore balance between the emotional and logical brain.
Used carelessly, they can destabilize the very systems they aim to heal.

As science advances, so must caution.

Further Reading (Peer-Reviewed Sources)

1. Lynch et al., Nature (2024): Expanded salience network in depression. News-Medical
2. Precision fMRI mapping of depression networks. National Institutes of Health (NIH)
3. Psychedelic connectivity changes (Frontiers in Psychiatry). Frontiers
4. High-THC cannabis and psychosis association. ScienceDaily
5. Ketamine impact on brain connectivity. Frontiers
6. Re-thinking chemical imbalance (Psychology Today summary). Psychology Today

The post Depression Is Not Just a Chemical Imbalance appeared first on Jacob Strack Consulting.

When I began working with miingl, the company faced a familiar challenge for small teams competing in markets dominated by incumbents: organic social content was both time-intensive and underperforming.

Over the prior year, miingl averaged approximately one organic post per month across LinkedIn, Facebook, X, TikTok, and Instagram. Engagement—measured primarily through likes and views—was consistent but flat. More importantly, content creation competed directly with higher-leverage work inside the company.

In the month immediately before building this system, one of the founders intentionally increased effort to approximately 30 hours per week to generate the minimum amount of content required to perform well algorithmically. That effort worked—it proved that higher posting volume could increase reach—but it also surfaced the real constraint:

Manual success was not sustainable.

For a small organization competing against Zoom, Google Meet, Microsoft Teams, and Slack, this was not a staffing problem. It was a systems problem.

The Strategic Constraint: Competing with Incumbents Requires a Different Game

miingl is not feature-rich compared to its competitors—and attempting to out-feature trillion-dollar companies is a losing strategy.

miingl’s advantage lies elsewhere:

• A mission to make online connections as meaningful as in-person ones
• Unique interaction paradigms such as Click-to-Cluster, Suites, and Call-to-Stage
• A clear philosophical position on how digital connection should feel

Historically, miingl’s social content was product-led, even when mission language was included. The underlying goal of those posts was still conversion: drive sign-ups, explain benefits, promote features.

That approach does not build engagement.
It does not create resonance.
And it does not produce a loyal audience.

Based on prior research and experience helping small organizations compete against incumbents, I recommended a decisive shift:

Move from product-led posting to mission-based marketing—optimized solely for engagement, shares, and audience alignment.

No CTAs.
No product promotion.
No feature explanations.

Just the mission, expressed consistently and at scale.

The Solution: Build a System, Not a Content Calendar

Rather than hiring, outsourcing, or expanding manual effort, I designed and built an automated content system using n8n, ChatGPT, Veo video generation, Pomelli, and supporting infrastructure.

From initial design to first post generation took three weeks. Refinement and expansion into additional formats took another month.

Today, the system consists of four engines, approximately 65 workflow nodes, and two intentional human review steps.

Engine 1: Idea Generation and Uniqueness Enforcement

The first bottleneck was not writing—it was idea quality and repetition.

To solve this, the system:

• Tracks all prior seed ideas globally
• Generates five new candidate ideas per run
• Scores them for uniqueness using a comparison process
• Selects the most differentiated idea
• Appends the selected idea back into the dataset for future reference

This prevents recycling, drift, and the “AI sameness” that plagues most automated content systems.

Uniqueness is enforced before any content is generated.

Engine 2: Multi-Format Content Generation

From a single approved seed idea, the system generates multiple post formats, intentionally weighted toward visual and short-form media:

• Text posts: 15%
• Polls: 5%
• Images: 40%
• Short-form video: 25%
• Carousels: 15%

Each format is created specifically for native platform consumption, rather than repurposing the same post everywhere.

Engine 3: Visual and Video Production at Scale

Pomelli is used to generate mission-aligned campaigns and images based on miingl’s business DNA. For each campaign, Pomelli produces multiple images, which are then:

• Reformatted into multiple aspect ratios
• Converted into short videos for Reels, Stories, and TikTok
• Combined with Veo-generated landscape videos
• Captioned via JSON2Video
• Branded with an outro using Shotstack

Assets are stored in Cloudflare R2, while post history and performance data are tracked in Google Sheets, limited to the most recent 50 posts to avoid token and prompt constraints.

Engine 4: Performance Feedback and Adaptation

This is where the system becomes intelligent.

Each post’s performance—views, engagement, and shares—is linked directly back to its original seed idea. On a weekly basis, the system derives implicit, human-readable principles from that data and feeds them back into all upstream prompts.

For example:

• Early outputs leaned heavily toward poetic language
• Performance data showed lower engagement
• The system adapted by deprioritizing abstraction in favor of clarity and relatability

The result is a system that learns, rather than one that simply produces volume.

Human Review (Minimal, by Design)

There are two human touchpoints:

1. A reviewer receives the generated content via email and copies it into Pomelli and Zoho Social (neither has a public API)
2. miingl’s CRO performs final approval inside Zoho Social

Rejection criteria are simple:

• Remove anything that is obviously AI-generated
• Filter based on brand alignment, audience fit, and anticipated reception

This preserves quality without reintroducing the original labor bottleneck.

Early Results (With Appropriate Caution)

This system is still new, and long-term KPIs are still maturing. That said, early indicators are meaningful:

• 84% reduction in social content generation labor
• 76% increase in engagement (aggregated likes and views)
• 23% increase in followers
• Posting frequency increased to 7–14 posts per week on X and TikTok

All results were achieved without paid amplification.

What Comes Next: Closing the Loop Between Engagement and Revenue

The next phase is intentionally designed:

1. Identify the highest-performing organic seed ideas
2. Use those ideas to generate paid ads with CTAs
3. Promote the best-performing paid narratives
4. Feed those validated messages into miingl’s website and product content

Instead of guessing what messaging converts, the audience determines it.

Why This Matters

This project was not about social media.
It was about eliminating operational drag while working inside existing constraints.

For founders and small teams, the lesson is clear:

• Hiring is not the only path to scale
• Automation without strategy accelerates waste
• Systems thinking creates leverage without disruption

My role in this project was not simply automation, content, or tooling.
It was redesigning how work flows through the organization so effort compounds instead of exhausting the team.

That is the work I do.

The post Eliminating Content Bottlenecks Through Systems Design at miingl appeared first on Jacob Strack Consulting.

“Women are all chasing the top 1% of men…
Young men can’t get any sex…
Society is collapsing…
And only the gurus (usually selling a course) can save us.”

It’s a dramatic story.
It makes for great podcast content.
And it’s extremely profitable—for the people telling it.

But here’s the inconvenient part:
The actual data does not support it at all.
In fact, the real story is more normal, less apocalyptic, and—ironically—way more interesting.

First, the big plot twist: everyone is having less sex

Not just men.
Not just “beta males.”
Everyone under 30 is seeing a noticeable drop in sexual activity.

The highlights:

• A 2023 analysis found 38% of Californians aged 18–30 had zero sexual partners last year.
  [Ref 1]
• Millennials born in the 90s were twice as likely as Gen X to have no sexual partners since 18.
  [Ref 2]
• Weekly sex across adults plunged from 55% (1990) to 37% (2024).
  [Ref 3]

If this is a “sexual marketplace,” it’s the slowest marketplace in history.
Even the bears would be bored.

Translation:
This isn’t a case of “women having too many options.”
It’s simply a generation having… less sex.
Period.

Gen Z is also dating less—so the math checks out

You can’t have sex if you never meet anyone. Simple biology.

• Around 44% of Gen Z men report zero romantic relationship experience.
  [Ref 4]
• Young adults are living with parents longer, socializing less in person, and spending more time on devices than ever before.

It’s not “rejection.”
It’s isolation + screens + economy + exhaustion.

No villain. No conspiracy.
Just physics:
If you never leave the house, you meet approximately zero people, and it’s hard to feel sexy with Mom in the next room.

Women are not exclusively chasing the “top 1% of men”

This is the part where red-pill influencers dramatically clutch their pearls, but the studies are clear.

What the data shows:

• Women’s ratings of attractiveness skew low,
  but their messaging doesn’t.
  They mostly message men who are just slightly above average.
  [Ref 5]
• Men tend to “aim up” and message more desirable partners.
  Women message similar partners.
  [Ref 6]
• eHarmony found that men who think they’re “10/10 hot” actually get fewer messages than men who rated themselves 5–9/10.
  [Ref 7]

Let me repeat that last one for the folks in the back:

Being extremely hot is not a cheat code.
Being moderately attractive is actually better for incoming messages.
Which means the entire “elite men hoard all the women” storyline… doesn’t match reality.

The real reasons sex is down are boring—but important

No guru wants to talk about these because they don’t sell $499 masculinity courses.

The actual big drivers:

• Digital life
  Phones replaced flirting.
  TikTok replaced mingling.
  Porn replaced exploration.
  DMing replaced talking.
  (None of this is sexy.)
• Economics
  Housing is expensive.
  Privacy is rare.
  Stress is high.
  Anxiety kills libido faster than any dating app.
• Delayed adulthood
  Young adults are hitting milestones later: jobs, independence, relationships, and families.
• Consent + mental health awareness
  People are more cautious, more thoughtful, and less impulsive with sex.

Not exactly the fire-and-brimstone nightmare the internet promised.
Just a different world.

And no—“sexless young men” are not becoming more dangerous

This narrative gets repeated over and over, but it collapses the second you look at crime data.

• Violent victimization is way down from the 1990s peak.
  [Ref 8]
• Youth sexual offense rates have generally declined over the past few decades.
  [Ref 9]

If “lack of sex causes chaos,” the crime charts forgot to cooperate.

Reality check:
Young men aren’t becoming violent because they’re not having sex.
They’re not having sex because society changed.

So what’s actually happening?

After all the research, the most accurate summary is:

Modern dating isn’t broken.
It’s just different.

• People are more isolated.
• They socialize less in person.
• They date less frequently.
• Sex is no longer the primary coping mechanism for stress, trauma, or boredom.
• Women aren’t chasing the top 1%.
• Men aren’t being systematically rejected.
• The “sexual crisis” is really a structural shift, not a romantic apocalypse.

If anything, young people might be developing healthier, slower, more intentional relationship habits—just in a world that doesn’t look anything like the one older generations grew up in.

References

1. Los Angeles Times, survey on sexual partners among young adults (2023)
2. Twenge, et al., Archives of Sexual Behavior, declines in sexual activity among young adults
3. Institute for Family Studies, national sexual frequency trends (2024)
4. American Institute of Behavioral Medicine, Gen Z relationship experience data
5. Haverford College analysis of OkCupid messaging patterns
6. PLOS One, “Desirability and Mate Choice on Online Dating Platforms” (2018)
7. Oxford Internet Institute + eHarmony, “The New Leading Man” analytics
8. Bureau of Justice Statistics, violent victimization trends
9. UNH Crimes Against Children Research Center, long-term sexual abuse case decline

The post Are Women Really Only Dating the Top 1% of Men? New Research Says No — And the Truth Is Much More Interesting appeared first on Jacob Strack Consulting.