José Miguel Gómez

Back to the home page

Mirador

Every repository at a glance, and what needs your decision today

The code lives in a private repository; this sheet and the demo, when there is one, show the work.

Status
Now showing
Type
Developer tool
Running time
November 2026 – November 2026
Role
Sole engineer
Domains
developer productivity, project tracking, observability
Cast
TypeScript, Node, Astro, Vitest, JSON Schema, Git, Github Cli, Cloudflare Pages

Context and problem

Observability dashboard for the whole portfolio (public view on synthetic data).

With 450+ repositories advanced by different AI agent conversations, the real state of each project is scattered across task files, state notes and git, so decisions, blockers and unpushed work get lost (assumption: one person steering 10+ active projects in parallel).

Screens

How it was built

147 tests · 1 audit

Source: Trysac/00c-mirador portfolio.yaml (line 23), dated 21 November 2026.

Results with dated evidence

Outcomes as stated in the manifest; the measured figures are the ones with a date.

  • Reads 455 projects in about 12 s with zero model calls and 98.5 % of free-text statuses normalized.
  • Answers what needs a decision today in under a minute: ranked waits, blockers, expiring resources and unbacked work.
  • A static site with one page per project and a 63-line brief a phone assistant can read.
  • Independent audit: 2 blockers found and fixed; 147 tests; axe 0 violations; Lighthouse 100 performance and accessibility on the demo.

Case study in preparation

The full case study adds these sections when it is published:

  • Constraints
  • Architecture diagrams (C4 context and containers)
  • Three key decisions
  • What went wrong
  • Demo video
  • What I would do differently

Highlights

zero token, read only scanner, tracking standard, static site, synthetic demo