sancovp

[0] the enterprise integration patterns library — every skill a certified region of the KB; call number = home : facets

[0.1] the core subdomain of enterprise integration patterns (11 concepts)

[0.1.6] A connection point that joins two channel segments or a channel to an external system, enabling message flow a

[0.1.1] A metadata field indicating the urgency or precedence level of a command message, used by schedulers and route

[0.1.2] The logical or physical destination endpoint to which a command message is addressed, specifying which receive

[0.1.3] The maximum duration a sender will wait for a command to complete before considering it failed; exceeding this

[0.1.4] A data envelope containing error details returned when an operation fails, typically including fault code, des

[0.1.5] A data envelope containing the return value or outcome produced by a successfully executed operation, structur

[0] the the grand argument (draft kernel v0) library — every skill a certified region of the KB; call number = home : facets

[0.1] the core subdomain of the grand argument (draft kernel v0) (117 concepts)

[0.1.3] The deployment strategy where the treasure sentence ships at depth 1 and every nightly post publicly instantia

[0.1.4] The prospect's journey of discovery through the system; the active navigation that completes the dare

[0.1.5] The earliest closed alpha deployments where initial users prove the transfer premise by operating without tech

[0.1.2] The operadic_train methodology connecting Roger template to Hormozi framework for mapping the reveal before co

[0.1.1] The mechanism by which the system transfers through successive operators who each leave it for the next person

[0.1.6] A scene that functions as proof; the GAS instantiation of a premise that carries its own evidence attached to

[0] the sourdough baking library — every skill a certified region of the KB; call number = home : facets

[0.1] the core subdomain of sourdough baking (8 concepts)

[0.1.3] Dusting the interior of a proofing basket with flour before placing shaped dough, preventing sticking and crea

[0.1.4] The physical feel and structural quality of bread's interior ranging from fine and tender to coarse and chewy

[0.1.2] The brown coloration of bread's outer layer produced by Maillard reaction and caramelization during baking, ra

[0.1.5] Techniques for manipulating dough during shaping including stretching, folding, and rolling that develop glute

[0.1.1] The depth and nuance of sourdough taste arising from multiple organic acids, esters, and alcohols produced dur

[0.1.6] Combining flour, water, and other ingredients to form a cohesive dough, developing initial gluten structure th

Use the restaurants neurosymbolic module: RAG library, agent brain, growable KB — proof-checked

[0.1.1] Appropriate for children and families

[0.1.2] Ambiance suitable for date night

[0.1.3] System handles parties fairly when busy

[0.1.4] Friendly host acknowledgment upon arrival

[0.1.5] Same dishes taste same across different visits

[0.1.6] Staff places guests at appropriate table based on party size and preferences

[0.1] the customer_experience subdomain of restaurants (105 concepts)

[0.1.1] The depth and nuance of sourdough taste arising from multiple organic acids, esters, and alcohols produced dur

[0.1.2] The physical feel and structural quality of bread's interior ranging from fine and tender to coarse and chewy

[0.1.3] The brown coloration of bread's outer layer produced by Maillard reaction and caramelization during baking, ra

[0.1.4] Dusting the interior of a proofing basket with flour before placing shaped dough, preventing sticking and crea

[0.1.5] Techniques for manipulating dough during shaping including stretching, folding, and rolling that develop glute

[0.1.6] The extent of sourdough fermentation progression, encompassing duration and metabolic development, where exten

[0.1] the core subdomain of sourdough baking (10 concepts)

[0.2.1] The visual shade of the bread interior ranging from pale ivory to deep golden depending on fermentation length

[0.1.1] A relation between atomic operations in memory models where a release fence on one thread synchronizes with an

[0.1.2] C11/C++11 memory ordering that only guarantees atomicity of the operation with no ordering constraints relativ

[0.1.3] The strongest memory ordering requiring a single total order of all sequentially consistent operations visible

[0.1.4] Memory ordering semantics ensuring all subsequent loads/stores cannot be reordered before the acquire operatio

[0.1.5] A fundamental ordering relation in memory models defining that if operation A happens-before operation B, then

[0.1.6] Standard C11 specification defining memory orderings: memory_order_relaxed, memory_order_consume, memory_order

[0.2.1] Compare-and-swap operation atomically loading a value, comparing it to an expected value, and storing a new va

[0.2.2] A synchronization operation or primitive that establishes an inter-thread happens-before relationship, ensurin

WHEN building any customer-facing content, funnel, page, email, call script, or offer structure THEN apply the AIDA fractal at every scale — each value ladder stage has its own AIDA cycle, each piece of content has AIDA within AIDA, and the customer journey…

WHAT: Dan Kennedy's framework for ascending customers through the value ladder — retention through progression WHEN: When applying direct marketing ascension knowledge

WHAT: Dan Kennedy's adaptation of Dale Carnegie's "make them feel important" for direct marketing WHEN: When applying direct marketing carnegie secret knowledge

WHAT: Dan Kennedy's Direct Marketing Diet — 6-step framework for direct marketing success WHEN: When applying direct marketing diet knowledge

WHAT: Craig Proctor's 8 Breakthrough Strategies for direct marketing success WHEN: When applying direct marketing eight breakthroughs knowledge

WHAT: Dan Kennedy's Follow-Up Framework — the 4-step structured follow-up campaign, closed loop systems, and the "no-fail" follow-up strategy. From No B.S. Direct Marketing. WHEN: When applying direct marketing follow up knowledge

WHAT: Dan Kennedy's Moving Parade of Interest — keeping your marketing consistently visible to hot prospects WHEN: When applying direct marketing moving parade knowledge

WHAT: Dan Kennedy's Shock and Awe Package — overwhelming value to eliminate price resistance WHEN: When applying direct marketing shock awe knowledge

"WHAT: the VIDEO ORGAN prompt — produces an explainer VIDEO from a published blog post using the proven video pipeline (script -> TTS audio + timing -> excalidraw diagrams -> remotion composition -> render -> ffmpeg assembly). WHEN: when the nightly video…

WHAT: the reliability-scored prompt-skill library for getting an AGENT to DO a task. WHEN: you need to dispatch an agent to do a task; or you say 'find / add / score / goldenize a prompt-skill for X' -- from change (dispatch the worker), seework (a gap that…

"WHAT: the BLOG ORGAN — produces THE FIXPOINT POST for a framework (the ONE invariant blog format: OVERVIEW + JOURNEY + FRAMEWORK, explicit hero's-journey structure) by reconstructing the journey from the journal/durable layer, FILLING the JourneyCore model,…

"WHAT: produces Blog 2 of a framework CHAPTER — the mechanical DEEP-DIVE technical article ('how it actually works') — for an already-built AIOS by reading its impl docs (doc(m) + SYSTEM.md + STATE_GRAPH) and assembling a faithful how-it-works explanation…

WHAT: THE blog writing skill — a dispatchable agent prompt that fills ONE JourneyCore + ONE JourneyBlog (the AIDA-within-AIDA blog format) from a source blog/journey, so the deterministic suite renderer derives the AIDA blog + the twitter/linkedin/discord…

WHAT: a dispatchable agent prompt that turns ONE published blog post into a ready-to-post socials pack — a Twitter/X thread, a LinkedIn post, a Discord post, and image prompts — following the 6-link mimetic desire chain quality bar. WHEN: when a blog is live…

WHAT: a dispatchable agent prompt that renders the actual PNG images for a blog's socials pack — hero, social-share, and thumbnail — as rich Excalidraw diagrams rendered via the render.py Playwright pipeline, visually verified. WHEN: when a socials pack…

"WHAT: folds a framework into the author's SkillTome (legacy name: nomicon) — the top-level holder + search of all of {user}'s frameworks (its {aios}-volumes). Creates the {user}-tome holder skill if it does not exist, then registers/updates the framework's…

[0.1.1] The specific cause that precipitated a transaction's transition to the aborted_state, such as a constraint vio

[0.1.2] The intermediate state of rows modified by a transaction that later aborted; the partial_effects_undone that e

[0.1.3] A durable record written to the transaction log capturing a single row modification, containing the transactio

[0.1.4] A protocol constraint requiring that a transaction in the aborted_state cannot be re-executed automatically by

[0.1.5] The deterministic act of relinquishing every lock held by a transaction upon reaching its transaction_boundary

[0.1.6] The invariant that upon rollback all modifications performed by the transaction are reversed to match the befo

[0.1] the core subdomain of database transaction isolation and concurrency control (17 concepts)

[0.2.1] The all-or-nothing property: a transaction's effects are either fully applied or fully absent; implemented via

[0] dinf: in the dinf domain: frame the task, recall a proven dinf chain, choose exploit (select a golden chain) vs explore (construct a new one), execute it, record the reward

How the bandit (the default ChainSelector persona) rolls up the AC→CoR→SC algebra and CLOSES it into a domain-specific persona — a self-contained "bandit chain system" that builds its own KB and improves itself via GlyphSteer chains. Use when asked to mint a…

[0.2] the dinf default workflow (BanditChain) — walk it

[0.1] in the dinf domain: frame the task, recall a proven dinf chain, choose exploit (select a golden chain) vs explore (construct a new one), execute it, record the reward

[0.1.3] ADJOIN — two frames fighting is a missing Ω one level up; pair them and close it

[0.1.4] CHRISTEN — name the invariant the moment things converge, or it evaporates

[0.1.2] FACTOR — find any framework's Ω by the three laws; what remains is k

[0.1.1] the governing chain: factor to the closure, inhabit a view, lift at the boundary, join into a plan, realize it

WHAT: assemble a framework CHAPTER from the two rendered blog posts — run framework.assemble_chapter to copy Blog 1 + Blog 2 verbatim into a self-contained chapter dir, wire the relative cross-links + plugin/skill links + CTAs, and write the chapter.md…

WHAT: produce Blog 2 of a framework CHAPTER — the mechanical deep-dive ('how it actually works') — for an already-built AIOS/package by reading its impl docs (README architecture sections, design docs, the code's module docstrings) and assembling a faithful…

WHAT: the TERMINAL stage — fold a finished framework into the author's SkillTome (the top-level holder + search of all their frameworks) by running framework.fold_into_tome, which registers the framework as a row on a tome volume node's generated ##…

WHAT: generate the FRAMEWORK SKILL for an already-built AIOS — the {aios}-volume (its SkillVolume face): one skill that indexes the AIOS's skills + rules + how they relate (as a diagram), gives a decision tree for what to do when, and ROUTES the agent into…

WHAT: produce Blog 1 of a framework CHAPTER — the narrative chapter-opener — for an already-built AIOS/package by reconstructing its journey from its own dir (CLAUDE.md, README, dev log) and FILLING framework.JourneyCore, then rendering with render_blog1…

WHAT: package a framework as a Claude Code PLUGIN (its operational face) — run framework.package_plugin to assemble plugin.json + skills/{aios}-volume/SKILL.md + the chapter bundled under resources/, with the skill's chapter links repathed to the bundle.…

Turn an already-built AIOS/package into a framework chapter — narrative blog + deep-dive blog → chapter → {aios}-volume index skill → plugin → folded into the author's SkillTome.

Use to refuse AI slop on every output: fix the sense, define the valid type, name the failure mode (emit-P-without-P-ness), define P-ness (the gate) and refuse the failure, grade every correspondence (G0–G9, never round up), commit, then actualize. The…

WHAT: the development-flow for the split-content capability — separating a concept whose description (n.d) holds raw CONTENT (a data dump / pasted document) from a real DESCRIPTION, by splitting the raw content into its own `{concept_name}_Desc_Content` node.…

WHAT: the dev-flow for the OPTIONAL domain/subdomain/personal_domain/produces params on add_concept_tool_func — the internal chokepoint function every CartON concept-creation caller (Dragonbones, sm_gate.py, split_content_concept, the migration scripts)…

WHAT: the development-flow for changing the CartON KV / CartonObj capability — the embedded-structured-KV-in-concept-descriptions feature (a <CartonObj name=..>{ JSON-with-bare-refs }</CartonObj> fence in n.d): the carton_kv parser/normalizer, edit_carton_obj…

WHAT: the dev-flow for editing the WEBBING AGENT — carton's standing CONCEPT-ATOMIZATION daemon, CLONED from the proven Sophia (docmirror-cohere) architecture: CODE detects a batch of under-structured, autolinker-processed, main-agent-authored concepts…

WHAT: just-in-time building of TreeShell nodes from CartON graph relationships — when a jump targets a coordinate not found in any family JSON config, resolve the CartON concept into a cached Menu node whose options come from its HAS_PART relationships. WHEN:…

WHAT: the CartON MCP — a persistent knowledge graph (Neo4j + ChromaDB) you add concepts to, query, edit, and project. WHEN: persisting knowledge, creating observations/concepts, querying concept networks, semantic search, or editing a concept's…

WHAT: Precision editing of CartON concept descriptions WHEN: When you need to update a concept description with surgical edits

WHAT: capture architectural design insights from a conversation into CartON as Design_-prefixed concepts in an architecture collection, with full descriptions and cross-reference relationships to other design concepts. WHEN: when an architecture discussion…