Guide B — Foundations¶
From Records to Meaning¶
What This Document Is¶
This document establishes the foundation beneath Guide B.
It explains why interpretation is a distinct skill from documentation, what Guide B asks of you that Guide A did not, and how the two phases of Vestigia work together to produce something professionally useful.
Read this before beginning Guide B proper. The framing here shapes everything that follows — students who skip it tend to approach the extraction work with the wrong expectations and get stuck earlier than they need to.
The Transition From Guide A to Guide B¶
Guide A helped you capture the work as it happened.
Over the course of your project, you recorded decisions, changes, problems, progress, and learning in motion. If you used Guide A well, you now have a body of material that reflects how your project actually unfolded — not how you wish it had, and not a sanitised summary written from memory.
Guide B begins at a different point.
It assumes you have:
◆ traces of thinking accumulated over time
◇ records of activity, decisions, and reflection
◆ fragments of insight, some clear and some incomplete
The purpose of Guide B is not to add more content to what you have. Its purpose is to help you decide:
◆ what matters within everything you recorded
◇ what explains the project most clearly and honestly
◆ what demonstrates your growth and contribution
◇ what should be visible to others — and what should remain private
This is the transition from recording to interpreting. It requires a different kind of effort. Recording is largely about paying attention. Interpreting is about making judgements — and judgements can be wrong, revised, and improved. That is expected and appropriate.
Why Interpretation Is Necessary¶
A common assumption among students is that thorough documentation will automatically produce a strong final narrative. It does not.
Raw records are detailed, chronological, and contextually meaningful to you while you are in them. But a showcase, portfolio entry, CV summary, or professional narrative must be something different:
◆ selective rather than comprehensive
◇ coherent to someone who was not there
◆ structured around what matters, not around what happened first
◇ grounded in evidence, not just activity
The gap between a record and a showcase is not filled by writing more. It is filled by making deliberate choices about what to keep, what to foreground, and what to set aside.
Guide B exists because this act of curation is itself a professional skill — one that rarely gets taught explicitly. Most students either reproduce everything (producing noise) or summarise vaguely (producing nothing useful). Guide B offers a middle path: extract what is significant, connect it to evidence, and present it with honesty and clarity.
Records Are Not the Same as Evidence¶
This distinction is central to Guide B, and worth being precise about.
Records¶
Your Guide A records capture what happened, when it happened, and how you experienced it at the time. They are often rough, personal, exploratory, and incomplete. They were written for you — to think, to track, to reflect.
Not all of them are suitable for presentation. That is expected and appropriate. A record that says "spent three hours on this, no idea what is wrong, will look at it tomorrow" is an honest entry that served you at the time. It is not showcase material. But it may point toward something that is.
Evidence¶
Evidence, in the context of a professional showcase, explains why decisions were made, how problems were resolved, what was learned, and how your contribution can be demonstrated to someone outside the project.
Evidence is:
◆ chosen — not everything, but the right things
◇ contextualised — given enough background to make sense
◆ explained — connected to outcomes, not just described
Guide B teaches you how to move from raw records to defensible evidence. This movement is not about polishing or inflating. It is about selecting honestly and explaining clearly.
Two Sources of Material¶
Your final showcase should draw from two distinct sources. Understanding the difference between them — and why both are necessary — is the most important preparation for the extraction work ahead.
Source 1 — Your Vestigia Records¶
These are your working traces. They capture how you thought — your decisions, pivots, failures, reflections, and learning in motion. They are personal and contextual. They answer the question:
What was I actually thinking while I was doing this?
This is the layer most students do not have access to at the end of a project, because they never captured it while the work was happening. If you used Guide A, you have it. This is its value.
Source 2 — Your Project Artefacts¶
These are the formal outputs your subject required: proposals, reports, designs, code repositories, prototypes, evaluations, presentations, meeting minutes, sprint documentation, WIL records. They represent what was delivered — structured, assessed, and shared with supervisors, clients, or markers.
They answer the question:
What did the project actually produce?
Why Both Matter¶
Using only artefacts produces showcases that are generic, descriptive, and thin on reflection. The work is listed but not explained. A reader can see what was built but has no insight into the thinking behind it — and cannot distinguish your contribution from anyone else on the same project.
Using only Vestigia records produces showcases that feel personal but lack credibility. There are no outcomes to point to. Claims cannot be verified. The thinking is present but the work is invisible.
Guide B connects the two. Your records provide the thinking; your artefacts provide the evidence. Together they produce something that is both honest and defensible.
If you skipped Guide A
If you did not keep Vestigia records during the project, your project artefacts become your primary source for reconstruction. Work backwards from formal documents — proposals, reports, sprint logs, design documentation — to recover the decisions and reasoning they contain. The extraction will be harder and the showcase less specific, but the process is the same. Use the prompts in Guide B — Extraction Prompts to structure your thinking.
Individual Ownership in Collaborative Projects¶
Most final-year projects are partly or fully collaborative. Guide B is, despite this, always concerned with the individual showcase.
This is intentional — and it is not a contradiction.
When you apply for roles, share work on LinkedIn, build a portfolio, or discuss your experience in an interview, you are always presenting as an individual. You cannot present your group. Employers are asking what you did, what you decided, what you learned.
Guide B will help you:
◆ extract your contribution honestly from shared work
◇ explain your decisions without erasing your teammates
◆ link to collective artefacts appropriately
◇ avoid both overstating and underselling your role
This balance — individual narrative within collective context — is a professional skill. Guide B makes it explicit, and the Integrity and Attribution document at the end of Guide B addresses it in detail.
What Guide B Does Not Do¶
Guide B deliberately avoids:
◆ templates to fill in
◇ prescribed section headings for your showcase
◆ fixed formats or platform requirements
◇ examples of finished showcases to model your work on
This is to protect the authenticity and disciplinary variation that make individual showcases genuinely valuable. If Guide B offered a structure to copy, students would copy it — and produce something that looks like a Vestigia showcase rather than a reflection of their actual project and their actual thinking.
Your final artefact should sound like you, not like a framework.
What Guide B Will Help You Do¶
By working through Guide B, you will be able to:
◆ identify which moments in your records are worth presenting
◇ extract learning and decisions that are genuinely significant
◆ connect your thinking to the evidence in your project artefacts
◇ present your contribution honestly and specifically
◆ prepare material suitable for portfolios, CVs, LinkedIn, interviews, and professional showcases
All of this without starting from scratch, and without reconstructing a project you have almost certainly already moved past.
A Note on Restraint and Integrity¶
Good interpretation includes leaving things out.
Not every difficulty needs to be public. Not every note deserves an audience. Not every part of your project will reflect well on you — and that is acceptable and normal.
What Guide B asks is that what is shown is accurate, reflective, and defensible.
Restraint is not dishonesty. It is professionalism. Integrity does not mean exposing everything — it means representing what you do share with honesty and precision.
In Summary¶
Guide A helped you build a record of the work.
Guide B helps you decide what that record means — and how to present it to people who were not there.
This is the moment where traces become meaning, work becomes narrative, and experience becomes evidence.
Continue to From Records to Narrative to begin the extraction process.