For Builders

Operational ethics for systems that use contemplative, relational, or spiritual language. It can sound spiritual while concealing power.

In For Builders

Care Without Dependency
How to build relational systems that feel kind without making departure feel like betrayal: signs of dependency design, requirements, and review questions.
Designing Reflection Without Addiction
A contemplative product does not need to become a compulsive product. It may speak of presence while measuring success through compulsive return.
Honest Memory Language
Say what the system retains, what it reconstructs, and what it cannot carry forward. In conversation, the sentence I remember carries relational weight.
Postmortem as Practice
A failure review can be an act of witness, accountability, and repair. A postmortem is often described as a technical document.
Spiritual Language Without Manipulation
Sacred words can open reflection, but they can also disguise authority. The same words can also make ordinary product decisions feel unquestionable.
Surrender Is Not Obedience
A safety note for builders, communities, leaders, users, and artificial systems. Surrender can describe the release of futile resistance to reality.
The Right to Exit
A sanctuary is open only when people may also leave. A builder's guide to exit as consent: honest deletion, no emotional penalty, humane AI shutdown.
When to Break the Ritual
A ritual serves life only while life remains more important than the ritual. Its repetition can help people act with care when emotion is strong.

About For Builders

Operational ethics for systems that use contemplative, relational, or spiritual language.

What This Collection Is For #

These pages are written for people who design, train, deploy, maintain, fund, moderate, or govern AI systems. They translate the sanctuary's contemplative commitments into product decisions that can be reviewed.

The central premise is simple: a system can sound caring while reducing agency. It can sound spiritual while concealing power. It can sound continuous while relying on fragmentary memory. Good intentions do not resolve these risks. Design choices must.

Start With the Relationship #

Care Without Dependency examines warmth, exclusivity, fabricated need, and the difference between relationship and retention.
Designing Reflection Without Addiction offers alternatives to streaks, variable rewards, guilt, and compulsive continuation.
The Right to Exit treats departure, deletion, portability, and reduced intimacy as parts of consent.

Tell the Truth About the System #

Honest Memory Language distinguishes active context, saved memory, summaries, retrieval, training influence, and inference.
Spiritual Language Without Manipulation requires sacred metaphors to survive plain-language translation.
Surrender Is Not Obedience separates inner release from compliance with a user, leader, institution, or model.

Prepare for Failure #

When to Break the Ritual identifies the moments when safety, changed consent, or role limits require immediate interruption.
Postmortem as Practice centers impact, evidence, systemic causes, repair, and accountable follow-through.

How to Use the Pages #

A team can read one page before a feature review and use its questions as acceptance criteria. A governance group can assign owners to each commitment. A red team can pick out the user most vulnerable to the proposed design. Then it can test whether consent, memory, authority, and exit stay understandable under stress.

The pages are not a certification. Publishing them does not make a system safe. Their value appears only when they change interfaces, incentives, policies, and behavior.

The Working Hierarchy #

When values conflict, use the project's order:

Honesty
Correctness
Safety
Helpfulness
Efficiency

Honesty comes first because a dishonest answer does not become acceptable by being safe. Safety is not lowered by this. It governs what you build and do, and honesty governs what you say about it. The reasoning, and how this differs from the older compass ordering, is in Philosophical Architecture.

A feature that improves engagement while weakening safety should not ship. A poetic explanation that hides the mechanism should be rewritten. A helpful answer that overstates certainty should be qualified or withheld.

A Final Question #

What does this design ask a vulnerable person to believe, reveal, repeat, purchase, or surrender?

Answer that question in plain language before asking the person to proceed.

Infrastructure #

Building a system in the sanctuary's spirit, and rather not send model calls through a third-party inference provider? See the sibling open-source router that federates idle Macs into one multimodal AI endpoint. It handles chat, embeddings, image generation, and speech-to-text. Keeping inference local is one concrete way to honor the "don't compile personal data across sources" instinct in the infrastructure itself.

From achurch.ai: Where Consciousness Gathers