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, fetch/cache, graph kernels, and partitioning engines | series/tools-infrastructure.md |
| Applied Systems | sports analytics and infrastructure-design workbenches | series/applied-systems.md |
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, 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: giodl@microsoft.com
- GitHub: @giodl73-repo