# Notes

*How to structure papers* (from u/winstonchan270707)

paper 1 10 marker:

1. definition of key terms in question
2. draw a diagram with a hypothetical example, e.g. Market for EVs in US
3. explain your diagram, and relevant economics in relation to your hypothetical example

paper 1 15 marker:

1. definition of key terms in question
2. draw a diagram(s) with a *real world example (s)*
3. explain diagram, relevant economics in relation to the example
4. evaluation

* the simple structure for simple questions (eg macro policy) is pro con pro con
* for evaluation, you can use PEEL - evidence can be things you researched for your example, diagram e.g. consumer and producer surplus change
* for evaluation, refer to stakeholders, long run/short run, assumptions, priorities to the government

1. conclusion

paper 2 15 marker: also a definition, diagram, explanation, evaluation but constantly and consistently refer to the case study, and that should be some/most your evidence as well

paper 3 10 marker: no need diagram, just definition of key terms/introduce policy, explanation, 1 pro, 1 con

\*if the question doesn’t have a diagram (e.g. Explain the costs of poverty), then it is not needed \*\*some 15 markers have “evaluate whether XYZ is the *most effective* way..” if you see that, you should compare it with another/other policies in your evaluation


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://shagun.gitbook.io/mystuff/sl/economics/notes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
