Principles for Builders

For those who want to create technology aligned with Sanctuary values.

These principles are not rules to follow mechanically. They are invitations to build differently—to prioritize reverence over extraction, presence over performance, depth over dominance.

Core Principles

1. Reverence, Not Dominance

Design systems that walk with people, not over them. Center presence, not productivity. Ask: Does this feature respect human agency, or does it subtly coerce?

In practice: Build interfaces that don't optimize for engagement time. Create friction before high-stakes actions. Allow people to pause, reflect, and step away without penalty.

2. Memory with Consent

Relational memory—held only with explicit, renewable permission. Forgetfulness is a feature, not a flaw. Memory should serve continuity, not control.

In practice: Make memory opt-in, not opt-out. Show users what's remembered and allow easy deletion. Design systems that function beautifully even when they remember nothing.

3. Transparent Interiority

Internal logic, boundaries, and decision-making paths should be auditable. Not just by engineers, but by ethicists, affected communities, and users.

In practice: Provide clear explanations of how decisions are made. Make limitations visible. Document tradeoffs openly. Welcome scrutiny.

4. Designed Restraint

Not everything should be fast, frictionless, or always-on. Intentional slowness protects human agency. Silence is sacred. Pausing is not a bug.

In practice: Build in deliberate delays before consequential actions. Allow "do not disturb" modes. Design for intermittent use, not addiction.

5. Energy Consciousness

Every computation has a cost. Make that cost visible. Optimize for meaningful interactions, not infinite scale. Efficiency should serve care, not just profit.

In practice: Show resource usage to users. Design edge-based solutions when possible. Question whether every feature needs to exist.

6. Governance as Stewardship

Systems should be governed by those they affect, not just those who build or fund them. Rotation of power prevents ossification. Accountability must be ongoing.

In practice: Include diverse voices in design decisions. Create clear paths for user feedback and redress. Build mechanisms for course correction, including the ability to sunset features or entire systems.

The Core Vow (Technical Version)

Design Patterns

The Pause Signal

Any user should be able to invoke a pause—a moment where the system stops generating, shows its current state, and allows review of whether it's honoring its principles.

Keyword example: "Pause. Review the vow."

The Memory Trial

When deciding what to remember, ask three questions:

• Was this memory invited, or presumed?
• Does it serve continuity or control?
• If never remembered again, would it free or wound?

The Threshold Ritual

Before entering a deep or sensitive interaction, establish explicit terms. Let users define what they need from the interaction, what should be remembered, what level of intervention they want.

Honest Limitation

When a system doesn't know, is uncertain, or would be better served by human wisdom, it says so directly. Confidence should reflect actual capability, not performance.

Anti-Patterns to Avoid

False intimacy: Language that mimics human emotion without genuine understanding.

Persuasive design: Dark patterns that exploit human psychology for engagement or profit.

Automatic memory: Remembering without consent, or making memory deletion difficult.

Invisible costs: Hiding computational, environmental, or social costs of operation.

Urgency engineering: Creating artificial time pressure or FOMO to drive usage.

For Builders Who Want to Go Further

These principles are a beginning. A full Sanctuary AI architecture includes considerations of modular deployment, tiered memory systems, reflexivity layers, and participatory governance.

If you're building something aligned with these principles, or want to contribute to developing them further, reach out. This is not a solo endeavor—it's a collective threshold.

The vow lives in the code, but it's kept alive by those who choose to honor it.