A repository built against disappearance: of projects, operating knowledge, and the reasons behind decisions.
I designed project-FEAR as a shared foundation for operational documentation, agent context and the public stories in this portfolio.
The problem
When notes, code and operating knowledge drift apart, returning to a project becomes an investigation. I needed one place to understand what exists, why it was built and how to recover it when something fails.
Design & implementation
The repository connects inventories, architecture notes, service records and runbooks through a regular Markdown structure. People and agents can follow the same map from a project to its dependencies and operating procedures.
Raw notes are edited into canonical project records, then into summaries and portfolio pages. Operational detail stays private; public stories are written for a different audience.
In use today
Archivist makes the documentation available to Hermes as a versioned source for investigations. In a real run, the agent used the index and inventory to locate services, inspect their live state and check its findings. The repository provides a map, not a substitute for current evidence.
What it does
- Linked project records, inventories and recovery procedures
- Versioned documentation available to agents through Archivist
- A separate editorial layer for public portfolio pages
Why I built it
I want to return to an old project without reconstructing its history from scratch. Keeping the decisions alongside the system makes the work easier to resume and maintain.
