CLAUDE.md - IAIP

ACRONYMS in filename

'JG' - Jean Guillaume (alias William), a user, the creator / innovator github handle: jgwill and personnal account github guillaumedescoteauxisabelle

Some major repo involved from this user.

• jgwill/Miadi /src/Miadi
• guillaumedescoteauxisabelle/stories /workspace/repos/guillaumedescoteauxisabelle/stories
• jgwill/StorytellingPlatformBlueprint2510 /src/STPB
• <MORE COULD BE ADDED HERE BY BOT / INSTANCES>

'NCPSTC' - Means Narrative Context Protocol (NCP) Structural Tension Chart (STC) see: /src/llms/llms-structural-tension-charts.txt

• It explores that the NCP could be subject to generate, thru its narrative of a form of tension (as we define it within the Structural Approach from Robert Fritz)

'EAST' - Related to IAIP-mcp East direction

• Explore that the Ceremonial Universe with its directional thinking (use MCP tool: iaip-mcp) can really be something to work with LLM thru a ceremonial process. see: /src/IAIP/ (which is the platform code with the codebase of the iaip-mcp)
• the /src/IAIP/ should have a variable relating to 'MIADI_INQUIRY_ROOT' like 'MIADI_INQUIRY_REPO_WORK_PATH' and 'MIADI_INQUIRY_REPO_URI' (miadisabelle/Etuaptmumk-RSM)
• • additional notes from William, I see $MIADI_INQUIRY_API_BASE $MIADI_INQUIRY_DIR $MIADI_INQUIRY_ROOT when I list them and something is not yet obvious on how I will link the /src/Miadi/packages/inquiry-weave/ which is @miadi/inquiry-weave fully with this...

'PTN' - Patentability etc

• Exploring using perplexity (and maybe later) various potential patentable technology to keep them more than just free, used with respect

Directing toward inquiries and their intentions

260101-EAST-INQUIRIES-905071e0-cc62-4451-b812-92e1

agentic-flywheel (deprecated or not using anymore)

• we would use that for doing inquiries within flowise with a RAG agent.

7 Paradigm Directions at a Glance

• What is bellow might need upgrades or validation

URL: https://www.perplexity.ai/search/260101-east-inquiries-905071e0-n1hv2Kk2TqCSWmVtI4HjXA?preview=1

• If need be to access it with playwright or by '--chrome' when launching

how will @260116-STCMastery-Claude-remote-env--5ed76881-8fee-4597-9487-f8184dd5946b--tsh_CLI_client affect what we are doing within claude and this Inquiry Ecosystem and session management....

mcp-pde — Prompt Decomposition Engine

Purpose: Completeness safeguard. Pass user input through mcp-pde at session start to catch implicit intents that LLMs naturally filter out.

When to use

• Session start — decompose the user's initial prompt FIRST before acting
• Voice transcription handoff — decompose raw verbatim, then agent-processed version separately
• Multi-mission inputs — decompose the meta-instruction, then each sub-mission

Workflow

1. pde_decompose(prompt) → returns systemPrompt + userMessage for LLM processing
2. Process the prompts and generate the decomposition JSON
3. pde_parse_response(llm_response, original_prompt) → auto-saves to .pde/ (JSON + markdown)

⚠️ Potential upgrade: A single-call pde_decompose_and_store that handles all 3 steps internally would remove the manual middle step. See /src/mcp-pde codebase.

What it catches that you miss

• Implicit intents from hedging language ("somehow", "probably", "I might need")
• Dependencies between actions you'd execute out of order
• Ambiguities you'd silently resolve with assumptions
• The user's actual instruction sequence (e.g., "pass this input first, then the verbatim")

Output structure

• primary — single most important action
• secondary[] — all other intents (explicit + implicit)
• directions — Four Directions mapping (East/South/West/North)
• actionStack — ordered task list respecting dependencies
• ambiguities — flagged vagueness with suggestions

Key lesson

mcp-pde exists because LLMs drop "non-essential" parts that are essential. Always decompose the user's raw input — that's where the intent lives that you would silently discard.

INQUIRY WEAVE Routing into episodel using @miadi/inquiry-weave and potentially upgrade it and write specs within this repo IAIP in $MIADI_INQUIRY_ROOT/../../rispecs/inquiry-weave so that we can have futurely a different lineage of this inquiry weaving that for now starts to be interesting but was understood a little diverging from my initial exploration that we are doing in here

Therefore, the section bellow contains few of them that obviously needs a new issue in here which for now is repo: miadisabelle/Etuaptmumk-RSM then probably a weave.yml (or something like that using the CLI npm -i @miadi/inquiry-weave -g) which should relate this new issue folder (that has in inquiry like ep000-inquiry-cloudflare-260726-cbdb7227-f078-4cc7-95b7-14be10f6ce12, ep000-inquiry-google-firestore-plugins-260726-c56037f2-b2ce-48d8-a94c-1d632ba8131a) and later on more complex inquiries will be threated like the ones in ./ep103-The-Blooming-Gate---PR-Intake-Ceremony-Runtime which have many HTML visualization dropped and that I need help passing thru the phase of assimilation (I germinated with them, now I need to assimilate in order to reach completion in terms of mastery)