My weekly limits roll over in about 9 hours. I have a bunch of Fable tokens left that I do not want to use. But I’m also at ~96% of my 5 hour usage window and I need to go to bed. Doesn’t reset for an hour. So, I did what anyone would do, I asked Fable what my options are. Apparently it has a timer. It has set one for 80 minutes and that will wake it so it can fire what we have queued up… I guess I’ll find out what does or doesn’t happen to that branch come morning…!!! Fable has immense confidence that all the results will be ready for me to review over a coffee… ☕️

BuilderCore Journey Update Over the last few weeks, something interesting happened. We weren’t just building an AI development platform. We were discovering what an AI software factory actually needs before it can be trusted. One of the biggest lessons was this: Governance is more important than autonomy. Everyone is racing to make AI agents that can do more. We’re trying to make AI systems that can be trusted to do more. Those are very different goals. The first goal isn’t autonomy. It’s predictability. Our first milestone wasn’t: - autonomous coding - autonomous deployment - autonomous GitHub actions It was proving that every stage of software delivery could be controlled, audited, replayed and stopped. That meant proving things like: - controlled apply - replay workspaces - validation - queue promotion - queue completion before even thinking about autonomous execution. That order matters. We stopped treating AI like one assistant. Instead, we started treating it like an organisation. Not one intelligence. A collection of specialised roles. For example: - Planner - Hardener - Researcher - Implementer - Reviewer - Judge - Operator That immediately changed how we think about AI. One of the strongest doctrines we’ve adopted: The same AI should never judge its own work. That now applies to: - reviews - validation - judgement If one model creates something… A different one should evaluate it. That’s closer to how healthy engineering teams actually work. Roles are permanent. Models are replaceable. This became one of the biggest architectural shifts. Instead of designing around: - GPT - Claude - Codex - Perplexity we design around roles. Today GPT might be the planner. Tomorrow another model might be better. The workflow shouldn’t have to change because the underlying model changes. We discovered evidence should change roadmaps. Not doctrine. This thread completely changed our roadmap. Originally we planned to test vague briefs next.