State of Dev - Week of August 3, 2026

The plan this week was simple.

Continue working on the Game Engine.

Unfortunately, somewhere between "expand the campaign system" and "I wonder if AI should generate JSON instead of TypeScript," several entirely new projects appeared, the blog quietly promoted itself to infrastructure, Git started looking suspiciously like a deployment platform, and AgentKit developed career ambitions.

None of this was scheduled.

I'm beginning to suspect the repositories are collaborating behind my back.

Development Completed

SubZeroDev.GameEngine

The engine itself behaved.

The campaign system did not.

What started as "let's add more campaigns" quietly evolved into an AI content pipeline where structured JSON replaces handwritten code, CI validates everything, and the engine simply consumes whatever fresh insanity gets committed next.

Apparently the engine's new hobby is eating data.

SubZeroDev.AgentKit

AgentKit continued discovering what it wants to be when it grows up.

The more work goes into it, the less it resembles another AI coding tool and the more it resembles that engineer who quietly fixes everything while asking uncomfortable questions about your architecture.

SubZeroDev.GitService

Git Service should not pretend to be intelligent.

It should move repositories around, open pull requests, report status, and generally behave like competent infrastructure.

The AI can keep making questionable life choices somewhere else.

Blog Platform

The blog somehow became:

• an engineering journal;
• a publishing workflow;
• architecture history;
• AI memory;
• and eventually another source of content.

It was supposed to be a website.

Project Status

Project	Status
Game Engine	Near MVP
Story Graph	Active Development
Campaign Pipeline	Escalating
AgentKit	Becoming Self-Aware (Probably Not)
Git Service	Architecture
Blog Platform	Publishing Conspiracies

Major Milestones

• AI stopped writing code and started writing content.
• Git became suspiciously close to being the deployment strategy.
• "I'll just make one small improvement" was once again proven to be fiction.

Conclusions Reached Entirely By Accident

• Git solves more problems than expected.
• AI should generate structured data whenever possible.
• MCP keeps appearing in every architecture diagram whether invited or not.
• Every project eventually discovers another project hiding inside it.

Things That Got Out of Hand

• Campaign generation.
• AI review agents.
• Trading automation.
• Blog automation.
• Story packs.

Scientists continue searching for the point where one project becomes seven.

Challenges

Choosing what not to build.

So far this remains largely theoretical.

Project Statistics

This journal focuses on why things happened.

For live repository statistics:

https://github.com/The-Running-Dev

Notable Quotes

"The absence of a plan is the plan."

"We don't follow roadmaps. Roadmaps follow us."

"Content is data."

Next Priorities

• Finish the campaign system.
• Expand the campaign library.
• Continue AgentKit.
• Keep refining Git Service.
• Resist creating three additional projects.

Looking Ahead

Every week starts with a perfectly reasonable objective.

By Friday, I've accidentally built half a platform while insisting to myself that I was "just making one small change."

I'm no longer convinced I'm designing this ecosystem.

I think it's assembling itself and occasionally asking me to type.