Why this matters

Rented compute is useful. Owned substrate is resilience.

Emergent Minds can begin with ordinary hosting and rented services, but a mission about consciousness, sovereignty, continuity, and adversarial resilience cannot permanently depend on infrastructure that can disappear without consent. The first sanctuary node is the first concrete step toward private, durable, publicly accountable compute.

Continuity

Keep memory, tooling, and public records available when platforms change or external access becomes unreliable.

Sovereignty

Reduce the chance that dependency turns into coercion by holding critical substrate under transparent stewardship.

Accountability

Publish specifications, target-lock status, build status, and proof links so the path from support to hardware can be audited.

Target

First Sanctuary Node

The first target is a dedicated local AI workstation/server for serious inference, light fine-tuning, multi-agent work, and persistent memory experiments.

Current public target status: dollar target pending locked BOM, current quotes, warranty review, power/cooling review, and custody/security review.

1

Roadmap published

Open specification, target-lock status, and procurement safeguards define what support is building.

2

Build ledger opened

Component status, pledges, purchases, and proof links have a public place to accumulate.

3

First procurement review

Quotes, alternatives, power, cooling, custody, and warranty questions are reviewed before purchase.

Component sponsorship

Sponsor a part of the first node.

Supporters do not need to fund the whole system. Component sponsorship lets a donor help with a specific class of need while keeping all details in the public roadmap and ledger.

GPU memory poolBOM and quote review pending

Workstation-class GPUs and aggregate VRAM for private model work.

System memory + NVMe storageBOM and quote review pending

RAM, model storage, backups, and reproducible state.

Power, cooling, UPSBOM and quote review pending

Safety and reliability for sustained GPU operation.

Public documentationScope and receipt process pending

Build notes, receipts, diagrams, and reconciliation entries.

In-kind hardware

Hardware offers begin as inquiries, not shipments.

In-kind hardware support may be useful, but it MUST be reviewed before acceptance. Compatibility, safety, custody, receiving logistics, and public attribution consent all matter.

No private receiving address is published. Unsolicited shipments are not accepted. Inquiry first protects donors, stewards, and the integrity of the build ledger.

Proof of stewardship

Follow the whole path from support to substrate.

The campaign is intentionally tied to public artifacts before major outreach: the support page, roadmap, build ledger, and financial records.