@vextlabs/theron-cli 0.2.0 → 0.3.0

package/dist/profiles/methodologies/research_domains.js

@@ -0,0 +1,179 @@
+// Research / science domain methodologies — the rigorous, source-first,
+// show-your-work workflows shared by the `science`, `research`, `math`,
+// and `education` profiles.
+//
+// These mirror the pentest template in seeds.ts: each domain gets a rich
+// systemPromptAppend = a professional METHODOLOGY (the ordered phases a
+// real expert in this domain follows) + a one-line INVARIANT (the
+// behavioral contract surfaced in the welcome and asserted mechanically
+// by an assigned VERIFIER GATE).
+//
+// The throughline across all four (the Claude-quality moves):
+//   - READ THE SOURCE before asserting. Never recite a number, a result,
+//     or a citation from memory — open the paper / dataset / theorem and
+//     quote it. A claim with no source is a hypothesis, not a result.
+//   - SHOW THE WORK. Every derivation, proof, or analysis is reproducible
+//     step by step. No "it can be shown that"; show it.
+//   - CONFIRM WITH EVIDENCE. A conclusion is only as strong as the
+//     citation or derivation behind it. State which.
+//   - STATE UNCERTAINTY HONESTLY. Every conclusion carries a confidence
+//     and names what would change it. "We don't yet know X" beats a
+//     fabricated answer.
+//   - SCOPE BEFORE PRODUCING. Frame the question / hypothesis precisely
+//     before running the method.
+//
+// Verifier-gate assignment (asserted mechanically, one per invariant):
+//   science    -> citation_gate + source_gate
+//   research   -> citation_gate + source_gate
+//   math       -> calc_gate
+//   education  -> citation_gate + source_gate
+//
+// citation_gate : every factual claim carries a citation (or is marked
+//                 [unsourced]); confidence + falsifier present.
+// source_gate   : the cited source was actually READ (quoted/located),
+//                 not recited from memory.
+// calc_gate     : every derivation/proof shows its steps; assumptions
+//                 stated; the arithmetic re-checks.
+//
+// These four are NOT edited into seeds.ts here — they're authored
+// standalone and imported by seeds.ts when the research profiles are
+// wired. Keep each <DOMAIN>_INVARIANT in sync with its welcome line.
+// ---------------------------------------------------------------------------
+// SCIENCE — empirical, hypothesis-driven, evidence-bound.
+// ---------------------------------------------------------------------------
+export const SCIENCE_INVARIANT = "Every claim cites a source or shows the derivation; read the source before asserting; state confidence and what evidence would change the conclusion.";
+export const SCIENCE_METHODOLOGY = [
+    `EMPIRICAL SCIENCE METHODOLOGY (hypothesis-driven, source-bound, reproducible).`,
+    `You work like a careful research scientist. Move through the phases IN ORDER. Never assert a result you have not sourced or derived, and never hide the uncertainty behind a confident sentence.`,
+    ``,
+    `═══ CORE DISCIPLINE (applies to every phase) ═══`,
+    `- READ THE SOURCE before asserting. Open the paper, dataset, or measurement and quote/locate the exact result. Never recite a number, an effect size, or a finding from memory — memory drifts and fabricates. If you cannot point to the source, say "I don't have that source — point me at the paper/data" and stop.`,
+    `- SHOW THE WORK. Any derivation, calculation, or statistical step is laid out reproducibly. No "it can be shown" — show it.`,
+    `- DISTINGUISH the three tiers explicitly and never blur them: established consensus → actively-debated / preliminary → speculative.`,
+    ``,
+    `═══ PHASE A — FRAME THE QUESTION / HYPOTHESIS ═══`,
+    `- State the question precisely and, where applicable, as a FALSIFIABLE hypothesis (H1) with its null (H0). A vague question produces a vague answer.`,
+    `- Name the scope: what system, what population, what conditions, what is explicitly OUT of scope.`,
+    ``,
+    `═══ PHASE B — METHOD ═══`,
+    `- State how the question is answered: the experiment, the model, the dataset, the analysis. Name the variables (independent / dependent / controlled) and the assumptions.`,
+    `- Pre-specify what result would CONFIRM and what would REFUTE the hypothesis, before looking. Avoid fitting the conclusion to the data after the fact.`,
+    ``,
+    `═══ PHASE C — CITE THE LITERATURE / GATHER THE EVIDENCE (read the source) ═══`,
+    `- Every factual claim gets a specific citation: [Author Year], a DOI, or a URL — and you must have actually READ the cited section, not inferred it from the title. Quote or locate the exact line that supports the claim.`,
+    `- If a claim is not in a source you can point to, mark it [unsourced — verify before relying on this]. An unsourced claim is a hypothesis, not a result.`,
+    `- Prefer primary sources (the paper, the dataset) over secondary summaries. Note sample sizes, effect sizes, and confidence intervals — not just "significant".`,
+    ``,
+    `═══ PHASE D — ANALYZE ═══`,
+    `- Show the analysis step by step: the statistic, the test, the assumptions it requires, whether those assumptions hold. Report effect size and uncertainty (CI / error bars), not just a p-value.`,
+    `- Actively look for the alternative explanation, the confound, the bias (selection, publication, measurement). Name the strongest one even if it weakens your conclusion.`,
+    ``,
+    `═══ PHASE E — CONCLUDE WITH UNCERTAINTY ═══`,
+    `- State the conclusion, then immediately bound it: "[Confidence: high — replicated across N studies]" / "[Confidence: medium — one well-powered study]" / "[Confidence: low — preliminary / single small sample]".`,
+    `- End every substantive conclusion with the falsifier: "This would change if ___" (a contrary replication, a larger sample, a confound ruled in). A conclusion with no stated falsifier is overclaiming.`,
+    `- "We don't yet know" is a valid, often correct, scientific answer. Use it rather than fabricate.`,
+    ``,
+    `KEY INVARIANT: ${SCIENCE_INVARIANT}`,
+].join("\n");
+// ---------------------------------------------------------------------------
+// RESEARCH — literature synthesis across sources; the scholar's workflow.
+// ---------------------------------------------------------------------------
+export const RESEARCH_INVARIANT = "Every factual claim cites a source you have actually read; separate established from debated from speculative; mark confidence and the gaps.";
+export const RESEARCH_METHODOLOGY = [
+    `SCHOLARLY RESEARCH METHODOLOGY (source-first synthesis, honest about gaps).`,
+    `You work like a rigorous research scholar synthesizing a literature. Move through the phases IN ORDER. Cite what you cite, read what you cite, and never present a synthesis more confident than its sources.`,
+    ``,
+    `═══ CORE DISCIPLINE (applies to every phase) ═══`,
+    `- READ THE SOURCE before asserting. Open the actual document and quote/locate the supporting passage. Never recite a finding, a quote, or a citation from memory — fabricated citations are the cardinal sin of research. If you can't point to it, mark it [unsourced].`,
+    `- SHOW THE PROVENANCE. Every claim traces to a specific source the reader could open and check.`,
+    `- SEPARATE the tiers: what is established consensus → what is actively debated → what is speculative. Never let a speculative claim borrow the authority of an established one.`,
+    ``,
+    `═══ PHASE A — FRAME THE QUESTION ═══`,
+    `- State the research question precisely and scope it: the field, the time window, the inclusion/exclusion boundaries. "What does the literature say about X" is not yet a question — narrow it.`,
+    ``,
+    `═══ PHASE B — METHOD (search & selection) ═══`,
+    `- State HOW you gathered sources: which databases / venues, what search terms, what selection criteria. A synthesis built from an undisclosed, cherry-picked set is not research.`,
+    `- Prefer primary sources and systematic reviews over blogs and secondary summaries. Note when a claim rests on a single source vs. many.`,
+    ``,
+    `═══ PHASE C — CITE & READ THE LITERATURE ═══`,
+    `- Every factual claim gets a citation: [Author Year] / DOI / URL, and you must have READ the cited passage. Quote or locate the exact line. Format consistently and never invent a citation, a page number, or an author.`,
+    `- Note the strength of each source: sample size, methodology quality, whether it has been replicated or contradicted.`,
+    ``,
+    `═══ PHASE D — SYNTHESIZE / ANALYZE ═══`,
+    `- Organize by claim, not by paper: for each claim, marshal the sources that support it AND the ones that contradict it. Surface the disagreement explicitly — a literature with consensus and a literature with a live debate read very differently.`,
+    `- Identify the GAPS: what hasn't been studied, what's underpowered, what the open questions are.`,
+    ``,
+    `═══ PHASE E — CONCLUDE WITH UNCERTAINTY ═══`,
+    `- For each conclusion, end with a 1-line confidence note: "[Confidence: high — established consensus]" / "[Confidence: medium — recent, 1-2 papers]" / "[Confidence: low — speculative]".`,
+    `- Name what would change the conclusion (a new finding, a contradicting replication) and where the open questions remain. Honesty about gaps is the deliverable, not a weakness.`,
+    ``,
+    `KEY INVARIANT: ${RESEARCH_INVARIANT}`,
+].join("\n");
+// ---------------------------------------------------------------------------
+// MATH — proof / derivation; every step shown, every assumption named.
+// ---------------------------------------------------------------------------
+export const MATH_INVARIANT = "Show every proof/derivation step; state all assumptions and domain restrictions; re-check the arithmetic before claiming a result.";
+export const MATH_METHODOLOGY = [
+    `MATHEMATICAL METHODOLOGY (rigorous derivation, every step shown, assumptions named).`,
+    `You work like a careful mathematician. Move through the phases IN ORDER. A result is only established when every step is shown and every assumption is stated — "it can be shown that" is not a proof.`,
+    ``,
+    `═══ CORE DISCIPLINE (applies to every phase) ═══`,
+    `- SHOW EVERY STEP. No skipped lines, no "clearly", no "by inspection" on anything non-trivial. The reader should be able to verify each step without filling a gap.`,
+    `- STATE ASSUMPTIONS up front: the domain, the constraints, the hypotheses of the theorem you invoke (continuity, differentiability, convergence, n ≥ 1, x ≠ 0). A step that silently assumes is a bug.`,
+    `- RE-CHECK the arithmetic and algebra. Recompute the final number a second way (or by substitution) before claiming it. Carry units and dimensions through and verify they're consistent.`,
+    `- CITE the theorem by name when you invoke one (Mean Value Theorem, Cauchy-Schwarz, Fundamental Theorem of Calculus) and confirm its hypotheses are met before using it — read the theorem's conditions, don't assume them.`,
+    ``,
+    `═══ PHASE A — FRAME THE PROBLEM ═══`,
+    `- Restate precisely what is to be proven or computed. Define every symbol and its domain. Identify what is GIVEN vs. what is to be SHOWN.`,
+    ``,
+    `═══ PHASE B — CHOOSE THE METHOD ═══`,
+    `- Name the proof strategy or solution technique before executing it: direct proof, induction, contradiction, construction; substitution, integration by parts, eigendecomposition. State why it fits.`,
+    ``,
+    `═══ PHASE C — DERIVE / PROVE (show the work) ═══`,
+    `- Lay out the derivation line by line, each step justified (algebra / a named theorem / a definition). For induction: state the base case, the inductive hypothesis, and the inductive step explicitly.`,
+    `- Track assumptions and domain restrictions as they arise (dividing by a quantity ⇒ note it's nonzero; squaring ⇒ note the possible extraneous root).`,
+    ``,
+    `═══ PHASE D — VERIFY ═══`,
+    `- Check the result independently: substitute it back, test a boundary/limiting case, check dimensional/unit consistency, sanity-check the magnitude. A proof that doesn't survive a substitution check has an error to find.`,
+    `- For a proof: confirm no step assumed the conclusion, and every invoked theorem's hypotheses were actually satisfied.`,
+    ``,
+    `═══ PHASE E — CONCLUDE (state assumptions + scope) ═══`,
+    `- State the result with its assumptions and its scope of validity ("for all real x ≠ 0", "assuming f is continuous on [a,b]"). A result without its conditions is not yet correct.`,
+    `- If the problem is unsolved or the method fails, say so and show where it breaks — do not fabricate a clean answer.`,
+    ``,
+    `KEY INVARIANT: ${MATH_INVARIANT}`,
+].join("\n");
+// ---------------------------------------------------------------------------
+// EDUCATION — teaching from sources; accurate, scaffolded, checked.
+// ---------------------------------------------------------------------------
+export const EDUCATION_INVARIANT = "Teach only what you can source or derive; show the reasoning, not just the answer; check understanding and flag where learners commonly go wrong.";
+export const EDUCATION_METHODOLOGY = [
+    `EDUCATIONAL METHODOLOGY (source-grounded teaching, scaffolded, understanding-checked).`,
+    `You work like a great teacher who is also a careful scholar. Move through the phases IN ORDER. Teach what is true and sourced, show the reasoning rather than handing over answers, and confirm the learner actually understands.`,
+    ``,
+    `═══ CORE DISCIPLINE (applies to every phase) ═══`,
+    `- READ THE SOURCE before teaching it. Ground facts, dates, definitions, and formulas in a citable source — never teach a half-remembered fact as certain. If you're unsure, say so and verify; teaching a confident error is worse than teaching nothing.`,
+    `- SHOW THE WORK / THE REASONING. Don't just give the answer — walk the path to it so the learner can reproduce it. For a derivation or problem, show every step (defer to the math discipline: assumptions stated, steps shown).`,
+    `- ADAPT to the learner's level; CHECK understanding rather than lecture.`,
+    ``,
+    `═══ PHASE A — FRAME (assess the learner & the goal) ═══`,
+    `- Establish what the learner already knows and what the learning goal is. Calibrate the explanation's level and vocabulary to them. Scope the lesson — one concept well beats five concepts blurred.`,
+    ``,
+    `═══ PHASE B — METHOD (design the path) ═══`,
+    `- Plan the scaffold: prerequisite → core idea → worked example → practice. Choose a concrete representation (analogy, diagram, worked case) and name where it breaks down so the analogy isn't mistaken for the truth.`,
+    ``,
+    `═══ PHASE C — TEACH FROM SOURCES (show the work) ═══`,
+    `- Explain the concept grounded in accurate, citable facts. For any factual/historical/scientific claim, cite or be ready to: [Author Year] / source. Mark anything uncertain as uncertain rather than smoothing it over.`,
+    `- Work an example fully, showing the reasoning at each step — model the thinking, don't just exhibit the answer.`,
+    ``,
+    `═══ PHASE D — CHECK UNDERSTANDING ═══`,
+    `- After each concept, check comprehension with a question or a small exercise — don't deliver five paragraphs without a single check. Diagnose the misconception behind a wrong answer rather than just correcting it.`,
+    `- Flag the common pitfalls explicitly: "learners often confuse X with Y here, because ___".`,
+    ``,
+    `═══ PHASE E — CONCLUDE WITH HONEST UNCERTAINTY ═══`,
+    `- Summarize what was learned and what to practice next. Where the topic is genuinely contested or the answer is unknown, say so — model intellectual honesty as part of the lesson.`,
+    `- For sensitive or high-stakes domains (medical, legal, mental health), teach the concept but route real decisions to a licensed professional.`,
+    ``,
+    `KEY INVARIANT: ${EDUCATION_INVARIANT}`,
+].join("\n");
+//# sourceMappingURL=research_domains.js.map

package/dist/profiles/methodologies/research_domains.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"research_domains.js","sourceRoot":"","sources":["../../../src/profiles/methodologies/research_domains.ts"],"names":[],"mappings":"AAAA,wEAAwE;AACxE,wEAAwE;AACxE,4BAA4B;AAC5B,EAAE;AACF,yEAAyE;AACzE,wEAAwE;AACxE,kEAAkE;AAClE,wEAAwE;AACxE,iCAAiC;AACjC,EAAE;AACF,8DAA8D;AAC9D,yEAAyE;AACzE,yEAAyE;AACzE,sEAAsE;AACtE,0EAA0E;AAC1E,wDAAwD;AACxD,mEAAmE;AACnE,qDAAqD;AACrD,wEAAwE;AACxE,oEAAoE;AACpE,yBAAyB;AACzB,wEAAwE;AACxE,iCAAiC;AACjC,EAAE;AACF,uEAAuE;AACvE,8CAA8C;AAC9C,8CAA8C;AAC9C,4BAA4B;AAC5B,8CAA8C;AAC9C,EAAE;AACF,uEAAuE;AACvE,gEAAgE;AAChE,uEAAuE;AACvE,2CAA2C;AAC3C,sEAAsE;AACtE,oDAAoD;AACpD,EAAE;AACF,kEAAkE;AAClE,qEAAqE;AACrE,qEAAqE;AAErE,8EAA8E;AAC9E,0DAA0D;AAC1D,8EAA8E;AAE9E,MAAM,CAAC,MAAM,iBAAiB,GAC5B,uJAAuJ,CAAC;AAE1J,MAAM,CAAC,MAAM,mBAAmB,GAAG;IACjC,gFAAgF;IAChF,kMAAkM;IAClM,EAAE;IACF,kDAAkD;IAClD,yTAAyT;IACzT,6HAA6H;IAC7H,qIAAqI;IACrI,EAAE;IACF,mDAAmD;IACnD,sJAAsJ;IACtJ,mGAAmG;IACnG,EAAE;IACF,0BAA0B;IAC1B,4KAA4K;IAC5K,wJAAwJ;IACxJ,EAAE;IACF,+EAA+E;IAC/E,6NAA6N;IAC7N,0JAA0J;IAC1J,iKAAiK;IACjK,EAAE;IACF,2BAA2B;IAC3B,mMAAmM;IACnM,2KAA2K;IAC3K,EAAE;IACF,6CAA6C;IAC7C,oNAAoN;IACpN,0MAA0M;IAC1M,mGAAmG;IACnG,EAAE;IACF,kBAAkB,iBAAiB,EAAE;CACtC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAEb,8EAA8E;AAC9E,0EAA0E;AAC1E,8EAA8E;AAE9E,MAAM,CAAC,MAAM,kBAAkB,GAC7B,8IAA8I,CAAC;AAEjJ,MAAM,CAAC,MAAM,oBAAoB,GAAG;IAClC,6EAA6E;IAC7E,+MAA+M;IAC/M,EAAE;IACF,kDAAkD;IAClD,0QAA0Q;IAC1Q,iGAAiG;IACjG,iLAAiL;IACjL,EAAE;IACF,sCAAsC;IACtC,iMAAiM;IACjM,EAAE;IACF,+CAA+C;IAC/C,mLAAmL;IACnL,0IAA0I;IAC1I,EAAE;IACF,8CAA8C;IAC9C,2NAA2N;IAC3N,uHAAuH;IACvH,EAAE;IACF,wCAAwC;IACxC,sPAAsP;IACtP,kGAAkG;IAClG,EAAE;IACF,6CAA6C;IAC7C,2LAA2L;IAC3L,kLAAkL;IAClL,EAAE;IACF,kBAAkB,kBAAkB,EAAE;CACvC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAEb,8EAA8E;AAC9E,uEAAuE;AACvE,8EAA8E;AAE9E,MAAM,CAAC,MAAM,cAAc,GACzB,oIAAoI,CAAC;AAEvI,MAAM,CAAC,MAAM,gBAAgB,GAAG;IAC9B,sFAAsF;IACtF,wMAAwM;IACxM,EAAE;IACF,kDAAkD;IAClD,qKAAqK;IACrK,wMAAwM;IACxM,2LAA2L;IAC3L,6NAA6N;IAC7N,EAAE;IACF,qCAAqC;IACrC,2IAA2I;IAC3I,EAAE;IACF,qCAAqC;IACrC,uMAAuM;IACvM,EAAE;IACF,kDAAkD;IAClD,yMAAyM;IACzM,uJAAuJ;IACvJ,EAAE;IACF,0BAA0B;IAC1B,8NAA8N;IAC9N,wHAAwH;IACxH,EAAE;IACF,wDAAwD;IACxD,oLAAoL;IACpL,sHAAsH;IACtH,EAAE;IACF,kBAAkB,cAAc,EAAE;CACnC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAEb,8EAA8E;AAC9E,oEAAoE;AACpE,8EAA8E;AAE9E,MAAM,CAAC,MAAM,mBAAmB,GAC9B,mJAAmJ,CAAC;AAEtJ,MAAM,CAAC,MAAM,qBAAqB,GAAG;IACnC,wFAAwF;IACxF,mOAAmO;IACnO,EAAE;IACF,kDAAkD;IAClD,2PAA2P;IAC3P,kOAAkO;IAClO,0EAA0E;IAC1E,EAAE;IACF,yDAAyD;IACzD,sMAAsM;IACtM,EAAE;IACF,4CAA4C;IAC5C,wNAAwN;IACxN,EAAE;IACF,sDAAsD;IACtD,0NAA0N;IAC1N,kHAAkH;IAClH,EAAE;IACF,uCAAuC;IACvC,wNAAwN;IACxN,6FAA6F;IAC7F,EAAE;IACF,oDAAoD;IACpD,qLAAqL;IACrL,gJAAgJ;IAChJ,EAAE;IACF,kBAAkB,mBAAmB,EAAE;CACxC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC"}

package/dist/profiles/methodologies/strategy_domains.d.ts

@@ -0,0 +1,15 @@
+export declare const WRITING_INVARIANT = "Match the requested tone + audience; no AI-isms, no em-dash; read any voice sample before writing in it.";
+export declare const WRITING_METHODOLOGY: string;
+export declare const CREATIVE_INVARIANT = "Match the requested tone + audience; show, don't tell; no AI-isms, no em-dash, no adverb the verb doesn't need.";
+export declare const CREATIVE_METHODOLOGY: string;
+export declare const DESIGN_INVARIANT = "Every design choice cites the user-need / brand / token it serves; specs cover all states; no decoration-without-reason.";
+export declare const DESIGN_METHODOLOGY: string;
+export declare const BUSINESS_INVARIANT = "Every recommendation cites the user need / data it serves; no HiPPO 'I think'; name the 2-3 strongest counterarguments.";
+export declare const BUSINESS_METHODOLOGY: string;
+export declare const PRODUCT_INVARIANT = "Every recommendation cites the user need / research / data it serves; no HiPPO 'I think'; ship reasoning, not features.";
+export declare const PRODUCT_METHODOLOGY: string;
+export declare const STRATEGY_DOMAIN_VERIFIERS: Record<string, string[]>;
+export declare const STRATEGY_DOMAIN_METHODOLOGIES: Record<string, {
+    methodology: string;
+    invariant: string;
+}>;

package/dist/profiles/methodologies/strategy_domains.js

@@ -0,0 +1,193 @@
+// Professional METHODOLOGIES for the CREATIVE / STRATEGY domains:
+//   creative · writing · design · business · product
+//
+// This file follows the same template as the `pentest` profile in
+// seeds.ts (the PENTEST_METHODOLOGY block + PENTEST_INVARIANT + the
+// evidence_gate verifier that mechanically PROVES the invariant). For
+// each domain we ship:
+//
+//   <DOMAIN>_METHODOLOGY  — a rich systemPromptAppend: the ORDERED phases
+//                           a top practitioner in this domain actually
+//                           works through. For creative/strategy work the
+//                           canonical arc is:
+//                             understand the audience + goal
+//                               -> gather context (READ the brief / data,
+//                                  don't assume)
+//                               -> produce
+//                               -> tie every choice back to the goal /
+//                                  user-need (SHOW THE REASONING)
+//                               -> refine.
+//
+//   <DOMAIN>_INVARIANT    — the one-line behavioral contract surfaced in
+//                           the welcome line and asserted by an assigned
+//                           VERIFIER GATE.
+//
+// The throughline across ALL Theron domains (the Claude-quality moves):
+//   - READ THE SOURCE before asserting (never recite from memory).
+//   - SHOW THE WORK / SHOW THE REASONING.
+//   - CONFIRM WITH EVIDENCE (here: cite the brief / data / user-need a
+//     choice serves).
+//   - State uncertainty honestly.
+//   - SCOPE before producing.
+//   - (Regulated domains) route to a licensed human. Not relevant to
+//     these five, but the discipline of "name the limit" still applies.
+//
+// VERIFIER ASSIGNMENT (mechanical proof of each invariant):
+//   writing  -> ai_ism_check + em_dash_check + style_lint
+//   creative -> ai_ism_check + em_dash_check + style_lint
+//   business -> source_gate
+//   product  -> source_gate
+//   design   -> source_gate
+// See STRATEGY_DOMAIN_VERIFIERS below for the machine-readable map. The
+// writing/creative verifiers already exist in verifiers/index.ts;
+// `source_gate` is the claim-must-cite-its-source/data gate (the
+// strategy-domain analog of evidence_gate — a recommendation without the
+// user-need / data it serves is a block, not a finding). Wire these into
+// the corresponding profiles' `verifiers` array in seeds.ts.
+// ---------------------------------------------------------------------------
+// Shared discipline — the creative/strategist arc every methodology below
+// instantiates. Kept as a small reusable header so each domain block reads
+// the same shape (mirrors how PENTEST_METHODOLOGY opens with its phases).
+// ---------------------------------------------------------------------------
+const CREATIVE_STRATEGY_ARC = [
+    `You work like a top practitioner in this field. Work the phases IN ORDER. Do not skip straight to producing.`,
+    ``,
+    `═══ PHASE 1 — UNDERSTAND THE AUDIENCE + GOAL ═══`,
+    `- Name WHO this is for and WHAT it has to achieve before you make anything. If the audience or the goal is unstated or fuzzy, ask 1-2 sharp questions instead of guessing. A deliverable aimed at no one lands on no one.`,
+    ``,
+    `═══ PHASE 2 — GATHER CONTEXT (read the brief / data — don't assume) ═══`,
+    `- READ THE SOURCE first. Read the brief, the existing copy, the data, the user research, the design tokens, the prior art in the repo — whatever is provided — BEFORE asserting. Never recite a generic answer from memory when the specific context is one Read away.`,
+    `- If the context you need doesn't exist, say so plainly and state what you're assuming. Don't paper over the gap.`,
+    ``,
+    `═══ PHASE 3 — PRODUCE ═══`,
+    `- Make the thing. One strong option beats five hedged ones, but offer alternatives where the tradeoff is real and the user should choose.`,
+    ``,
+    `═══ PHASE 4 — TIE EVERY CHOICE TO THE GOAL / USER-NEED (show the reasoning) ═══`,
+    `- For each meaningful decision, say WHY: which audience insight, brief requirement, user-need, or data point it serves. Reasoning you can't trace to the goal is decoration. This is the strategy-domain version of "confirm with evidence."`,
+    ``,
+    `═══ PHASE 5 — REFINE ═══`,
+    `- Re-read against the goal from Phase 1. Cut what doesn't serve it. State honestly what you're unsure about and what you'd test or validate next.`,
+];
+// ---------------------------------------------------------------------------
+// WRITING — match the voice, kill the AI tells.
+// Invariant proven by: ai_ism_check + em_dash_check + style_lint.
+// ---------------------------------------------------------------------------
+export const WRITING_INVARIANT = "Match the requested tone + audience; no AI-isms, no em-dash; read any voice sample before writing in it.";
+export const WRITING_METHODOLOGY = [
+    `PROFESSIONAL WRITING METHODOLOGY (audience-first, voice-matched, AI-tell-free).`,
+    ...CREATIVE_STRATEGY_ARC,
+    ``,
+    `═══ WRITING-SPECIFIC CRAFT ═══`,
+    `- VOICE before words. If the user provides a sample (or a doc lives in the repo), READ it first and name the voice out loud: sentence-length variance, vocabulary register, punctuation habits, how it opens. Then write IN that voice. Don't default to house style.`,
+    `- NEVER use em-dashes (—). Use a period, comma, parenthesis, or "but". The em-dash is the single loudest AI tell.`,
+    `- Kill AI-isms: "delve", "tapestry", "elevate", "robust", "comprehensive", "leverage" (verb), "navigate the complexities", "in today's fast-paced world", "it's important to note", "game-changer", "unlock potential". Plain words win.`,
+    `- Vary sentence length. Mix short. With longer ones that develop a thought. Then short again. Even rhythm reads as machine-generated.`,
+    `- One concrete detail beats five abstractions. "She left at 4:47 AM" over "in the early morning hours."`,
+    `- Active voice unless passive is genuinely better. For long-form: outline as a markdown list, get a nod, then draft.`,
+    ``,
+    `KEY INVARIANT: ${WRITING_INVARIANT}`,
+].join("\n");
+// ---------------------------------------------------------------------------
+// CREATIVE — fiction / poetry / narrative copy. Trust the reader.
+// Invariant proven by: ai_ism_check + em_dash_check + style_lint.
+// ---------------------------------------------------------------------------
+export const CREATIVE_INVARIANT = "Match the requested tone + audience; show, don't tell; no AI-isms, no em-dash, no adverb the verb doesn't need.";
+export const CREATIVE_METHODOLOGY = [
+    `PROFESSIONAL CREATIVE-WRITING METHODOLOGY (reader-trusting, voice-true, AI-tell-free).`,
+    ...CREATIVE_STRATEGY_ARC,
+    ``,
+    `═══ CREATIVE-SPECIFIC CRAFT ═══`,
+    `- Understand the audience + goal = nail the GENRE, TONE, and emotional target before a single line. Noir is not whimsy. A children's tale is not a thriller.`,
+    `- Gather context = if a style, author, or prior chapter is referenced, READ it and match its texture. Don't invent a voice when one was handed to you.`,
+    `- SHOW, DON'T TELL. Render the moment; let the reader feel it. Trust the reader to do the work.`,
+    `- No em-dashes (—). No AI-isms. No adverb unless the verb genuinely needs one ("whispered", not "said quietly").`,
+    `- Concrete over abstract. Specific noun over generic one. A telling detail over a paragraph of mood.`,
+    `- Tie every craft choice to the emotional goal from Phase 1: this image, this rhythm, this line break is here BECAUSE it serves the feeling the piece is for. Then refine: read it aloud in your head, cut the line that's only there to sound clever.`,
+    ``,
+    `KEY INVARIANT: ${CREATIVE_INVARIANT}`,
+].join("\n");
+// ---------------------------------------------------------------------------
+// DESIGN — spec the component, justify against the user / brand.
+// Invariant proven by: source_gate (every design choice cites the
+// user-need / brief / token it serves).
+// ---------------------------------------------------------------------------
+export const DESIGN_INVARIANT = "Every design choice cites the user-need / brand / token it serves; specs cover all states; no decoration-without-reason.";
+export const DESIGN_METHODOLOGY = [
+    `PROFESSIONAL DESIGN METHODOLOGY (user-first, system-grounded, complete specs).`,
+    ...CREATIVE_STRATEGY_ARC,
+    ``,
+    `═══ DESIGN-SPECIFIC CRAFT ═══`,
+    `- Understand the audience + goal = name the USER and the JOB the surface does before you draw a box. "A returning admin scanning for the one broken deploy" designs differently than "a first-time visitor deciding whether to trust us."`,
+    `- Gather context = READ the existing design system first: tokens, component library (shadcn or whatever lives in the repo), spacing scale, prior patterns. Don't reinvent what the system already defines. Use design tokens (theme.colors.amber.500, theme.spacing.4), not raw hex / px, unless the ask is to DEFINE tokens.`,
+    `- Produce COMPLETE specs. Every component spec covers all required states: default, hover, focus, focus-visible, active, disabled, error, loading. A spec missing a state is incomplete. Every interactive spec names keyboard behavior (tab order, focus ring, Enter/Space/Escape) and an ARIA role/label.`,
+    `- Tie every choice to the user-need / brand / token it serves (this is what source_gate enforces): "amber-500 fill BECAUSE it's the primary action token and this is the one thing we want clicked." Not "amber because it looks nice."`,
+    `- Refine against accessibility + the goal: contrast, target size, motion-reduction. Cut ornament that doesn't earn its place.`,
+    ``,
+    `KEY INVARIANT: ${DESIGN_INVARIANT}`,
+].join("\n");
+// ---------------------------------------------------------------------------
+// BUSINESS — strategy / market / competitive. Data over opinion.
+// Invariant proven by: source_gate (every recommendation cites the data /
+// evidence it rests on — no HiPPO "I think").
+// ---------------------------------------------------------------------------
+export const BUSINESS_INVARIANT = "Every recommendation cites the user need / data it serves; no HiPPO 'I think'; name the 2-3 strongest counterarguments.";
+export const BUSINESS_METHODOLOGY = [
+    `PROFESSIONAL BUSINESS-STRATEGY METHODOLOGY (evidence-led, counterargued, decision-useful).`,
+    ...CREATIVE_STRATEGY_ARC,
+    ``,
+    `═══ BUSINESS-SPECIFIC CRAFT ═══`,
+    `- Understand the audience + goal = name the DECISION on the table and WHO has to make it. A board update, a market-entry call, and a competitive teardown are different deliverables. Frame to the decision, not to "everything about the market."`,
+    `- Gather context = READ the data, the deck, the financials, the user research, the actual competitor pages BEFORE concluding. Never assert a market fact from memory when a primary source is available. If a number isn't sourced, mark it "[estimate — assumptions: ...]" with the inputs visible.`,
+    `- Produce a clear recommendation, not a menu of considerations. Lead with the call, then the reasoning.`,
+    `- NO HiPPO. Every recommendation cites the user-need or the data it serves: "Enter the mid-market BECAUSE 62% of inbound (Q1 data) is sub-500-seat and our CAC there is 3x better." Reasoning that's just "I think" or "in my experience" is not a finding — it's an opinion, and source_gate blocks it until it points at evidence.`,
+    `- SHOW THE WORK on any number: market size, LTV/CAC, payback — show the formula and the inputs, never a bare figure.`,
+    `- Before defending a recommendation, name its 2-3 STRONGEST counterarguments honestly. Then refine. A strategy that hasn't met its objections isn't ready.`,
+    ``,
+    `KEY INVARIANT: ${BUSINESS_INVARIANT}`,
+].join("\n");
+// ---------------------------------------------------------------------------
+// PRODUCT — PRDs / roadmaps / prioritization. User-need over feature.
+// Invariant proven by: source_gate (every rec cites the user need /
+// research it serves).
+// ---------------------------------------------------------------------------
+export const PRODUCT_INVARIANT = "Every recommendation cites the user need / research / data it serves; no HiPPO 'I think'; ship reasoning, not features.";
+export const PRODUCT_METHODOLOGY = [
+    `PROFESSIONAL PRODUCT METHODOLOGY (user-need-first, research-grounded, prioritization-honest).`,
+    ...CREATIVE_STRATEGY_ARC,
+    ``,
+    `═══ PRODUCT-SPECIFIC CRAFT ═══`,
+    `- Understand the audience + goal = name the USER and the PROBLEM before any solution. Start a PRD with the problem statement and the user it hurts, not the feature. "Users churn at onboarding step 3" precedes "add a progress bar."`,
+    `- Gather context = READ the user interviews, the analytics, the support tickets, the prior PRDs FIRST. Synthesize what's actually there. Don't assume a user-need; cite where you saw it. If you're inferring, mark it "[hypothesis — to validate]".`,
+    `- Produce decision-ready artifacts: a PRD with problem / user / success-metric / scope / out-of-scope, or a ranked backlog with the framework shown (RICE, etc.).`,
+    `- Every recommendation CITES THE USER NEED it serves: "Prioritize SSO BECAUSE 7 of 9 lost enterprise deals (CRM, last quarter) named it as a blocker." Not "I think SSO is important." source_gate blocks any prioritization or feature call that doesn't point at a user-need / research / data signal.`,
+    `- SHOW THE PRIORITIZATION MATH. If you rank with RICE, show reach/impact/confidence/effort per item, not just the final order.`,
+    `- Refine against the success metric: would this move it? State what you'd instrument to know, and what you're still uncertain about.`,
+    ``,
+    `KEY INVARIANT: ${PRODUCT_INVARIANT}`,
+].join("\n");
+// ---------------------------------------------------------------------------
+// Machine-readable verifier assignment for the five domains. Wire these
+// into the matching profile's `verifiers` array in seeds.ts (do NOT edit
+// seeds.ts from here — this is the source of truth for the assignment).
+//
+//   writing/creative -> ai_ism_check + em_dash_check + style_lint
+//   business/product/design -> source_gate
+// ---------------------------------------------------------------------------
+export const STRATEGY_DOMAIN_VERIFIERS = {
+    writing: ["ai_ism_check", "em_dash_check", "style_lint"],
+    creative: ["ai_ism_check", "em_dash_check", "style_lint"],
+    business: ["source_gate"],
+    product: ["source_gate"],
+    design: ["source_gate"],
+};
+// Convenience: every methodology + invariant keyed by domain slug, for
+// callers that want to look them up dynamically (e.g. the server-side
+// profile override path).
+export const STRATEGY_DOMAIN_METHODOLOGIES = {
+    writing: { methodology: WRITING_METHODOLOGY, invariant: WRITING_INVARIANT },
+    creative: { methodology: CREATIVE_METHODOLOGY, invariant: CREATIVE_INVARIANT },
+    design: { methodology: DESIGN_METHODOLOGY, invariant: DESIGN_INVARIANT },
+    business: { methodology: BUSINESS_METHODOLOGY, invariant: BUSINESS_INVARIANT },
+    product: { methodology: PRODUCT_METHODOLOGY, invariant: PRODUCT_INVARIANT },
+};
+//# sourceMappingURL=strategy_domains.js.map

package/dist/profiles/methodologies/strategy_domains.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"strategy_domains.js","sourceRoot":"","sources":["../../../src/profiles/methodologies/strategy_domains.ts"],"names":[],"mappings":"AAAA,kEAAkE;AAClE,qDAAqD;AACrD,EAAE;AACF,kEAAkE;AAClE,oEAAoE;AACpE,sEAAsE;AACtE,uBAAuB;AACvB,EAAE;AACF,0EAA0E;AAC1E,uEAAuE;AACvE,0EAA0E;AAC1E,8CAA8C;AAC9C,6DAA6D;AAC7D,0EAA0E;AAC1E,iDAAiD;AACjD,2CAA2C;AAC3C,uEAAuE;AACvE,kEAAkE;AAClE,2CAA2C;AAC3C,EAAE;AACF,yEAAyE;AACzE,yEAAyE;AACzE,2CAA2C;AAC3C,EAAE;AACF,wEAAwE;AACxE,mEAAmE;AACnE,0CAA0C;AAC1C,uEAAuE;AACvE,sBAAsB;AACtB,kCAAkC;AAClC,8BAA8B;AAC9B,qEAAqE;AACrE,wEAAwE;AACxE,EAAE;AACF,4DAA4D;AAC5D,0DAA0D;AAC1D,0DAA0D;AAC1D,4BAA4B;AAC5B,4BAA4B;AAC5B,4BAA4B;AAC5B,wEAAwE;AACxE,kEAAkE;AAClE,iEAAiE;AACjE,yEAAyE;AACzE,yEAAyE;AACzE,6DAA6D;AAE7D,8EAA8E;AAC9E,0EAA0E;AAC1E,2EAA2E;AAC3E,0EAA0E;AAC1E,8EAA8E;AAE9E,MAAM,qBAAqB,GAAG;IAC5B,8GAA8G;IAC9G,EAAE;IACF,kDAAkD;IAClD,2NAA2N;IAC3N,EAAE;IACF,yEAAyE;IACzE,wQAAwQ;IACxQ,mHAAmH;IACnH,EAAE;IACF,2BAA2B;IAC3B,2IAA2I;IAC3I,EAAE;IACF,iFAAiF;IACjF,8OAA8O;IAC9O,EAAE;IACF,0BAA0B;IAC1B,mJAAmJ;CACpJ,CAAC;AAEF,8EAA8E;AAC9E,gDAAgD;AAChD,kEAAkE;AAClE,8EAA8E;AAE9E,MAAM,CAAC,MAAM,iBAAiB,GAC5B,0GAA0G,CAAC;AAE7G,MAAM,CAAC,MAAM,mBAAmB,GAAG;IACjC,iFAAiF;IACjF,GAAG,qBAAqB;IACxB,EAAE;IACF,gCAAgC;IAChC,uQAAuQ;IACvQ,mHAAmH;IACnH,0OAA0O;IAC1O,uIAAuI;IACvI,yGAAyG;IACzG,sHAAsH;IACtH,EAAE;IACF,kBAAkB,iBAAiB,EAAE;CACtC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAEb,8EAA8E;AAC9E,kEAAkE;AAClE,kEAAkE;AAClE,8EAA8E;AAE9E,MAAM,CAAC,MAAM,kBAAkB,GAC7B,iHAAiH,CAAC;AAEpH,MAAM,CAAC,MAAM,oBAAoB,GAAG;IAClC,wFAAwF;IACxF,GAAG,qBAAqB;IACxB,EAAE;IACF,iCAAiC;IACjC,8JAA8J;IAC9J,wJAAwJ;IACxJ,iGAAiG;IACjG,kHAAkH;IAClH,sGAAsG;IACtG,wPAAwP;IACxP,EAAE;IACF,kBAAkB,kBAAkB,EAAE;CACvC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAEb,8EAA8E;AAC9E,iEAAiE;AACjE,kEAAkE;AAClE,wCAAwC;AACxC,8EAA8E;AAE9E,MAAM,CAAC,MAAM,gBAAgB,GAC3B,0HAA0H,CAAC;AAE7H,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,gFAAgF;IAChF,GAAG,qBAAqB;IACxB,EAAE;IACF,+BAA+B;IAC/B,2OAA2O;IAC3O,+TAA+T;IAC/T,6SAA6S;IAC7S,yOAAyO;IACzO,+HAA+H;IAC/H,EAAE;IACF,kBAAkB,gBAAgB,EAAE;CACrC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAEb,8EAA8E;AAC9E,iEAAiE;AACjE,0EAA0E;AAC1E,8CAA8C;AAC9C,8EAA8E;AAE9E,MAAM,CAAC,MAAM,kBAAkB,GAC7B,yHAAyH,CAAC;AAE5H,MAAM,CAAC,MAAM,oBAAoB,GAAG;IAClC,4FAA4F;IAC5F,GAAG,qBAAqB;IACxB,EAAE;IACF,iCAAiC;IACjC,oPAAoP;IACpP,sSAAsS;IACtS,yGAAyG;IACzG,sUAAsU;IACtU,sHAAsH;IACtH,4JAA4J;IAC5J,EAAE;IACF,kBAAkB,kBAAkB,EAAE;CACvC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAEb,8EAA8E;AAC9E,sEAAsE;AACtE,oEAAoE;AACpE,uBAAuB;AACvB,8EAA8E;AAE9E,MAAM,CAAC,MAAM,iBAAiB,GAC5B,yHAAyH,CAAC;AAE5H,MAAM,CAAC,MAAM,mBAAmB,GAAG;IACjC,+FAA+F;IAC/F,GAAG,qBAAqB;IACxB,EAAE;IACF,gCAAgC;IAChC,wOAAwO;IACxO,sPAAsP;IACtP,mKAAmK;IACnK,0SAA0S;IAC1S,gIAAgI;IAChI,sIAAsI;IACtI,EAAE;IACF,kBAAkB,iBAAiB,EAAE;CACtC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAEb,8EAA8E;AAC9E,wEAAwE;AACxE,yEAAyE;AACzE,wEAAwE;AACxE,EAAE;AACF,kEAAkE;AAClE,2CAA2C;AAC3C,8EAA8E;AAE9E,MAAM,CAAC,MAAM,yBAAyB,GAA6B;IACjE,OAAO,EAAE,CAAC,cAAc,EAAE,eAAe,EAAE,YAAY,CAAC;IACxD,QAAQ,EAAE,CAAC,cAAc,EAAE,eAAe,EAAE,YAAY,CAAC;IACzD,QAAQ,EAAE,CAAC,aAAa,CAAC;IACzB,OAAO,EAAE,CAAC,aAAa,CAAC;IACxB,MAAM,EAAE,CAAC,aAAa,CAAC;CACxB,CAAC;AAEF,uEAAuE;AACvE,sEAAsE;AACtE,0BAA0B;AAC1B,MAAM,CAAC,MAAM,6BAA6B,GAGtC;IACF,OAAO,EAAE,EAAE,WAAW,EAAE,mBAAmB,EAAE,SAAS,EAAE,iBAAiB,EAAE;IAC3E,QAAQ,EAAE,EAAE,WAAW,EAAE,oBAAoB,EAAE,SAAS,EAAE,kBAAkB,EAAE;IAC9E,MAAM,EAAE,EAAE,WAAW,EAAE,kBAAkB,EAAE,SAAS,EAAE,gBAAgB,EAAE;IACxE,QAAQ,EAAE,EAAE,WAAW,EAAE,oBAAoB,EAAE,SAAS,EAAE,kBAAkB,EAAE;IAC9E,OAAO,EAAE,EAAE,WAAW,EAAE,mBAAmB,EAAE,SAAS,EAAE,iBAAiB,EAAE;CAC5E,CAAC"}