Distinction between Project Instructions and Project Files

Here’s a clear way to see the difference — it’s about function vs. substance.

1. Project Instructions → The “How”

Function:
- They are the operational playbook for how we run the project.
- They tell me what to do, how to do it, in what order, and to what standards.
Content type:
- Purpose, scope, roles, workflow, quality standards, review process.
- Decision rules — how to select sources, how to judge relevance, how to move between phases.
Example (from your current work):

In the literature review phase, select at least five external sources published in the last three years from academic journals, reputable news outlets, or recognised think tanks. Summarise each source in under 200 words, highlighting relevance to key dangers and potential mitigations.

Function:
- They are the knowledge base we draw from to build content.
- They give me the substantive material — facts, quotes, data, ideas — to work with.
Content type:
- Reports, notes, essays, quotes, background context, case studies, existing analyses.
- In this project: ethos documents, AI warnings, contextual scaffolding papers.
Example (from your files):

_“There is a risk that students might outsource their thinking to AI and lose or not acquire the ability for critical thinking”warnings_about_ai.

Project Instructions → procedural framework; defines the rules of engagement.
Reference Material → substantive input; provides the raw material to be analysed and synthesised.

You can think of Instructions as the recipe, and Reference Material as the ingredients.