I've been working on this for a long time. Since before vibecoding was really a thing. So what happened with this is I took a digital twin I had made of my property and fed that to GPT 5.5 when that came out through codex to make a tool called "Adirondack Land Research" that basically did a bunch of research on parcels in the Adirondack park to get geospatial data necessary to make these "map packs" (basically cartographic products).

Well it was really expensive to host and it turns out the Adirondack park is kind of small as far as a total--addressable-market goes. So I put it on the shelf. 

But I had these fetchers built for a lot of national data layers, namely USGS LiDAR data, LANDFIRE, and GAP species richness. And I had this digital twin thing going at home...

So enter fable. With fable I developed most of what you see here. 

My workflow is to write up requirements for features (I will usually iterate this a few times with GPT 5.5 Research Pro). Then I hand those requirements to fable in claude code. 

Fable has explicit instructions to delegate as much code writing to GPT 5.5 xhigh via codex and to focus on high level planning, verification, and orchestration work. I save a lot of tokens this way. 

Occasionally, for really complicated features, I take my spec and give it to Hermes agent that has an adversarial skill to write verification criteria against my specs with gpt 5.5 and then have claude opus 4.8 review them and give feedback, repeating that loop until claude is satisfied the criteria are legit and the requirements are valid.   
  
Anyway it's a lot of fun and of great personal use to me. Hope you enjoy!  

Vibe Coded Digital Twin Engine