Framework fields

A framework is a note about one topic, concept or decision you teach. Sophia drafts them from your files. You can also build one: open your course, click Frameworks, then Create Framework.

Every framework has the same five parts. Press a part to see the fields inside it.

The short version. Switch to Full for every detail.

Market-entry decision

Module 4 · Entry strategy

Approved

1
Basics
Which decision it covers, the kind of reasoning it uses, and whether learners have to master it.
2
Inputs & Outputs
What the assistant has to know about the learner's case, asked outright or picked up from the conversation, and what the learner leaves with.
3
Logic Structure
The questions you'd ask, in your order. The assistant takes the learner through them one at a time.
4
Relationships
What it builds on, what it leads to, and the course files it draws from, so a learner meets your frameworks in the order you teach them.
5
Advanced
The situations it's meant for, and the ones where it doesn't hold.

The wizard has six steps: Basics, Relationships, Inputs & Outputs, Logic Structure, Advanced and Summary. A * marks a required field. The last button reads Create Framework, or Save Changes when you edit. To approve or delete a draft, see review frameworks.

Basics

Field	What to write
Name *	A specific name, like "Accept or Reject a Project".
Purpose *	One or two sentences on what the method helps a student decide. The tutor reads it to pick the right method.
Quantitative Nature *	Quantitative works with numbers. Qualitative works with judgment. Mixed uses both.
Requirements Type	Core: you teach and test it. Required: used often, not central to the exam. Optional: extra for keen students.
Modules	Pick the modules (weeks or topics) it belongs to. Click Select modules. Create modules in Files first.

Relationships

All optional. Under Link to Related Frameworks, pick other frameworks for three boxes.

Builds On: methods this one rests on.
Leads To: what comes next.
Alternatives: a method you could use instead.

Inputs & Outputs

You need at least one of each to move on.

Inputs are what the tutor needs from the student. Click Add input. Each has four fields.

Field	What it means
Name *	What you call it, like "Estimated NPV".
Type	Numeric: a number. Boolean: yes or no. Categorical: one pick from a short list. Text: free words.
Ask strategy	Required: the tutor always asks. Infer (the default): the tutor uses what the student already said, and asks only if it is missing.
Description *	What to ask for, in plain words.

Outputs are what the method produces. Click Add output. Give each a Name and a Description that says what a finished answer looks like.

Logic Structure

Framework Type * sets the shape of your logic. Changing it later clears the logic but keeps your inputs and outputs.

Type	Use it for	Example
Linear Steps	Steps in a fixed order	Working out a ratio
Decision Tree	A path that changes with the answers	Accept or reject a project
Causal Chain	Cause leads to effect	Why gross margin fell
Formula/Numerical Evaluation	Options scored on weighted criteria	Choosing a vendor
Evaluation Matrix	A grid of items against dimensions, like a SWOT	Comparing market entry options
Diagnosis Checklist	Items to check before you go on	A pre-launch check
Chart	A picture, like a bar or waterfall chart	A revenue bridge

For Chart, you describe what is plotted and how it looks. You can add an HTML example.

Under Logic Structure you have four tools.

Edit and View switch between building and a picture.
Open the ... menu next to Logic Structure and click Load example to start from a sample.
The same menu has Edit as XML. Use it to change weights and formulas for Formula/Numerical Evaluation.
Creator Note is your private note. Decision Gate is the check after the logic: do you have everything you need to decide, and does the answer look right or clearly wrong?

Most types use Add Step, Add Link, Add Row or Add Column. A Decision Tree has more boxes.

Box	What it means
Root Node	The first question.
When (edge label)	The answer that leads here, like "Yes".
Type	Condition asks another question. Action ends the path.
Label	The question or the action.
Explanation	Why this branch exists.
Loop To (Optional)	Send the student back to an earlier branch.

Add Branch allows 5 branches at the top. Add Sub-branch allows 5 under each Condition.

Advanced

All optional: When to Use, Invalid When, Prerequisites and Assumptions, Introductory Hook and Next Steps. Tags are labels only. Course search does not use them.

Summary

Check your work, then click Create Framework. A framework you build starts as Pending review, like a Sophia draft.

A small example

Box	Entry
Name	Accept or Reject a Project
Purpose	Decide whether to fund a project, using its net present value and its risk.
Quantitative Nature	Mixed
Input	"Estimated NPV", Numeric, Required
Input	"Risk within limit", Boolean, Infer
Output	"Funding decision": accept or reject, with one sentence of reasoning.
Framework Type	Decision Tree
Root Node	Is the NPV above zero?
Branch	When "No": Action, "Reject the project".
Branch	When "Yes": Condition, "Is the risk within limit?"
Sub-branch	When "Yes": Action, "Accept the project".
Sub-branch	When "No": Action, "Send for a risk review".