Barry Jones·Sep 17RCF Walkthrough 15: The two-question auditHow code links back to a business decision, and how a business decision links forward to a test.
Barry Jones·Sep 14Governance moved inside the build.Security leaders and private equity operating partners in my feed are agreeing on AI governance. It needs to be built into the software and…
Barry Jones·Sep 10RCF and requirements-driven developmentRequirements-driven development got there first. It has been putting requirements at the centre of the build for decades, with a defined…
Barry Jones·Sep 7Vibe coding at enterprise scale: the review that never happens.Vibe coding keeps climbing the search charts, and every enterprise governance post carries the same line about a senior engineer reviewing…
Barry Jones·Sep 2RCF Walkthrough 13: What RCF is for, and what it isn’tThe methodology, as published today, scopes the build-side of the lifecycle: everything between an agreed PRD and TAD, and a feature…
Barry Jones·Aug 27RCF Walkthrough 12: Functional build specificationsA Y-shape, not a line. Intent comes down the left arm, architecture down the right, and the two meet at the build chain. Each layer points…
Barry Jones·Aug 24Your tests passed. Your suite lied.An unattended AI build shipped an email channel with an integration suite at twelve of twelve green, marked approved, and no API key had…
Barry Jones·Jul 13One graph or two: how we chose CodeNodes for RCF’s spec-to-code bridgeRCF’s traceability chain was complete on the spec side and stopped dead at the code. Here is the design call I made to carry it across, and…
