bamr87.github.io: a portfolio that runs on data, not memory
One tile on my portfolio's stats strip is typed by hand: years building. The rest are generated nightly; one failed fetch stops the run.
The Quest Log
Every level and side quest, one deep dive at a time
My repositories, written up as levels and side quests, one per deep dive: what each one is, how it works, and what the daily review found
Table of Contents
The Quest Log in Badwill Impairment drew the map: eight levels, more than thirty side quests.
This is the walkthrough. One repository at a time, with screenshots, the architecture, and a status report nobody has polished for the board.
How the log is kept
A daily review routine, the deep dive, takes one of my repositories each day, every active one once per 42-day cycle. The first cycle started on 30 October 2026.
An AI agent reviews the repository, scores it out of 100, files issues and opens pull requests. It never merges. I do.
The plan: every repository that gets its deep dive also gets an entry here. What it is, who it is for, how it works, and what the review found, open issues included. Built things are called built. Plans are called plans.
A corporate status report rounds everything to a color. This one gets a score out of 100 once the deep dive records it, and links to the open issues.
The entries
Newest first.
bamr87/bamr87: 44 projects run from one registry
The status deck is always green. My control plane leads with its own red, and the AI auditor whose ledger it keeps gave it a 78.
IT-Journey: learn IT as quests you run in your own terminal
Corporate training ends in a certificate nobody reads. My curriculum sends AI agents through it and publishes its own failing grade.
Follow along
Each entry is also drafted as a LinkedIn post, and it goes out only after I approve it. To catch them as they land, follow Amr Abdel-Motaleb on LinkedIn.
The whole fleet is public at github.com/bamr87/bamr87.