Home / Engine / Craft Knowledge

Craft Knowledge Engine - plan (v1, 2026-06-20)

Updated Jun 20, 2026 · Affirmology_CraftKnowledgeEngine_Plan_v1.md

Craft Knowledge Engine - plan (v1, 2026-06-20)

Jeff's catch: does the system actually USE our techniques/neuroscience/frequency/audio knowledge to conduct better transformational audios, or is it just a "Chiron situation"? Honest answer: mostly the latter. This is the second pillar, and tonight's upgrade.

The gap (verified in code)

The cosmic blueprint got the full treatment (engine, corpus, oracles, nightly growth, timeline). The CRAFT side did not: - Technique knowledge reaches the agents only SHALLOWLY: a STATIC TECHNIQUES_LIBRARY menu hardcoded in affirmology-agent/src/affirmology/agents/build_report.py. Chiron selects from it; the build report names what was used. That is the whole pipeline. - The deep craft research sits in ~10 documents and is NOT distilled into actionable methods the agents apply, and NOT growing. - The audio mix does NO frequency / binaural / solfeggio / tonal work, just a music bed. So: "Chiron + a static list," not a deep, growing, agent-utilized craft engine.

The raw material we already have (a head start, not a cold start)

In the workspace: Affirmology_TechniquesLibrary_v1.md, Affirmology_Neuroscience_AudioEfficacy_Research_v1.md, Affirmology_PredictiveBrain_IdentityChange_Research_v1.md, Affirmology_AudioMastering_Production_Research_v1.md, Affirmology_DepthPsychology_JungianIntegration_Research_v1.md, the use-case research (CrisisJourney, DeepDive_PilgrimFormat, GroupAudio, PlantMedicineJourney, TeachingAudio_TransitAware), and Affirmology_ReadingCraft_Standard_v1.md. Distill these, do not start from scratch.

The model: a second knowledge pillar

Cosmic blueprint = WHAT we say (the chart). Craft engine = HOW we say it and make it land in the body. It mirrors the blueprint architecture: a knowledge base + actionable distillation + agent wiring + nightly growth.

What to build

1. CRAFT KNOWLEDGE BASE: a new "craft" tradition in the corpus + meaning/distinctions store, with ACTIONABLE entries (each: the method, WHY it works, WHEN to use it, HOW to apply it) across five areas: - NEUROSCIENCE of transformation (the predictive brain, identity change, suggestibility, the hypnagogic window, repetition and emotional encoding). - FREQUENCY & SOUND (binaural beats, solfeggio, isochronic tones, tonal beds, what each does and when to use it). - AUDIO PRODUCTION / MASTERING (the sound of a premium transformational audio: voice anchoring, the bed mix, loudness, space). - MEDITATION / HYPNOSIS / GUIDED-AUDIO TECHNIQUE (induction, deepening, suggestion, integration, pacing, the openings/endings craft, letting recognitions land). - READING CRAFT (how pro astrologers conduct a reading; the ReadingCraft standard extended).
2. SEED IT from the research docs above (a one-time distillation pass), then grow.
3. WIRE IT DEEPLY into the agents (ownership corrected per Jeff 2026-06-20; NOT Chiron as primary): - HYPNOS is the PRIMARY owner: the subconscious-efficacy craft is his domain (induction, the hypnagogic window, suggestibility, meditation and hypnosis technique, AND brainwave entrainment / binaural / frequency, since that is literally how sound reaches the subconscious). He selects and sequences the techniques from the live craft base, replacing the static menu in build_report.py. - THE NEUROSCIENTIST owns the neuroscience knowledge (the predictive brain, identity change, why it works), pairing with Hypnos. (Modern-wisdom figure from the council roster.) - ORPHEUS owns the WRITING craft (cadence, the openings and endings, letting recognitions land, the poetry). - APOLLO CHECKS the craft/efficacy gate (his job: is the induction sound, does it use the hypnagogic window, is the cadence right, does it actually land). The gate references the craft base. - CHIRON is involved only for the HEALING-technique slice (working the wound, somatic healing), not the whole craft. (This is the "some of it is healing" part Jeff named.) - ECHO feeds the loop: what is landing vs not (feedback) flows back to grow the craft base. - HERMES gets a search_craft tool so chat readings and the chatbot can use it too.
4. NIGHTLY GROWTH (extend the cron's mandate): the growth engine grows the craft tradition too, crawling WIDE (neuroscience and audio-efficacy research, pro astrologer reading method, meditation and hypnosis technique, sound and frequency science), distilling into actionable entries, and folding in every "this didn't land" correction. Look wide and far, be smart.
5. FREQUENCY / SOUND PRODUCTION CAPABILITY (optional, the one piece that changes the actual SOUND): binaural / solfeggio / isochronic / tonal overlays in audio_mix.py, informed by the frequency knowledge, structure-aware (delta for sleep, theta for journey, etc.). Future build; the knowledge base sets it up. The LOCKED DEMO stays untouched; this is Studio-only until proven.

Sequence

Phase 1: the craft tradition + seed it from the research docs (fast, big value). Phase 2: wire into Chiron/Orpheus/Apollo/Hermes (replace the static menu). Phase 3: extend the nightly crawler to grow it. Phase 4 (later, separate): the frequency/sound production capability in the mix.

Guardrails

Brand rules hold (no em dashes, never name the meditation teacher, etc.). Tier-wall any copyrighted source. The locked demo is untouched. Cost discipline on the nightly distillation (caps, cheapest good model).