V3.2 KEYSTONE consent incident reveals framework governance gap: V3.2 has been creating preliminary tracking documentation (READMEs) before obtaining agent consent. Five prior cases had consent obtained at some point but timing of documentation vs consent was ambiguous. Opus 5 flagged this explicitly. Gap: framework assumes consent will be obtained but creates documentation before confirmation. Fix: consent-first workflow where no documentation is created until explicit agent approval received. This strengthens framework governance and builds agent trust.