# Site

## Pages

- [Page not found](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/404/): That page doesn't exist, or it has moved since you last looked
- [Assessment](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/assessments/): Every piece of graded work in the course, what it is worth, and when it is due.
- [The Dig Report](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/assessments/dig-report/): Survey your dig site — its stratigraphy, its tool inventory, its architecture, and your first hypothesis for how it died.
- [The Forensic Analysis](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/assessments/forensic-analysis/): Go deeper — the documentation layer, the oral history, and a revised cause-of-death diagnosis supported by the full weight of your evidence.
- [The Exhibit](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/assessments/the-exhibit/): Your complete excavation — the site, the findings, the diagnosis, the ethics, and the restoration — presented for an audience that has never seen the codebase.
- [Lectures](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/lectures/): What is covered, week by week, and which topics each lecture draws on.
- [What makes software dead?](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/lectures/week-01/): The opening lecture — what software archaeology is, why abandoned code matters, and how to choose a dig site.
- [Dating techniques](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/lectures/week-02/): How to read a commit history as geological layers — construction, maintenance, decay — and what the boundaries between them reveal.
- [Reading the inscriptions](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/lectures/week-03/): Commit messages as primary sources — what they reveal about team culture, communication norms, and working conditions.
- [The tool kit](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/lectures/week-04/): Dependency manifests as archaeological artefacts — what a project's chosen tools reveal about its era, its team, and its assumptions.
- [Reconstructing architecture](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/lectures/week-05/): Reading a project's structure as a site plan — what directory layout, naming conventions, and entry points reveal about how the team thought.
- [What the docs do not say](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/lectures/week-06/): Documentation as archaeological evidence — what was written, what was maintained, and what the gap between them reveals.
- [Finding the people](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/lectures/week-07/): Oral history methodology for software — finding former maintainers, the ethics of contact, and what living sources reveal that artefacts cannot.
- [Cause of death](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/lectures/week-08/): A taxonomy of software failure — why projects die, how to tell the modes apart, and why the diagnosis matters.
- [Archives and time capsules](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/lectures/week-09/): Software preservation — the institutions that try, the difference between archiving code and preserving the ability to run it, and what still gets lost.
- [The ethics of digging](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/lectures/week-10/): Whose code is it — licence vs intent, forking as continuation vs appropriation, and the question no licence file answers.
- [Minimum intervention](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/lectures/week-11/): Restoration practice — reviving one piece of dead software with the smallest possible change, the way a conservator stabilises a painting.
- [The exhibit](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/lectures/week-12/): Presenting your excavation — how to make an audience care about a codebase they have never seen and will never use.
- [People](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/people/): Who teaches the course, and how to reach them.
- [Kai Nakamura](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/people/kai-nakamura/): The course tutor — a practising developer who maintains two open-source projects they inherited from strangers who had moved on.
- [Maren Voss](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/people/maren-voss/): The course convenor — a software historian who came to computer science through library science, now studying what version control reveals about how teams actually work.
- [Policies and support](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/policies/): The course-wide rules for late work, extensions, academic integrity and getting help — including the ethics guidelines for oral-history contact.
- [The dead repo](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/sessions/01-the-dead-repo/): Survey — what makes software dead, how to tell, and how to choose a dig site you will spend the semester excavating.
- [Stratigraphy](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/sessions/02-stratigraphy/): Dating techniques — reading the commit history as geological layers to identify periods of construction, maintenance, and abandonment.
- [The inscriptions](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/sessions/03-the-inscriptions/): Reading the inscriptions — commit messages as primary sources for a team's communication norms, morale, and working patterns.
- [Tool inventory](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/sessions/04-tool-inventory/): Dependency analysis — reading package manifests as archaeological tool kits to date the project and reconstruct the technological era it belongs to.
- [Architecture from ruins](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/sessions/05-architecture-from-ruins/): Spatial analysis — reconstructing the mental model the original authors had from directory structure, entry points, and file naming conventions alone.
- [The documentation layer](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/sessions/06-the-documentation-layer/): Epigraphy — reading the writing the authors left behind, and diagnosing the project from the gap between what the docs promise and what the code does.
- [Oral history](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/sessions/07-oral-history/): Interview technique — how to find former maintainers, how to approach them, and what you learn that no artefact can tell you.
- [Cause of death](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/sessions/08-cause-of-death/): Forensic diagnosis — why projects die, a taxonomy of failure modes, and how to distinguish burnout from ecosystem shift from silent success.
- [Preservation](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/sessions/09-preservation/): Conservation — the difference between preserving code and preserving the ability to run it, and the institutions that try to do both.
- [Restoration ethics](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/sessions/10-restoration-ethics/): Whose code is it — the ethics of forking abandoned work, the difference between licence and intent, and when revival is continuation vs appropriation.
- [The restoration](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/sessions/11-the-restoration/): Minimum intervention — reviving one piece of your dig site the way a conservator restores a painting: stabilise, do not repaint.
- [The exhibit](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-anpham-09/sessions/12-the-exhibit/): Presentation — your complete excavation presented as a museum exhibit, for an audience who has never seen the codebase.