I build public systems in series: each repo is a concrete artifact, and each series is the story that explains why those artifacts belong together. The implementation through-line is Rust: even when the artifact is a paper, corpus, game, or design lab, the durable machinery tends to become a Rust CLI, library, or verifier.
Public repos in this portfolio use ROLES,
the .roles convention for repository-local review panels.
Day job: VP of Engineering at Microsoft on Agents 365. Everything here is built outside that.
AI-first development is not about coding faster. It is about making the parts of engineering that usually get skipped actually happen: research, simulation, review, validation, critique, and rework before the wrong design hardens.
The pattern is consistent across the portfolio:
- A repo produces artifacts: code, papers, games, chapters, scorecards, maps, or packages.
- Skills and reviewers evaluate those artifacts against an explicit rubric.
- Findings become evidence.
- Repeated evidence becomes a stronger process, a new skill, or a new repo.
The series below are the public map.
| Series | What it contains | Start here |
|---|---|---|
| AI Methodology | decision intelligence and simulated expert review | series/ai-methodology.md |
| Games Design | puzzle hunts, D&D, board games, escape rooms, and world-building simulators — with shared simulation and UX infrastructure | series/games-design.md |
| Knowledge Systems | civilization, reference, and local-production corpora | series/knowledge-systems.md |
| Design Labs | visualization, writing, and music scoring labs | series/design-labs.md |
| Election Systems | redistricting, district plans, count evidence, and audit packages | series/election-systems.md |
| Standards & Protocols | portable conventions, identifiers, context-transfer formats, and review-panel specs | series/standards-protocols.md |
| Tools & Infrastructure | markdown, context selection and algebra, harness replay, fetch/cache, graph kernels, and partitioning | series/tools-infrastructure.md |
| Applied Systems | sports analytics and infrastructure-design workbenches | series/applied-systems.md |
These four repos show the portfolio's artifact-to-context through-line: ROUTE produces evidence-heavy work; CROP selects relevant source context; LATTICE closes and explains that context; FLETCHER records and replays how an AI harness used it.
| Repo | What it demonstrates |
|---|---|
| CROP | Graph-cut context selection and provenance-aware corpus tooling. |
| LATTICE | Deterministic context closure, meet/join, budgets, frontiers, and receipts. |
| FLETCHER | Replayable AI harness events, checkpoints, and LATTICE handoffs. |
| ROUTE | Evidence-gated Interstate 2.0 research, simulation, maps, and design. |
The public infrastructure family now extends from highways into rail, connectivity, ports, water, and aviation. See Applied Systems for the full map and evidence boundaries.
The repos are not isolated experiments. They form layers:
- Methodology repos define how decisions are researched and reviewed.
- Artifact repos produce serious work in games, knowledge, civic systems, and design.
- Infrastructure repos make those artifacts reproducible: stable markdown addresses, compact context-transfer formats, repo-local review panels, corpus compilers, context packs, context algebra, replayable harness events, finished shared fetch/cache substrate for ROUTE, BISECT, and ICELINES, graph kernels, plan packages, audit ledgers, and shared game simulation and UX engines (MUDDLE, RALLY, COURT, RACKET).
That is the through-line: build the artifact, build the evaluator, then promote the reusable Rust substrate when more than one system needs it.
- Email: giodl73@gmail.com
- GitHub: @giodl73-repo