The portfolio should survive the app that inspired it
On 19 July, I brought in a VisualMind map of the AEGNTIC GitHub profile and asked to turn it into a portfolio. Then I added the part that mattered: it shouldn't depend on that app continuing to exist.
Retrospective field note for 2025-07-21. Reconstructed in November 2026 from dated sources, not originally published on the archive date.
On 19 July, I brought in a VisualMind map of the AEGNTIC GitHub profile and asked to turn it into a portfolio. Then I added the part that mattered: it shouldn’t depend on that app continuing to exist.
I also asked to start simple, avoid errors, iterate and test. That wasn’t a request to make it boring. It was a request to build the thing in an order that could actually work.
ChatGPT agent had arrived two days earlier. More capable assistants made ambitious builds easier to imagine. They didn’t make the resulting data any less important to own and recover.
For this portfolio, the projects, descriptions, links and relationships should be separate from the display. Replace the canvas, replace the library, replace the hosting. The information should survive those decisions.
Before adding spectacle, I’d want to see that a visitor could find a project, open it, and understand how it connected to the rest. Then export the underlying information and prove it could be restored.
The chat records the brief, not a launch. A prototype screenshot wouldn’t settle the independence question anyway. The test is whether the portfolio still belongs to us when the original service is no longer part of the picture.