Platform Changelog.
Updates
Every change to the platform documented with technical detail. Release notes, feature additions, security patches, and infrastructure updates.
Changelog
Transparent development. Every change documented.
The platform is under active development. Release notes will be published here as features ship, updates land, and the forge grows.
8 items
A consulting-fee figure and an overstated arithmetic result were cut, and the arguments they supported hold without them. The deploy gate's allowance for third-party costs narrowed to match.
Every article was rewritten against the architecture corpus: design-present tense, fabricated statistics removed, mechanisms traced to their source or cut. Where the site had folded the DoD Impact Levels into a span, it now names the four the issuing authority defines. Machine headlines are checked against the headline a reader sees.
Every answer was reviewed and rewritten where the voice law required it: design-present tense, every claim traced or cut, status questions answered plainly. Company commitments now speak from the company document register, machine mirrors are regenerated from the rendered text, and the build fails on any mirror that drifts from its answer.
All nine capability pages and their index were rewritten against the architecture corpus: design-present tense, every claim traced or cut, evidence carried in the sentence. Published counts are now computed from the site or declared with their basis in counts.json, and the build fails on any number that matches neither.
A page's Last updated date moves when the page's own content moves, and never because a shared fragment was regenerated or a cache token bumped. A verifier classifies every changed page as content, chrome, or metadata and fails a content change that carries a stale date. The same classifier gates deployment: a deploy that ships content without a changelog entry is refused before it reaches the network. The record of change is not a courtesy here. It is a precondition.
A charter now governs every word on this site. Redoubt Forge is a compliance control plane: the layer that holds desired state, reconciles the world against it, and reports divergence as a diff. Not a GRC platform, which is a filing cabinet with workflows. Not compliance automation, which collects evidence about systems where this computes proof from them. Every page that named the old category has been corrected.
CMMC versus FedRAMP, and the framework comparison that sets four regimes side by side, now live under guides. They teach the ground rather than argue a purchase, and that is where a reader looking to understand the terrain expects to find them. The former paths redirect; nothing a search engine or a bookmark points at has broken.
Redoubt Forge is in design, and the site now says so plainly, everywhere a reader or a machine looks.