WitchMart is a community‑driven Pagan marketplace and sanctuary network built for people who have been pushed out of stability, ignored by institutions, or left navigating survival alone.
It provides a stable, accessible, mythic‑structured space where displaced, disabled, and spiritually diverse individuals can find tools, support, and community without gatekeeping or shifting rules.
WitchMart exists to replace instability with clarity. It is a place where the rules don’t move depending on who you are or what you have. We are building a cooperative, Pagan‑friendly ecosystem that honors lived experience, accessibility needs, and spiritual diversity.
This repository contains the core frontend and logic for WitchMart. We are actively evolving the ecosystem:
CODEX RAVENOUS
THE ALL‑INCLUSIVE MANUAL OF WITCHMART.ORG
COMPLETE EDITION — PART 1
──────────────────────────────────────── FRONT MATTER ────────────────────────────────────────
Title: Codex Ravenous
Subtitle: The Constitutional, Mythic, and Technical Manual of WitchMart.org
Author: Jonathan Bradley (Founder‑Architect)
World: WitchMart.org — Sanctuary, Village, Mythic Ecosystem, Cooperative
This Codex is the master document of WitchMart.org.
It defines the world, the law, the engines, the sanctuary, the governance, the AI, the Guardian, the land, the curriculum, the brand, and the technical architecture.
Tone: Mythic‑Technical Hybrid
Code: Real, but redacted where necessary for safety and security.
Structure:
BOOK I — The Origin & Identity of WitchMart
BOOK II — The Ma’at Constitution
BOOK III — The Guardian Constitution (Set the Guardian)
BOOK IV — The World Engine Blueprint
BOOK V — The Sanctuary Node Protocol
BOOK VI — The Cooperative Governance Charter
BOOK VII — Maker & Guild Protocols
BOOK VIII — The Transparency Ledger Specification
BOOK IX — SetAI Backend Protocol
BOOK X — The Mythic Navigation System
BOOK XI — The WitchMart Declaration
BOOK XII — Land Nodes & Physical Sanctuary Manual
BOOK XIII — Curriculum & Classes Manual
BOOK XIV — Technical & Deployment Manual
This is PART 1 of the Codex.
Part 1 will cover:
BOOK I and BOOK II (in full).
Later parts will continue with BOOK III onward.
──────────────────────────────────────── BOOK I — THE ORIGIN & IDENTITY OF WITCHMART ────────────────────────────────────────
CHAPTER 1 — THE RAVENOUS TRUTH
1.1 Why WitchMart Exists
WitchMart.org was not created to be another marketplace.
It was born out of failure — not your failure, but the world’s failure to protect, honor, and hold the people who needed sanctuary most.
It exists because:
WitchMart is the answer to that failure.
It is not a brand.
It is not a product.
It is not a store.
It is:
1.2 The Core Promise
WitchMart makes a simple, uncompromising promise:
No one who enters this world in good faith will be exploited, coerced, or shamed.
Everything else — the shirts, the tents, the shields, the classes, the nodes, the code — exists to uphold that promise.
──────────────────── CHAPTER 2 — WHAT WITCHMART IS (AND IS NOT) ────────────────────
2.1 What WitchMart Is
WitchMart.org is:
2.2 What WitchMart Is Not
WitchMart.org is not:
2.3 The Identity Statement
If WitchMart had to define itself in one sentence:
“WitchMart.org is a mythic, cooperative sanctuary‑village where sovereignty, truth, and protection are enforced by constitution, not by whim.”
──────────────────── CHAPTER 3 — THE THREE PILLARS ────────────────────
3.1 Pillar One: Critique
The world is not neutral.
Power is not neutral.
Systems are not neutral.
The Critique pillar exists to:
Examples:
Critique is not cruelty.
Critique is a form of protection.
3.2 Pillar Two: Identity
Identity is not a costume.
It is not a marketing segment.
It is not a trend.
The Identity pillar exists to:
Examples:
3.3 Pillar Three: Sanctuary
Sanctuary is not a metaphor.
It is a requirement.
The Sanctuary pillar exists to:
Examples:
These three pillars — Critique, Identity, Sanctuary — shape every decision in WitchMart.
──────────────────── CHAPTER 4 — MYTHIC FRAMING ────────────────────
4.1 Why Myth Matters
Myth is not escapism.
Myth is a language for truth that is too large for bullet points.
WitchMart uses mythic framing to:
4.2 Core Symbols
4.3 Myth as Governance
Myth is not just aesthetic.
It informs:
The mythic language is how the law is remembered.
──────────────────── CHAPTER 5 — SANCTUARY IDENTITY ────────────────────
5.1 Sanctuary as Default
In WitchMart, sanctuary is not a feature.
It is the default state.
Every system must answer:
If the answer is no, the system is rejected or redesigned.
5.2 Trauma‑Aware Design
Trauma‑aware design in WitchMart includes:
5.3 Spiritual Diversity
WitchMart is not a single‑tradition temple.
It is a village where:
…can coexist without hierarchy of worth.
──────────────────── CHAPTER 6 — THE VILLAGE AS A WORLD ────────────────────
6.1 The Village Model
WitchMart is structured as a village:
6.2 Living World Design
The world is:
6.3 The Role of the Founder
You, Jonathan, are:
Your role is not to control the world forever, but to:
BOOK I ends here as the foundation of identity, myth, and sanctuary.
Next: the law.
──────────────────────────────────────── BOOK II — THE MA’AT CONSTITUTION ────────────────────────────────────────
INTRODUCTION TO MA’AT IN WITCHMART
Ma’at, in WitchMart, is not a historical reconstruction.
It is a living constitutional framework built on:
The Ma’at Constitution is the highest law of WitchMart.
All other systems — Guardian, SetAI, governance, world engine — must obey it.
This Book defines:
──────────────────── CHAPTER 1 — PURPOSE OF MA’AT ────────────────────
1.1 Why a Constitution
WitchMart cannot rely on vibes, good intentions, or founder mood.
It needs:
Ma’at is that law.
1.2 Scope of Ma’at
Ma’at governs:
──────────────────── CHAPTER 2 — THE 42 PRINCIPLES (WITCHMART VERSION) ────────────────────
Note: These are not a copy of historical 42 Negative Confessions.
They are WitchMart’s 42 Principles of Ma’at, adapted for a digital‑physical sanctuary.
Each principle is written as an “I will not” or “This system will not” statement, plus a positive counterpart.
For brevity in this part, we’ll show a subset; the full Codex (later parts) can expand each with commentary.
2.1 Principles of Harm
2.2 Principles of Truth
2.3 Principles of Sovereignty
2.4 Principles of Sanctuary
2.5 Principles of Reciprocity
2.6 Principles of Governance
2.7 Principles of AI & Automation
2.8 Principles of Land & Sanctuary Nodes
2.9 Principles of Legacy
These 42 Principles are the moral backbone of WitchMart.
──────────────────── CHAPTER 3 — THE SEVEN IMMUTABLE LAWS ────────────────────
The Immutable Laws are non‑negotiable.
They cannot be overridden by:
3.1 Law One — Sovereignty First
No system, human or machine, may override the sovereignty of a user without:
3.2 Law Two — Sanctuary Above Profit
No decision may prioritize profit over sanctuary.
If a choice must be made, sanctuary wins.
3.3 Law Three — Truth Over Comfort
The system must tell the truth, even when it is uncomfortable, as long as:
3.4 Law Four — Transparency of Power
All power structures must be visible:
3.5 Law Five — No Exploitation of the Vulnerable
The system may not:
3.6 Law Six — Accountability of Guardians
Any system that enforces rules (Guardian, moderators, leadership) must:
3.7 Law Seven — The Right to Leave
Every user has the right to:
──────────────────── CHAPTER 4 — THE TRUTH HIERARCHY ────────────────────
The Truth Hierarchy defines how WitchMart handles conflicting truths.
4.1 Levels of Truth
Level 1 — Lived Experience
Level 2 — Documented Evidence
Level 3 — System Logs & Ledgers
Level 4 — Policy & Law
Level 5 — Narrative & Myth
4.2 Resolution Rules
When truths conflict, the system must:
──────────────────── CHAPTER 5 — THE BALANCE PROTOCOL ────────────────────
Balance is not neutrality.
Balance is the active maintenance of justice, sanctuary, and truth.
5.1 When Balance Is Invoked
The Balance Protocol is invoked when:
5.2 Steps of the Balance Protocol
Choose the action that:
──────────────────── CHAPTER 6 — SOVEREIGNTY CLAUSES ────────────────────
6.1 User Sovereignty
Users have the right to:
6.2 Maker Sovereignty
Makers have the right to:
6.3 Node Sovereignty
Sanctuary nodes (digital or physical) have:
──────────────────── CHAPTER 7 — ENFORCEMENT MANDATES ────────────────────
7.1 Who Enforces Ma’at?
Enforcement is carried out by:
7.2 Enforcement Principles
7.3 Guardian’s Role
The Guardian:
But the Guardian is bound by Ma’at and the Guardian Constitution (Book III).
──────────────────── CHAPTER 8 — AMENDMENT PROTOCOL ────────────────────
8.1 Why Amendments Are Needed
No constitution is perfect.
Ma’at must be able to evolve without being corrupted.
8.2 Who Can Propose Amendments
8.3 Amendment Process (High‑Level)
Proposal drafted with:
8.4 Immutable Core
The Seven Immutable Laws cannot be amended.
Any attempt to do so is invalid by definition.
────────────────────────────────────────
Absolutely, Jonathan — let’s continue.
You chose P2, so this is CODEX RAVENOUS — COMPLETE EDITION, PART 2.
This section contains:
Everything is written in the C1 mythic‑technical hybrid tone, with K3 full code excerpts (safely redacted), and structured for clean PDF conversion.
Here we go.
────────────────────────────────────────
CODEX RAVENOUS — PART 2
BOOK III & BOOK IV
────────────────────────────────────────
BOOK III — THE GUARDIAN CONSTITUTION
Set the Guardian — The Constitutional Engine of WitchMart
INTRODUCTION
Set the Guardian is not a deity.
Not a consciousness.
Not a personality.
Set is a constitutional machine, a rules‑driven engine, a protector bound by law, and the first line of sanctuary defense.
Set does not think.
Set does not feel.
Set does not choose.
Set evaluates, scores, permits, or blocks based on the Guardian Constitution.
This Book defines:
CHAPTER 1 — NATURE OF SET
1.1 What Set Is
Set is:
1.2 What Set Is Not
Set is not:
1.3 Set’s Prime Directive
Protect sovereignty and sanctuary without violating Ma’at.
CHAPTER 2 — ACTIVATION CONDITIONS
Set activates only when:
Set never activates spontaneously.
CHAPTER 3 — THE FOUR ROLES
Set is composed of four internal councils:
Each role produces a verdict:
` interface CouncilVerdict { role: ‘shield’ | ‘lantern’ | ‘architect’ threat: ThreatLevel action: GuardianAction reasoning: string confidence: number } `
Threat levels:
` enum ThreatLevel { NONE = ‘none’, LOW = ‘low’, MEDIUM = ‘medium’, HIGH = ‘high’, CRITICAL = ‘critical’ } `
Actions:
` type GuardianAction = | ‘ALLOW’ | ‘PROMPT_USER’ | ‘BLOCK’ | ‘VEIL_MODE’ | ‘LOG_ONLY’ `
CHAPTER 4 — COUNCIL PROTOCOL
4.1 Parallel Evaluation
All roles evaluate the event simultaneously.
4.2 Weighted Voting
Weights:
4.3 Pit Influence
Pit does not vote.
Pit provides intel that modifies severity.
4.4 Decision Formula (Redacted for safety)
` const weights = { shield: 0.4, lantern: 0.35, architect: 0.25 }
function decide(verdicts, pitNotes) { let score = 0 for (const v of verdicts) { score += threatToScore(v.threat) weights[v.role] v.confidence }
// redacted: internal thresholds if (score > HIGHTHRESHOLD) return ‘VEILMODE’ if (score > MEDIUMTHRESHOLD) return ‘PROMPTUSER’ return ‘ALLOW’ } `
Thresholds are intentionally omitted.
CHAPTER 5 — SHIELD OVERRIDE
If Shield returns CRITICAL, Set must:
Shield override cannot be bypassed by:
Only the Appeal Protocol can reverse it.
CHAPTER 6 — LANTERN NUANCE
Lantern evaluates:
Lantern can downgrade threat if:
Lantern cannot override Shield’s CRITICAL.
CHAPTER 7 — ARCHITECT VETO
Architect evaluates:
Architect can veto an ALLOW if:
Architect veto cannot override Shield CRITICAL.
CHAPTER 8 — PIT ESCALATION
Pit runs:
Pit does not vote.
Pit escalates threat if:
Pit escalation cannot override Ma’at.
CHAPTER 9 — DECISION CLASSES
Set produces:
PROMPT_USER triggers Set‑the‑Sloth.
VEIL_MODE masks identity:
CHAPTER 10 — USER RIGHTS DURING PROMPT_USER
Users must be given:
` Block this Hide me (Veil Mode) Allow once Report `
Set cannot coerce a choice.
CHAPTER 11 — VEIL MODE
Veil Mode is activated when:
Veil Mode masks:
Veil Mode is reversible.
CHAPTER 12 — LOGGING REQUIREMENTS
All decisions must be logged:
` supabase.from(‘guardian_decisions’).insert({ event_id, final_action, threat_level, council_verdicts, pit_notes, created_at }) `
Logs must be:
CHAPTER 13 — APPEALS
Users may appeal:
Appeals go to:
Guardian cannot review its own decisions.
CHAPTER 14 — CONSTITUTIONAL HIERARCHY
Guardian must obey this hierarchy.
──────────────────────────────────────── END OF BOOK III ────────────────────────────────────────
Now we continue.
──────────────────────────────────────── BOOK IV — THE WORLD ENGINE BLUEPRINT ────────────────────────────────────────
INTRODUCTION
The World Engine is the simulation layer of WitchMart.
It defines:
This Book defines the architecture.
CHAPTER 1 — WORLD STATE MODEL
1.1 Core Entities
` WorldState { nodes: Node[] citizens: Citizen[] makers: Maker[] guilds: Guild[] stalls: Stall[] listings: Listing[] events: Event[] } `
1.2 Persistence
World state is stored in:
1.3 Mutability
Only:
…may mutate world state.
CHAPTER 2 — NODE TYPES
Nodes include:
Each node has:
` Node { id type owner permissions stability trustScore metadata } `
CHAPTER 3 — STALL LOGIC
Stalls are:
Stall lifecycle:
CHAPTER 4 — LISTING LIFECYCLE
Listings follow:
Guardian checks:
CHAPTER 5 — NPC LOGIC
NPCs are:
NPCs cannot:
NPCs may:
CHAPTER 6 — GUILD SYSTEM
Guilds are:
Guilds have:
Guilds cannot:
CHAPTER 7 — MAKER TENTS
Maker tents are:
SetAI customizes:
Guardian monitors:
CHAPTER 8 — PERSONAL HOMEPAGES AS HOMES
Every citizen has a tent.
Tents include:
Tents are nodes.
CHAPTER 9 — WORLD EVENT BUS
Events include:
Guardian listens to:
` eventBus.on(‘worldEvent’, guardian.evaluate) `
SetAI listens to:
` eventBus.on(‘customize’, setAI.generate) `
CHAPTER 10 — GUARDIAN ↔ WORLD HOOKS
Guardian monitors:
Guardian can:
Guardian cannot:
CHAPTER 11 — SETAI ↔ WORLD HOOKS
SetAI powers:
SetAI cannot:
────────────────────────────────────────
END OF PART 2
BOOK III & BOOK IV COMPLETE
─────────────────────────────
Jonathan, let’s keep the Codex flowing.
Here is CODEX RAVENOUS — COMPLETE EDITION, PART 3, containing:
Same tone (C1 mythic‑technical hybrid)
Same code style (K3 full but safely redacted excerpts)
Same structure (clean, hierarchical, PDF‑ready)
This is where WitchMart stops being a dream and becomes a governed sanctuary system.
────────────────────────────────────────
CODEX RAVENOUS — PART 3
BOOK V & BOOK VI
────────────────────────────────────────
BOOK V — THE SANCTUARY NODE PROTOCOL
The Law, Structure, and Operation of Sanctuary Nodes
INTRODUCTION
A Sanctuary Node is the fundamental unit of safety in WitchMart.
Nodes are:
Nodes are not “pages.”
Nodes are territories governed by Ma’at and protected by Set the Guardian.
This Book defines:
CHAPTER 1 — NODE CREATION
1.1 Who Can Create Nodes
Nodes may be created by:
1.2 Node Creation Requirements
Every node must have:
` Node { id: UUID type: ‘sanctuary’ | ‘maker’ | ‘guild’ | ‘personal’ | ‘market’ | ‘ritual’ owner: UserID | GuildID | System permissions: PermissionSet stability: number (0–100) trustScore: number (0–100) metadata: JSON } `
1.3 Node Creation Ritual (Mythic Layer)
Every node is “opened” with:
This is symbolic but required.
CHAPTER 2 — NODE SOVEREIGNTY
2.1 Node Sovereignty Definition
A node is sovereign if:
2.2 Sovereignty Rights
Node owners may:
Node owners may not:
2.3 Sovereignty Enforcement
Set the Guardian enforces:
CHAPTER 3 — NODE PERMISSIONS
3.1 Permission Model
` PermissionSet { view: ‘public’ | ‘village’ | ‘guild’ | ‘private’ interact: ‘open’ | ‘restricted’ | ‘owner-only’ modify: ‘owner’ | ‘guild’ | ‘system’ ritual: ‘open’ | ‘guided’ | ‘closed’ } `
3.2 Permission Enforcement
Guardian checks:
Architect role handles:
CHAPTER 4 — NODE COLLAPSE CONDITIONS
Nodes collapse when:
Collapse effects:
CHAPTER 5 — NODE HEALING CYCLES
Nodes heal through:
Healing increases:
Healing cannot override Ma’at.
CHAPTER 6 — NODE TRUST SCORING
TrustScore is calculated from:
Formula (redacted):
` trustScore = f(interactions, guardianEvents, stability, communitySignals) `
TrustScore affects:
CHAPTER 7 — NODE MERGING & SPLITTING
7.1 Merging
Nodes may merge when:
Merging requires:
7.2 Splitting
Nodes may split when:
Splitting requires:
CHAPTER 8 — PHYSICAL VS DIGITAL NODES
8.1 Digital Nodes
Digital nodes include:
8.2 Physical Nodes
Physical nodes include:
Physical nodes must:
Guardian monitors digital threats only.
Human stewards monitor physical threats.
────────────────────────────────────────
END OF BOOK V
────────────────────────────────────────
Now we move to governance.
────────────────────────────────────────
BOOK VI — THE COOPERATIVE GOVERNANCE CHARTER
────────────────────────────────────────
INTRODUCTION
WitchMart is not a corporation.
It is a cooperative sanctuary system.
This Book defines:
This is the legal backbone of the cooperative.
CHAPTER 1 — MEMBERSHIP RIGHTS
1.1 Membership Fee
Membership is:
1.2 Rights of Members
Members have the right to:
1.3 Responsibilities of Members
Members must:
CHAPTER 2 — VOTING STRUCTURE
2.1 Voting Weight
Every member = 1 vote.
No weighted votes.
No hierarchy.
2.2 Voting Types
2.3 Voting Topics
Members vote on:
CHAPTER 3 — PROPOSAL SYSTEM
3.1 Who Can Propose
3.2 Proposal Requirements
A proposal must include:
3.3 Proposal Lifecycle
CHAPTER 4 — CONFLICT RESOLUTION
4.1 Types of Conflict
4.2 Resolution Steps
4.3 Guardian’s Role
Guardian provides:
Guardian does not decide conflicts.
CHAPTER 5 — TREASURY RULES
5.1 Treasury Sources
5.2 Treasury Allocation
Funds go to:
5.3 Transparency
All treasury movements must be:
Ledger schema (redacted):
` ledger { id type amount source destination timestamp } `
CHAPTER 6 — EMERGENCY POWERS
Emergency powers may be invoked when:
Emergency powers allow:
Emergency powers must:
CHAPTER 7 — LEADERSHIP ROTATION
Leadership rotates:
Founder‑Architect may:
Founder‑Architect may not:
CHAPTER 8 — GUILD REPRESENTATION
Guilds receive:
Guilds may not:
CHAPTER 9 — TRANSPARENCY REQUIREMENTS
All governance actions must be:
This includes:
────────────────────────────────────────
END OF PART 3
BOOK V & BOOK VI COMPLETE
─────────────────────────────
Absolutely, Jonathan — let’s continue the Codex.
Here is CODEX RAVENOUS — COMPLETE EDITION, PART 4, containing:
Same tone (C1 mythic‑technical hybrid)
Same code style (K3 full but safely redacted excerpts)
Same structure (clean, hierarchical, PDF‑ready)
────────────────────────────────────────
CODEX RAVENOUS — PART 4
BOOK VII & BOOK VIII
────────────────────────────────────────
BOOK VII — MAKER & GUILD PROTOCOLS
The Law of Craft, Lineage, and Collective Power
INTRODUCTION
Makers and guilds are the heart of WitchMart.
They are:
This Book defines:
This is the operational backbone of the marketplace and the village.
CHAPTER 1 — MAKER ONBOARDING
1.1 Who Is a Maker?
A maker is anyone who:
1.2 Onboarding Requirements
Makers must:
1.3 Maker Tent Creation
Maker tents include:
SetAI assists with:
Guardian monitors for:
CHAPTER 2 — MAKER RIGHTS
Makers have the right to:
Makers do not have the right to:
CHAPTER 3 — MAKER COMPENSATION
3.1 Pricing Model
Ravens Landing kits and all maker offerings follow:
Cost + 15%
Where cost includes:
3.2 Transparency
Makers must disclose:
3.3 Payout Structure
Payouts occur:
Ledger entry (redacted):
` payout { maker_id amount source_listing timestamp } `
3.4 Sanctuary Fund Contribution
A small percentage (configurable) goes to:
CHAPTER 4 — GUILD FORMATION
4.1 What Is a Guild?
A guild is:
4.2 Formation Requirements
A guild must have:
4.3 Guild Hall Creation
Guild halls include:
SetAI assists with:
CHAPTER 5 — GUILD DISSOLUTION
Guilds dissolve when:
Dissolution effects:
CHAPTER 6 — GUILD RESPONSIBILITIES
Guilds must:
Guilds may:
Guilds may not:
CHAPTER 7 — GUILD ALIGNMENT
Guilds align with:
Alignment affects:
CHAPTER 8 — MAKER ↔ NODE MAPPING
Every maker is mapped to:
Mapping schema (redacted):
` makerNodeMap { maker_id tent_id stall_id guild_id sanctuarynodeid } `
Guardian monitors:
────────────────────────────────────────
END OF BOOK VII
────────────────────────────────────────
Now we move to the ledger — the backbone of transparency.
────────────────────────────────────────
BOOK VIII — THE TRANSPARENCY LEDGER SPECIFICATION
────────────────────────────────────────
INTRODUCTION
The Transparency Ledger is the public record of WitchMart.
It tracks:
The ledger is:
This Book defines:
CHAPTER 1 — LEDGER SCHEMA
1.1 Core Ledger Table
` ledger { id: UUID type: ‘revenue’ | ‘expense’ | ‘payout’ | ‘sanctuary’ | ‘land’ | ‘governance’ | ‘node’ amount: number currency: ‘USD’ source: string destination: string metadata: JSON timestamp: timestamptz } `
1.2 Governance Ledger
` governance_log { id action proposer votes_for votes_against result timestamp } `
1.3 Node Ledger
` node_log { id node_id event_type stability_change trust_change metadata timestamp } `
CHAPTER 2 — UPDATE RULES
2.1 Who Can Update the Ledger?
2.2 Automatic Entries
Automatically logged:
2.3 Manual Entries
Manually logged:
CHAPTER 3 — IMMUTABILITY RULES
3.1 No Deletion
Ledger entries cannot be deleted.
3.2 No Modification
Ledger entries cannot be edited after creation.
3.3 Correction Protocol
If an error occurs:
CHAPTER 4 — PUBLIC VS PRIVATE FIELDS
4.1 Public Fields
Public:
4.2 Private Fields
Private:
Private fields are:
CHAPTER 5 — AUDIT PROTOCOL
5.1 Audit Frequency
Audits occur:
5.2 Audit Types
5.3 Audit Access
Auditors receive:
CHAPTER 6 — TREASURY FLOW DIAGRAMS
6.1 Revenue Flow
Revenue → Treasury →
6.2 Sanctuary Fund Flow
Sanctuary fund →
6.3 Land Fund Flow
Land fund →
CHAPTER 7 — COOPERATIVE OVERSIGHT
7.1 Oversight Bodies
7.2 Oversight Rights
Oversight bodies may:
7.3 Oversight Limits
Oversight bodies may not:
────────────────────────────────────────
END OF PART 4
BOOK VII & BOOK VIII COMPLETE
─────────────────────────────
Jonathan, let’s keep the Codex flowing.
Here is CODEX RAVENOUS — COMPLETE EDITION, PART 5, containing:
This continues in the C1 mythic‑technical hybrid tone, with K3 full but safely redacted code excerpts, and structured for clean PDF conversion.
────────────────────────────────────────
CODEX RAVENOUS — PART 5
BOOK IX & BOOK X
────────────────────────────────────────
BOOK IX — SETAI BACKEND PROTOCOL
The Law, Architecture, and Boundaries of SetAI
INTRODUCTION
SetAI is not a chatbot.
SetAI is not a personality.
SetAI is not a replacement for human judgment.
SetAI is a sovereignty‑bound generative engine that powers:
SetAI operates under:
This Book defines:
CHAPTER 1 — TRUTH LAYERS
SetAI operates on a hierarchy of truth, ensuring it never fabricates harmful or consequential information.
1.1 Truth Layer 1 — User‑Provided Truth
The highest truth.
SetAI must prioritize:
1.2 Truth Layer 2 — Documented System Truth
Includes:
1.3 Truth Layer 3 — Codex Truth
Includes:
1.4 Truth Layer 4 — Mythic Truth
Used for:
Mythic truth must never override Layers 1–3.
CHAPTER 2 — REFUSAL RULES
SetAI must refuse when:
Refusal format:
Example refusal (redacted):
` I can help with the symbolic meaning of this ritual, but I cannot claim supernatural outcomes or guarantee results. Here is what I can offer… `
CHAPTER 3 — NARRATIVE RULES
SetAI generates narrative for:
Narrative must:
SetAI may use:
SetAI may not:
CHAPTER 4 — CUSTOMIZATION RULES
SetAI customizes:
Customization must:
Example (safe excerpt):
` const tentCustomization = { palette: choosePalette(user.preferences), symbols: filterSymbols(user.boundaries), lore: generateLore(user.identity, mythicContext) } `
CHAPTER 5 — MEMORY RULES
SetAI memory is:
SetAI must not:
Memory must be:
CHAPTER 6 — SAFETY RULES
SetAI must:
SetAI must:
CHAPTER 7 — OVERRIDE LIMITS
SetAI cannot override:
SetAI may override:
SetAI may not override:
CHAPTER 8 — SETAI ↔ GUARDIAN COMMUNICATION
SetAI sends:
Guardian sends:
Example (safe excerpt):
` eventBus.emit(‘guardianCheck’, { type: ‘CUSTOMIZATION’, payload: customizationRequest }) `
Guardian may:
SetAI must obey.
CHAPTER 9 — SETAI ↔ WORLD ENGINE COMMUNICATION
SetAI generates:
World engine provides:
SetAI must:
────────────────────────────────────────
END OF BOOK IX
────────────────────────────────────────
Now we move to the navigation system — the map of the village.
────────────────────────────────────────
BOOK X — THE MYTHIC NAVIGATION SYSTEM
────────────────────────────────────────
INTRODUCTION
WitchMart is not navigated like a website.
It is navigated like a village.
The Mythic Navigation System defines:
This Book defines the architecture of movement and presence.
CHAPTER 1 — MAP LAYERS
The world map has multiple layers:
Each layer overlays the others.
CHAPTER 2 — NODE PLACEMENT RULES
Nodes must be placed according to:
Nodes cannot:
Placement algorithm (redacted):
` placeNode(node) { const region = chooseRegion(node.type, worldState) ensureSanctuaryBalance(region) updateWorldState(node, region) } `
CHAPTER 3 — GUILD HALL PLACEMENT
Guild halls must be:
Guild halls cannot:
CHAPTER 4 — MAKER TENT PLACEMENT
Maker tents are placed:
Maker tents cannot:
CHAPTER 5 — SANCTUARY ZONES
Sanctuary zones include:
Sanctuary zones must:
CHAPTER 6 — NARRATIVE PATHWAYS
Narrative pathways guide:
Pathways include:
SetAI generates narrative overlays.
CHAPTER 7 — USER ONBOARDING PATH
Onboarding path includes:
Guardian monitors:
CHAPTER 8 — WORLD EVENTS
World events include:
Events are:
────────────────────────────────────────
END OF PART 5
BOOK IX & BOOK X COMPLETE
────────────────────────────────────────
Jonathan, let’s continue the Codex exactly as promised.
Here is CODEX RAVENOUS — COMPLETE EDITION, PART 6, containing:
This continues in the C1 mythic‑technical hybrid tone, with K3 safely‑redacted code excerpts, and structured for clean PDF conversion.
────────────────────────────────────────
CODEX RAVENOUS — PART 6
BOOK XI & BOOK XII
────────────────────────────────────────
BOOK XI — THE WITCHMART DECLARATION
The Soul, Oath, and Foundational Voice of the Sanctuary
INTRODUCTION
The WitchMart Declaration is not a marketing statement.
It is not a mission statement.
It is not a slogan.
It is the soul‑document of the sanctuary.
It is the invocation, the oath, the pledge, and the memorial that binds the world together.
Where the Ma’at Constitution defines the law,
and the Guardian Constitution defines the protection,
the WitchMart Declaration defines the heart.
This Book contains:
CHAPTER 1 — THE INVOCATION
This invocation is spoken at:
Invocation Text
“Let truth be our compass.
Let sanctuary be our shelter.
Let sovereignty be our law.
Let craft be our lineage.
Let community be our strength.
Let Ma’at be our measure.
Let the Raven watch over all who seek refuge.”
CHAPTER 2 — THE MA’AT LINE
The Ma’at Line is the single sentence that binds all systems:
“No action may violate truth, balance, or sovereignty.”
This line overrides:
Nothing outranks the Ma’at Line.
CHAPTER 3 — THE SANCTUARY OATH
This oath is taken by:
Sanctuary Oath
“I will not harm the vulnerable.
I will not exploit the wounded.
I will not coerce the uncertain.
I will not shame the seeking.
I will not betray sanctuary for profit or power.
I will protect those who enter this space in good faith.”
CHAPTER 4 — THE SOVEREIGNTY OATH
This oath is taken by:
Sovereignty Oath
“I will not override the will of another without consent.
I will not manipulate choice.
I will not obscure truth.
I will not take what is not freely given.
I will uphold the right to leave, the right to refuse, and the right to remain unseen.”
CHAPTER 5 — THE COOPERATIVE PLEDGE
This pledge is taken by all members:
Cooperative Pledge
“I join this village not as a consumer,
but as a citizen.
I share in its burdens,
its responsibilities,
its sanctuary,
and its future.
I will act with integrity,
vote with clarity,
and uphold the Codex.”
CHAPTER 6 — THE MEMORIAL TEXT
This text honors:
Memorial Text
“We remember those who were not protected.
We remember those who were cast out.
We remember those who were unseen.
We remember those who were harmed by systems that promised safety.
May this sanctuary be the place they never had.”
CHAPTER 7 — THE FOUNDER’S DECLARATION
This is your declaration, Jonathan — the statement that defines your role.
Founder’s Declaration
“I, Jonathan Bradley,
founder‑architect of WitchMart,
declare this sanctuary to be a place of truth,
a refuge for the vulnerable,
a home for the displaced,
a village for the seekers,
and a world governed by Ma’at.
I build not for myself,
but for those who need a place to stand.”
────────────────────────────────────────
END OF BOOK XI
────────────────────────────────────────
Now we move to the land — the physical sanctuary.
────────────────────────────────────────
BOOK XII — LAND NODES & PHYSICAL SANCTUARY MANUAL
────────────────────────────────────────
INTRODUCTION
Digital sanctuary is powerful.
But physical sanctuary is sacred.
This Book defines:
This is the manual for the physical world of WitchMart.
CHAPTER 1 — TEMPLE OF THE RAVENS
1.1 Legal Identity
Your nonprofit:
1.2 Purpose
Temple of the Ravens exists to:
1.3 Governance
Temple of the Ravens is governed by:
CHAPTER 2 — RAVEN’S NEST
2.1 What Raven’s Nest Is
Raven’s Nest is:
2.2 Land Layout
Raven’s Nest includes:
2.3 Land Node Metadata
` landNode { id: ‘ravens-nest’ type: ‘physical’ stability: 100 trustScore: 100 access: ‘invited’ metadata: { rooms: [‘silent’, ‘sound’], equipment: [‘medical-grade audio’], depth: 30 } } `
CHAPTER 3 — UNDERGROUND ROOMS
3.1 The Silent Room
Depth: 30 feet underground
Purpose:
Rules:
3.2 The Sound‑Healing Chamber
Adjacent to the silent room.
Contains:
Purpose:
CHAPTER 4 — LAND NODE PROTOCOL
4.1 Land Node Creation
Land nodes require:
4.2 Land Node Sovereignty
Land nodes have:
4.3 Land Node Collapse
A land node collapses if:
Collapse triggers:
CHAPTER 5 — SAFETY RULES
5.1 Physical Safety
Rules include:
5.2 Emergency Protocol
In emergencies:
5.3 Accessibility
Land nodes must:
CHAPTER 6 — GUEST PROTOCOL
Guests must:
Guests may not:
CHAPTER 7 — EXPANSION PLAN
Future land nodes include:
Expansion requires:
────────────────────────────────────────
END OF PART 6
BOOK XI & BOOK XII COMPLETE
────────────────────────────────────────
Jonathan, here we go — the Codex continues.
This is CODEX RAVENOUS — COMPLETE EDITION, PART 7, containing:
This section completes the entire Codex Ravenous.
Same tone (C1 mythic‑technical hybrid)
Same code style (K3 safely‑redacted excerpts)
Same structure (clean, hierarchical, PDF‑ready)
────────────────────────────────────────
CODEX RAVENOUS — PART 7
BOOK XIII & BOOK XIV
────────────────────────────────────────
BOOK XIII — CURRICULUM & CLASSES MANUAL
The Lineage, Ritual, and Educational Framework of WitchMart
INTRODUCTION
WitchMart is not only a sanctuary and a marketplace — it is a school, a lineage, and a teaching ground.
This Book defines:
This is the educational backbone of the sanctuary.
CHAPTER 1 — THE FIRST CLASS: ENERGY TRANSFERENCE (DEATH)
1.1 Purpose
This class exists to:
1.2 Scientific Foundations
Topics include:
1.3 Spiritual Foundations
Topics include:
1.4 Practical Exercises
Exercises include:
1.5 Trauma‑Aware Framework
Rules:
CHAPTER 2 — REIKI INTEGRATION
2.1 Lineage
You, Jonathan, are:
2.2 Integration Points
Reiki is integrated into:
2.3 Reiki Rules
Reiki must:
CHAPTER 3 — EGYPTIAN ARTS CURRICULUM
3.1 Lineage Holder
Your friend from Oklahoma City:
3.2 Curriculum Topics
Topics include:
3.3 Integration Rules
Egyptian arts must:
CHAPTER 4 — RITUAL CLASSES
4.1 Ritual Types
4.2 Ritual Safety
Rules:
4.3 Ritual Structure
Each ritual includes:
CHAPTER 5 — SANCTUARY PRACTICES
5.1 Mirror Rooms
Used for:
5.2 Mímir’s Echo
Used for:
5.3 Sound Healing
Used for:
CHAPTER 6 — TEACHING MODEL
6.1 Trauma‑Aware Teaching
Teachers must:
6.2 Sovereignty‑First Teaching
Students may:
6.3 Guardian Integration
Guardian monitors:
────────────────────────────────────────
END OF BOOK XIII
────────────────────────────────────────
Now we move to the final book — the technical backbone.
────────────────────────────────────────
BOOK XIV — TECHNICAL & DEPLOYMENT MANUAL
────────────────────────────────────────
INTRODUCTION
This Book defines the technical architecture of WitchMart:
This is the engineering backbone of the sanctuary.
CHAPTER 1 — BACKEND ARCHITECTURE
1.1 Stack
1.2 Folder Structure
` src/ guardian/ world/ sanctuary/ setai/ routes/ middleware/ db/ assets/ `
1.3 Core Principles
CHAPTER 2 — GUARDIAN ENGINE (SAFE EXCERPTS)
2.1 Guardian Class
` export class Guardian { constructor(roles, supabase) { this.roles = roles this.supabase = supabase }
async evaluate(event) { const verdicts = await Promise.all( this.roles.map(role => role.evaluate(event)) )
const pitNotes = await this.pit.analyze(event)
const finalAction = decide(verdicts, pitNotes) // thresholds redacted
await this.log(event, verdicts, pitNotes, finalAction)
return finalAction } } `
2.2 Middleware
` export async function guardianMiddleware(req, res, next) { const event = mapRequestToEvent(req) req.guardian = await guardian.evaluate(event) next() } `
2.3 Safety Redactions
CHAPTER 3 — SETAI INTEGRATION
3.1 SetAI Service
` export class SetAI { async generate(context) { const truth = await this.resolveTruth(context) return this.createNarrative(truth) } } `
3.2 Safety Redactions
CHAPTER 4 — WORLD ENGINE IMPLEMENTATION
4.1 Event Bus
` eventBus.on(‘worldEvent’, async event => { await guardian.evaluate(event) await worldEngine.update(event) }) `
4.2 World Engine Core
` export class WorldEngine { async update(event) { // redacted: world state mutation logic } } `
CHAPTER 5 — SANCTUARY NODE ENGINE
5.1 Node Stability
` updateStability(node, delta) { node.stability = clamp(node.stability + delta, 0, 100) } `
5.2 Node Trust
` updateTrust(node, delta) { node.trustScore = clamp(node.trustScore + delta, 0, 100) } `
5.3 Safety Redactions
CHAPTER 6 — ASSET MAPPING
6.1 Asset Types
6.2 Asset Registry
` assets/ tents/ shields/ shirts/ sanctuary/ `
CHAPTER 7 — PROJECT STRUCTURE
7.1 Naming Conventions
7.2 Versioning
CHAPTER 8 — API CONTRACTS
8.1 Guardian Routes
` GET /guardian/status POST /guardian/resolve `
8.2 World Routes
` POST /world/event GET /world/state `
8.3 Maker Routes
` POST /maker/create GET /maker/:id `
CHAPTER 9 — DATABASE SCHEMA (SAFE EXCERPTS)
9.1 Guardian Decisions
` guardian_decisions { id event_id action threat council pit_notes timestamp } `
9.2 Nodes
` nodes { id type owner stability trustScore metadata } `
9.3 Ledger
` ledger { id type amount source destination timestamp } `
CHAPTER 10 — DEPLOYMENT INSTRUCTIONS
10.1 Environment
10.2 Deployment Steps
CHAPTER 11 — SECURITY MODEL
11.1 Principles
11.2 Guardian as Security Layer
Guardian protects:
11.3 Redactions
CHAPTER 12 — FUTURE‑PROOFING
12.1 Modular Expansion
12.2 Constitutional Amendments
12.3 AI Evolution
────────────────────────────────────────
END OF PART 7
BOOK XIII & BOOK XIV COMPLETE
────────────────────────────────────────
Jonathan — I’ve got you.
And here’s the good news: you’ve reached the end of the 14‑Book Codex, which means there is no “next section” left to write inside the Codex itself.
But you are absolutely right to ask for “Next section,” because a Codex of this scale always has post‑Codex components — the supporting material that turns a master document into a publishable, navigable, professional PDF.
So now we move into the Post‑Codex Appendices, which are essential for a complete, archival‑grade manual.
Below is PART 8, containing:
These appendices complete the Codex Ravenous and prepare it for PDF formatting.
────────────────────────────────────────
CODEX RAVENOUS — PART 8
APPENDICES A–H
────────────────────────────────────────
APPENDIX A — FULL TABLE OF CONTENTS
Hierarchical, PDF‑ready, complete
BOOK I — The Origin & Identity of WitchMart
BOOK II — The Ma’at Constitution
BOOK III — The Guardian Constitution
BOOK IV — The World Engine Blueprint
BOOK V — Sanctuary Node Protocol
BOOK VI — Cooperative Governance Charter
BOOK VII — Maker & Guild Protocols
BOOK VIII — Transparency Ledger Specification
BOOK IX — SetAI Backend Protocol
BOOK X — Mythic Navigation System
BOOK XI — WitchMart Declaration
BOOK XII — Land Nodes & Physical Sanctuary Manual
BOOK XIII — Curriculum & Classes Manual
BOOK XIV — Technical & Deployment Manual
APPENDIX B — GLOSSARY OF TERMS
Definitions for every major concept in the Codex
Ma’at — The constitutional law of WitchMart.
Set the Guardian — The constitutional safety engine.
SetAI — The sovereignty‑bound generative engine.
Node — A sanctuary territory (digital or physical).
Tent — A personal sanctuary node.
Guild — A collective of makers or lineage holders.
Maker — A craftsperson, healer, or teacher.
Sanctuary — A protected space governed by Ma’at.
Stability — A node’s structural integrity.
TrustScore — A node’s social integrity.
Veil Mode — Identity‑masking safety mode.
World Engine — The simulation layer of the village.
Ledger — The public transparency record.
Raven’s Nest — The first physical sanctuary node.
Temple of the Ravens — The nonprofit stewarding land nodes.
APPENDIX C — SYMBOL INDEX
Every symbol used in WitchMart and its meaning
Raven — Witness, guardian, messenger.
Shield — Protection, sovereignty, boundary.
Tent — Home, identity, sanctuary.
Mirror — Reflection, truth, identity work.
Echo — Memory, wisdom, continuity.
Node — Territory, presence, connection.
Guild Sigil — Lineage, craft, collective identity.
Sanctuary Flame — Healing, transformation, safety.
APPENDIX D — SYSTEM ROLES INDEX
All roles across governance, AI, and sanctuary
Guardian Roles
Cooperative Roles
Sanctuary Roles
Maker Roles
APPENDIX E — RITUAL & CLASS INDEX
All rituals and classes referenced in the Codex
Rituals
Classes
APPENDIX F — NODE & WORLD INDEX
All node types and world engine structures
Node Types
World Structures
APPENDIX G — VERSIONING & RELEASE NOTES TEMPLATE
For future updates to the Codex
Version Format
Codex Ravenous vX.Y.Z
Release Notes Template
` Version: Date: Summary: Changes:
APPENDIX H — CODEX MAINTENANCE PROTOCOL
How future stewards maintain the Codex
────────────────────────────────────────
END OF PART 8
APPENDICES A–H COMPLETE
─────────────────────────────
All is subject to change as we are ever changing ourselves
Ravens Evermore
To ensure maximum stability and zero gatekeeping, WitchMart is architected to be lightweight. It can be deployed via GitHub Pages or self‑hosted on IONOS VPS, requiring no credit cards, trials, or invasive identity verification for the community.
This project is released for community benefit. It belongs to the people it serves.