/wbExplain — Live Demo ()
What /wbExplain would actually produce on wb-labs today (2026-05-04). Rows, files, and concepts in this matrix are real — the explanations the agent would generate are excerpted from realistic outputs.
1. Live target
| Field | Live value |
|---|---|
| Active package | core2/packages/wb-core |
| Active plan | reports/20260504/plans/plan_wb-core_20260504.md (3 rows, all ⬜) |
| Memory available to the agent | MEMORY.md index plus 12 leaf files (user profile, project tech debt, feedback rules, etc.) |
| Search corpus for free-text targets | The full working tree under /home/wissemb11/Allprojects/wb-labs/ |
/wbExplain is the only command in this group that actively reads memory at runtime. When you ask "what is the docs edition," it's the memory file project_docs_edition.md that tells it. The other commands in the QA group read code; /wbExplain reads code and memory.
2. What each target form would resolve to today
| Target | Live resolution |
|---|---|
--id="1" | Row 1 of plan_wb-core_20260504.md — JWT handshake. Files referenced: tierEnforcement.js. |
--id="*" | All 3 rows: JWT handshake, renderString escape, WBC.js decomposition. Synthesized as one narrative. |
core2/packages/wb-core/ | Package-level explanation: role, exports, position in the monorepo. |
core2/packages/wbc-ui2-cdn/ | Triggers the parked tech-debt note: "package declares main at dist/ but vite writes to dist-dev/" (per project_pkg_dist_mismatch.md). |
"the wbCode dev gate" | Resolves to the __WBC_DEV__ 3-mode pattern (full / dev / hidden) — visible in feedback_wbCode_dev_only.md. |
"WBDataViewer apiResponse_" | Resolves to the cache-pattern memory note plus the actual code in core2/packages/wb-dataviewer/. |
"docs edition" | Resolves to project_docs_edition.md (the structural rules for this very documentation project). |
The free-text resolutions are interesting because they pull from memory + code. A naive grep would miss them; a code-only search would miss the context the memory adds.
3. Per-flag behavior, applied live
| Flag combination | What /wbExplain would produce |
|---|---|
--id="1" (no style) | ~400-word principle-first explanation of the JWT handshake row. |
--id="1" --as="eli5" | ~200-word version with bouncer/bracelet metaphors. |
--id="1" --as="fr, expert" | Same content, French, with technical vocabulary preserved (no translation of JWT, tierEnforcement). |
"WBDataViewer apiResponse_" --as="senior reviewer, skeptical" | Surfaces the three open questions (key scope, naming, no invalidation) before any approval. |
"docs edition" (no style) | The structural rules: 33 commands × 6 layers, no hub files, english-only docs. |
4. Pipelines
/wbExplain "frontEnd/wbc-ui/core2/packages/wb-flow/templates/" --as="expert, fr, IPEIM CS senior, internship onboarding"> /wbExplain "frontEnd/wbc-ui/core2/packages/wb-flow/templates/" --as="expert, fr, IPEIM CS senior, internship onboarding"💠 Pipeline Onboarding doc for the IPEIM student
Wissem teaches at IPEIM (CS instructor since 2018, per memory). A senior-year student joining wb-labs for an internship needs the conceptual map of the agentic framework, in French.
💠 Pipeline The WBDataViewer apiResponse_ design review
A reviewer comes back to the WBDataViewer code six months from now. They see apiResponse_ (with the trailing underscore) and don't remember why. Run live:
💠 Pipeline The dist-folder mismatch, explained for a fresh pair of eyes
A real piece of tech debt parked in memory: the wbc-ui2 packages declare main at dist/ but vite writes to dist-dev/. Someone new sees a "module not found" error and asks /wbExplain "core2 dist folder mismatch":
5. What would refuse today
| Trigger | Live response |
|---|---|
/wbExplain with no target | Halt. Provide --id, a path, or a concept string. |
/wbExplain --id="*" right now | Produces the 3-row epic overview (rows are ⬜ but explanation doesn't require Done). |
/wbExplain --id="4" | Halt. Plan only contains 3 rows. |
/wbExplain "the auth thing" | Disambiguation prompt — could be JWT in wb-core, login in wbc-ui.com, session handling in wbc-ui2-cdn. Lists all three; asks user to pick. |
/wbExplain "rebuild the universe" | Honest "no clear target found in workspace" with suggestions of nearby concepts. |
/wbExplain --id="1" --as="haiku" | Honors the constraint. Produces a haiku about the JWT handshake row. The user owns the format. |
The unifying point: /wbExplain is the most permissive command in the QA group on the input side and the most disciplined on the output side. It accepts almost any target; it refuses to produce content that's incorrect-but-confident. When in doubt, it asks; when truly unable, it admits.