anton415 AI-first engineering

Project case study

Orchestrator

A module for visualizing and managing the AI-assisted engineering workflow itself — ChatGPT for analysis, Claude for architecture, Codex for implementation, with approval gates and GitHub as source of truth. Currently frozen.

Frozen
Problem
An AI-assisted engineering workflow that lives only in a developer's head is unreviewable, unrepeatable, and hard to teach. The interesting artifact isn't the code — it's the workflow that produced it.
Solution
A module slice that captures the workflow as data: which agent ran on which spec, which approval gate was crossed, which PR shipped. The slice exists in the repository; the live UI is frozen until the workflow itself stabilizes.
AI-first angle
The module is the AI-first workflow made inspectable. It records spec → architecture → implementation → review handoffs and the human approval gates between them. The orchestrator is the meta-module of the hub.
Tech stack
Go 1.25, PostgreSQL 16, n8n, chi, GitHub Actions
Links
Repository

Status

Frozen. The module slice exists in the repository (internal/orchestrator/) and the production stack still runs the supporting n8n service, but the module is not under active development.

The workflow it describes

  1. ChatGPT — problem analysis, scope drafting, specification writing.
  2. Claude Code — architecture review, ADRs, layer-respecting implementation, codebase navigation.
  3. Codex — visual polish and UI iteration on the frontend.
  4. Human (Anton) — approval gate on every PR; sole owner of merges to main.
  5. GitHub — source of truth for what shipped.

Boundaries that matter (layer dependencies, public/private isolation, deploy guardrails) are enforced by CI rather than by review discipline. An agent cannot accidentally cross a boundary the build refuses to compile.

Why it’s frozen

The workflow itself is still evolving. Building a UI on top of a workflow that changes monthly is premature. The module thaws when the workflow stabilizes and the orchestrator has a real job to do beyond recording history that already exists in git log.

What’s already in place

  • Backend module slice (internal/orchestrator/).
  • n8n integration scaffolding and a callback-token-protected endpoint.
  • Frontend module shell.

Repository

github.com/anton415/anton415-hub — orchestrator slice lives under internal/orchestrator/.