gFactory
an attempt. building in public.

by Rupreet · solo build

gFactory is my attempt at an autonomous software factory: a way to keep more than one product moving without personally pushing every task across the finish line.

I'm building it in the open, sharing what works, what doesn't, and what actually makes it out the door.

A builder sketches a product plan while several available agents wait for work packets.

What gFactory actually does

Every project breaks down into work packets that move through five stages: plan, break down, build, test and review, then ship. Idle agents claim the next packet the moment they're free; several can be working at once.

A finished packet isn't a finished product. If review sends it back, it loops through refine before it ships. Only work that survives build, test and review actually goes out the door.

Multiple projects. One shared queue. A path to ship.
Diagram of three projects feeding one shared queue, built in parallel by agents, then tested, reviewed and shipped.

Analytics, mobile and ecommerce projects feed work packets into a shared queue. Packets are planned, broken down, built by agents in parallel, tested and reviewed, then shipped. Work can return for refinement.

Deciding which agent takes which packet, and knowing when a result is actually ready, are still being tested rather than settled. The journal is where I track what holds up.

Why gFactory →

Why I'm doing this

I have more product ideas than hours in a week. gFactory is what I'm building to give those ideas a better chance of becoming real products.

Right now it's just me, a roadmap, and a very patient stack of agents. Whether it works or not, this is the record of how it goes.

Nights, weekends, one desk. That's where the extra hours come from.

A desk at night: lamp light over a laptop, a book, a plant and a coffee mug, with a moon and stars in the window.

This week at a glance

[ latest notes ]

Notes from October 18. The full story lives in the journal below.

Week 3 · 18 Oct

  • ·Built and validated a reusable spec-writer skill on gFactory's own PRD
  • ·Produced and reviewed the M0 spec pack (specs 00 to 10) with a testing playbook
  • ·Chose Python for the orchestrator and moved spec writing into v1

Next up

  • ·Stand up the dev environment and the sandbox; build the data model and config
  • ·See whether the specs survive contact with an actual agent

The Journal

Every Sunday I share what moved forward, what is still open, and what comes next. The journal keeps the full record.

Read the Journal →

Sketch of stacked notebooks and an open journal with a pen

Follow along

I post the build in the open: updates, wins, and the occasional dead end.

Get the Sunday entry in your inbox

One email each Sunday when a new entry goes up. No spam, unsubscribe anytime.