Open product module
Method cards
Versioned, teachable ways to clarify, generate, compare, reframe, or stress-test a decision.
Why it exists
A method card turns a named thinking tradition into a bounded interface: when it helps, what it asks, and what result it should produce.
Inputs and outputs
Inputs
- Current activity state
- A compatible task facet
- A method lens or Auto mode
Outputs
- A method explanation
- A small sequence of prompts
- A measurable decision artifact
Visual flow
- Read the task facet
- Check applicability and contraindications
- Run the card’s smallest useful move
- Return the requested artifact
- Record only bounded method signals
Practical example
Situation
Several options exist, but the person cannot say what “best” means.
Result
A weighted-criteria card makes criteria and trade-offs visible before a shortlist is chosen.
Limitations
- A card is not a claim that the method always works.
- Cards do not expose private model prompts or effectiveness data.
- A mismatch must fall back explicitly rather than silently changing the task.
Open and closed boundary
Open here
Card names, educational explanations, applicability concepts, and standalone templates are public.
Kept private
Runtime ranking weights, private prompts, and effectiveness metrics remain product internals.