Guide A — Foundations¶
The Record-Keeping Tradition Behind Vestigia¶
What This Document Is¶
This document establishes the foundation beneath Guide A.
It is not a set of instructions. It explains why the practice of keeping a working record during a project has a long history, where Vestigia sits within that tradition, and why it matters for the kind of work you are doing now.
Read this once before you begin. Return to it if the habit ever starts to feel like overhead rather than investment — a reminder of why the effort is worthwhile.
The Traditional Log Book¶
The practice of maintaining a working record throughout a project is not new.
Across engineering, science, research, and professional practice, students and practitioners have long been expected to document their work as it progresses — not at the end, but continuously. These records have taken different forms across disciplines and institutions:
◆ the engineering notebook
◇ the lab book
◆ the project diary
◇ the field journal
◆ the design log
The names differ. The underlying purpose does not.
What these records were expected to contain¶
◆ dated, sequential entries
◇ evidence of decisions and the reasoning behind them
◆ documentation of both progress and failure
◇ notes on meetings, instructions received, and direction changes
◆ a traceable account of intellectual ownership
In many professional and academic contexts, these records carried weight beyond assessment — they were legal and professional artefacts. They answered a question that still matters:
Who thought of this, when, and why?
Why the Tradition Has Broken Down¶
The intent of the log book persists in modern final-year project expectations. The practice, however, has become misaligned with how students actually work.
Common problems include:
◆ records reconstructed after the fact, from memory
◇ documentation scattered across tools — Git commits, chat threads, notebooks, emails
◆ reflection delayed until submission time, producing generic or sanitised accounts
◇ log books treated as compliance artefacts rather than thinking tools
◆ difficulty translating raw working notes into final reports and presentations
This is not a failure of students. It is a mismatch between a tradition designed for one kind of work environment and the reality of contemporary, distributed, digitally mediated project work. A format designed for a single researcher working in a single location does not map cleanly onto a group of four students working across GitHub, WhatsApp, VS Code, and a shared document.
What Vestigia Does¶
Vestigia does not reject the log book tradition. It refines its purpose and removes the friction that has made the tradition feel irrelevant to modern students.
Guide A preserves what mattered about log books — evidence, thinking, continuity — while freeing you from format assumptions that no longer serve you.
What remains the same¶
◆ records are dated and sequential
◇ decisions and their reasoning are documented
◆ failures and dead ends are captured honestly
◇ the record belongs to the person doing the work
What changes¶
◆ the medium is your choice — digital, markdown, notebook, whatever works
◇ you record meaningful moments, not everything indiscriminately
◆ entries serve two audiences: yourself during the work, and readers after it
◇ the record feeds directly into your professional showcase
The result is a practice that is lighter, more honest, and more useful than the log books it replaces.
The Two Audiences of a Good Record¶
One of the most important shifts Vestigia asks you to make is this:
Write as if your future self will need to explain this to someone else.
Your entries are primarily for you — to think, to track, to reflect. But they should be legible enough that:
◆ you can return to them weeks later and understand what you meant
◇ they can be selectively shared with a supervisor or teammate
◆ they can feed directly into report sections without total rewriting
◇ they support your individual showcase at the end of the project
This dual awareness — private thinking tool and professional record — is what distinguishes a Vestigia entry from a diary.
A diary entry says: I worked on the authentication module today. It was frustrating.
A Vestigia entry says: I spent three hours on the token refresh logic. The failure turned out to be that the mobile client and web client handle token expiry differently — I had assumed they would synchronise automatically. I'll need to handle expiry independently on each surface.
Both are honest. Only one is useful to your future self, your supervisor, and your showcase.
Individual Records Within Group Projects¶
Most final-year projects involve group work. Vestigia is designed with this in mind.
Your records are individual. Your project may be collaborative. This is not a contradiction — it mirrors professional practice exactly.
In industry, engineers keep personal notebooks. Developers keep personal notes. Teams produce shared deliverables. Both exist simultaneously, and neither replaces the other.
Your individual Vestigia records serve you specifically:
◆ they document your thinking, your decisions, your contribution
◇ they protect your reflection from being generic or reconstructed
◆ they give you defensible, specific material for individual assessment components
◇ they prepare you for interviews, portfolios, and professional conversations
At the same time, a group culture of good individual record-keeping tends to produce better collective outcomes — clearer decision trails, less repeated discussion, more grounded supervision meetings.
On Agile projects
If your project runs in Agile sprints, your sprint ceremonies already create natural recording moments. Use them. A sprint retrospective entry in Vestigia is more specific and more useful than a generic reflection written at submission time. Your stand-up notes become the raw material for your work-performed entries. The sprint boundary is a reliable trigger for a substantive record.
Where Guide A Fits in the Vestigia System¶
Vestigia is organised around two phases:
Guide A is the first phase. It runs during the project. It asks: what is worth capturing, and how should I capture it?
Guide B is the second phase. It begins when the project ends. It asks: what do I do with what I recorded?
Guide B depends on Guide A. The quality of what you can present professionally later is directly shaped by the quality of what you record now. Students who arrive at Guide B with rich, specific records have something to work with. Students who arrive with vague or reconstructed notes face a much harder task.
This is why Guide A is where the work actually begins.
A Note on Discipline¶
Guide A is written primarily with Computer Science, IT, and Engineering students in mind — disciplines where the log book tradition is most deeply rooted, and where Agile methodology, client-facing projects, and full-stack development create the most immediate need for intentional record-keeping.
The practice is transferable. If your project involves decisions, iteration, and learning over time — regardless of discipline — Guide A applies to you. The thinking habits it builds are not subject-specific. They are professional.
In Summary¶
Vestigia Guide A is a modern form of a long-established professional practice. It preserves what log books were always meant to do:
◆ create a traceable record of thinking
◇ document decisions at the moment they are made
◆ capture failure and revision honestly
◇ produce material that supports future explanation and reflection
It removes what made log books difficult:
◆ rigid format requirements
◇ the expectation that everything must be recorded
◆ the assumption of a single, shared medium
What remains is the habit that matters:
Pay attention to your work while you are doing it.
Write it down. Date it. Be honest.
Your future self will thank you.
Continue to The Guide to begin the practice.