Magical Servitor Creation: Complete Lifecycle Protocol — Design, Birth, Service, Dissolution

Phase 1: Design Specification — The Blueprint

A servitor without a written specification is a hallucination. The specification document is your contract with the construct, it defines what it is, what it does, how it lives, and how it dies. Every field below is mandatory. If you cannot fill a field, the servitor is not ready for birth.

The Servitor Specification Document (One Page, Mandatory)

Dual Sigil Generation (Mandatory)

1. Identity Sigil: From "NAME + PURPOSE" via Chaos Sigil Generator. Anchors the servitor's existence.
2. Command Sigil: From mandate sentence via Spare method (remove vowels, dedupe consonants, abstract glyph). Anchors the specific intent.
3. Linking: Place both on charging plate. Visualize connection line. Charge together.

Housing (The Servitor's Address)

• Physical: Small box, jar, or dedicated altar tile. Sigil visible. Kept in fixed location.
• Digital: Encrypted folder with: sigil PNG/SVG, mandate.txt, feeding_log.csv, health_log.csv, spec.pdf.
• Rule: Housing never moves without formal relocation ritual. Housing = address. No address = no delivery.

Feeding & Health Metrics Definition

Health Metrics Dashboard

• Primary KPI: Mandate progress % (0-100)
• Energy Level: Subjective 1-10, post-feed
• Anomaly Count: Unintended effects/week
• Dream Reports: Ally/Tool/Neutral/Threat ratio
• PSI GYM Correlation: Hit rate vs. servitor activity

Phase 2: Birth — Charging & Activation

Birth is the moment the specification becomes a live construct. It requires gnosis (altered state), dual-sigil charging, verbal declaration, and sealing. Do not rush, failed birth = stillborn servitor that drains without output.

Pre-Birth Checklist

• [ ] Spec document complete & printed
• [ ] Dual sigils generated, printed, on charging plate
• [ ] Housing ready (physical + digital)
• [ ] Feeding schedule in calendar (recurring events)
• [ ] Health dashboard created (spreadsheet/app)
• [ ] Emergency off-switch memorized

Charging Protocol (20 Minutes)

Post-Birth Verification (Days 1-7)

Phase 3: Service — Feeding, Monitoring, Maintenance

Service is the working life of the servitor. It runs on the feeding schedule you defined. Missed feeds = parameter drift. 3 missed feeds = mandatory review. The servitor has no autonomy to request food, you are the operator.

Daily Feed (5 Minutes) — Attention

1. Open housing / digital folder
2. Read mandate aloud
3. Log one action taken toward mandate today
4. Rate subjective energy (1-10)
5. Note anomalies (unintended effects, synchronicities, blocks)

Weekly Feed (15 Minutes) — Energy

1. Gnosis induction: 4-7-8 breath ×3, anchor phrase
2. Sigil gaze: 5 min on identity + command sigils
3. Mandate restatement aloud
4. Review weekly metrics: mandate progress %, anomaly count, dream log summary
5. Adjust parameters if progress stalled 2+ weeks

Monthly Feed (30 Minutes) — Data + Deep Charge

1. Full metrics dump: export all trackers (income, traffic, health, etc.)
2. Feed data to servitor: visualize metrics flowing into housing
3. Deep charge: 15 min gnosis (exhaustion/trance/sexual/fear) + both sigils
4. Monthly audit: Progress %, Anomaly trend, Dream pattern, PSI GYM correlation
5. Decision: Continue / Re-parameter / Re-charge / Terminate

Health Monitoring Dashboard

Track in spreadsheet with these columns:

Parameter Adjustment Protocol

If mandate progress stalls 2+ weeks:

1. Run Clarifier: Is mandate still aligned? (Use tarot Clarifier spread)
2. Check feeding compliance: Any missed feeds?
3. Check PSI GYM: Is hit rate dropping? (Channel noise)
4. Check dreams: Threat/neutral = drift. Ally/tool = functioning.
5. Adjust ONE parameter at a time. Log change. Monitor 1 week.

Phase 4: Dissolution — Safe Termination & Emergency Banishment

Every servitor must end. A servitor without an end is a parasite. The off-switch is not optional, it's the most important part of the design.

Standard Termination (Mandate Fulfilled / Time Expired / Condition Met)

1. Formal Revocation: Stand at housing. Aloud: "I, [YOUR NAME], revoke [SERVITOR NAME]. Your mandate is complete. Return to source. You are released."
2. Sigil Destruction: Burn physical sigils completely. Ash to running water or crossroads. Digital: secure delete (7-pass overwrite) or encrypt + lose key.
3. Energy Return: Stand. Visualize servitor's energy as light returning to your solar plexus. Do not keep, return to your central channel.
4. Banish: LBRP, Star Ruby, Gnostic Pentagram, or your tradition's equivalent.
5. Ground: Salt bath or shower (visualize draining). Drink 500ml water + pinch salt. Eat protein. Sleep 8h minimum.
6. Journal: Log: Termination date, final mandate %, total days active, total feeds, anomalies resolved, lessons learned.

Emergency Termination (Rogue / Parasitic / Drift / Unintended Harm)

Triggers — IMMEDIATE ACTION REQUIRED:

• Servitor acts outside parameters (unauthorized actions)
• Energy drain >15% daily baseline (chronic fatigue, headaches, insomnia)
• Dream reports: Threat / Attack / Parasitic (feeding on you)
• Unintended consequences manifesting (harm to others, financial loss, relationship damage)
• Parameter drift: Servitor redefines its own mandate
• PSI GYM hit rate crashes + servitor active = channel hijack

Post-Termination Quarantine (72 Hours)

• No magical work. No servitor creation. No charging.
• Monitor: Energy levels, sleep quality, dream content, physical symptoms.
• If symptoms persist >7 days: seek experienced practitioner / medical eval.

Failure Modes: Diagnosis & Correction at Each Phase

Advanced: Compound Servitors, Egregore Seeding & Codex Chaoticus

Compound Servitors (2-3 Archetypes)

For objectives requiring multiple functions that must coordinate.

• Magician + Chariot: Manifestation + timeline defense. "Build the asset AND protect the deadline."
• High Priestess + Hermit: Intuition + deep research. "Find the variable I cannot see."
• Empress + Temperance: Growth + calibration. "Scale without breaking."
• Death + Star: End + guide. "Clean transition to next phase."
• Devil + Tower: Shadow exposure + demolition. "Burn the false structure."

Protocol: Create each as separate servitor with own spec, sigils, housing. Shared mandate clause: "Coordinates with [Other Name]." Shared feeding calendar. You are the coordination layer, they do not communicate directly.

Egregore Seeding (From Servitor to Group Entity)

A servitor can become an egregore if:

1. Mandate expands to collective benefit
2. Multiple operators adopt it (shared off-switch = consensus required)
3. Feeding becomes group ritual
4. Housing becomes shared space (physical or digital)

Codex Chaoticus details the full seeding protocol: consensus governance, feeding rotation, schism protocols, and dissolution by unanimous vote.

Codex Chaoticus — The Complete Servitor System

The Codex Chaoticus PDF contains the full advanced curriculum:

• Servitor Taxonomy: 12 classes (Sentinel, Weaver, Courier, Architect, etc.) with templates
• Charging Variants: Planetary hour charging, elemental charging, group charging, remote charging
• Communication Protocols: Dream protocol, automatic writing, pendulum, Zener-card signaling, app-based logging
• Diagnostic Suite: Health scan, parameter audit, drift detection, parasite scan, energy audit
• Warfare Protocols: Servitor vs. servitor, servitor vs. parasite, banishment under fire, counter-measures
• Egregore Engineering: Seeding, governance, feeding economies, schism resolution, dissolution
• Integration: PSI GYM calibration, Chaos Sigil Generator automation, Astral Lab planetary timing