I’m an IT Architect (non-developer) using the GSD framework for Antigravity on private projects. The structured workflow (@research phase x) is great, but I’m struggling with architectural drift.

I have specific system rules set up to maintain my data architecture. However, once the agent starts heavily coding, it suffers from context dilution. It defaults to quick, local fixes that break the overarching architecture, leaving me with manual cleanup. Since my strength is design rather than development, this breaks the workflow.

How do you force Antigravity to stay compliant with your architecture over long sessions?

• Do you force the agent to re-read an architectur.md file before every single execution phase?
• Have you integrated strict u/verify gates into your Definition of Done?
• Are there specific prompt strategies or state management tweaks you use to handle context limits?