What this shows: How the same three files evolve across a real collaboration over 6 weeks.
Most examples show you a snapshot of what files look like. This example shows the movie — how the files change as a project progresses, decisions accumulate, and errors get caught and fixed.
New users often ask: "When do I update these files? What does updating actually look like?" This example answers both questions with a concrete 6-week timeline.
Project: Building a small SaaS product (a scheduling tool for freelancers)
Owner: Daniel Torres (freelance developer, building solo)
AI role: Architecture decisions, code review, user research synthesis, copy
Duration shown: 6 weeks (Week 1 → Week 6)
| File | What it shows |
|---|---|
week-01-snapshot.md |
The three files at the very start — sparse, mostly placeholders |
week-03-snapshot.md |
After first major decisions and one correction |
week-06-snapshot.md |
After a pivot, two failures caught, and scope change |
evolution-commentary.md |
What changed between each snapshot and why |
- Start sparse, grow naturally — Week 1 files are short. That's correct.
- Decisions accumulate over time — The decisions log is the most valuable part of the running document
- The strategy master rarely changes — But when it does, it matters
- Failure log grows with the project — Every project has failures. Logging them is the practice.
- Numbers file gets more specific — It starts vague, becomes precise as real data arrives
Part of LC-OS-Project. See root README for full documentation.