<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://iamulya.one/</id><title>Amulya Bhatia</title><subtitle>A blog written by Amulya Bhatia, connecting technical innovations to business wins.</subtitle> <updated>2026-07-03T22:47:37+02:00</updated> <author> <name>Amulya Bhatia</name> <uri>https://iamulya.one/</uri> </author><link rel="self" type="application/atom+xml" href="https://iamulya.one/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://iamulya.one/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Amulya Bhatia </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Understanding the Policy Priority Model in Antigravity</title><link href="https://iamulya.one/posts/understanding-the-policy-priority-model/" rel="alternate" type="text/html" title="Understanding the Policy Priority Model in Antigravity" /><published>2026-07-02T13:00:00+02:00</published> <updated>2026-07-02T13:00:00+02:00</updated> <id>https://iamulya.one/posts/understanding-the-policy-priority-model/</id> <content src="https://iamulya.one/posts/understanding-the-policy-priority-model/" /> <author> <name>Amulya Bhatia</name> </author> <category term="Antigravity" /> <category term="Engineering" /> <summary> This article is part of the Antigravity Engineering Series. You have 15 policies. The agent calls run_command with npm install lodash. Which policy fires? Why that one and not the three others that also match run_command? If you’ve ever debugged a firewall rule set or traced a message through a content-based router, you already know the shape of this problem. Multiple rules match the same... </summary> </entry> <entry><title>Testing Strategies for Automating Antigravity Workflows</title><link href="https://iamulya.one/posts/testing-strategies-for-automating-antigravity-workflows/" rel="alternate" type="text/html" title="Testing Strategies for Automating Antigravity Workflows" /><published>2026-07-02T13:00:00+02:00</published> <updated>2026-07-02T13:00:00+02:00</updated> <id>https://iamulya.one/posts/testing-strategies-for-automating-antigravity-workflows/</id> <content src="https://iamulya.one/posts/testing-strategies-for-automating-antigravity-workflows/" /> <author> <name>Amulya Bhatia</name> </author> <category term="Antigravity" /> <category term="Engineering" /> <summary> This article is part of the Antigravity Engineering Series. You built the hook scripts. You wrote the policies. You configured the sidecar. You shipped it all and went to bed. At 3 AM, a one-character typo in your PreToolUse hook emitted malformed JSON, silently failing open. The agent — now ungated — ran npm publish against your production registry. You woke up to 47 Slack messages. The... </summary> </entry> <entry><title>System Instructions Architecture in Antigravity</title><link href="https://iamulya.one/posts/systems-instruction-architecture-in-antigravity/" rel="alternate" type="text/html" title="System Instructions Architecture in Antigravity" /><published>2026-07-02T13:00:00+02:00</published> <updated>2026-07-02T13:00:00+02:00</updated> <id>https://iamulya.one/posts/systems-instruction-architecture-in-antigravity/</id> <content src="https://iamulya.one/posts/systems-instruction-architecture-in-antigravity/" /> <author> <name>Amulya Bhatia</name> </author> <category term="Antigravity" /> <category term="Engineering" /> <summary> This article is part of the Antigravity Engineering Series. Your agent writes code like a chatbot — overly polite, hedging every suggestion with “you might want to consider…”, emitting markdown explanations where you need raw code. You want it to act like a senior engineer: direct, opinionated, testing everything it ships. This is a configuration problem, not a training problem. The syste... </summary> </entry> <entry><title>Orchestrating Multi-Agent Teams with Subagents and Worktrees in Antigravity 2.0</title><link href="https://iamulya.one/posts/orchestrating-multi-agent-teams-with-antigravity/" rel="alternate" type="text/html" title="Orchestrating Multi-Agent Teams with Subagents and Worktrees in Antigravity 2.0" /><published>2026-07-02T13:00:00+02:00</published> <updated>2026-07-02T13:00:00+02:00</updated> <id>https://iamulya.one/posts/orchestrating-multi-agent-teams-with-antigravity/</id> <content src="https://iamulya.one/posts/orchestrating-multi-agent-teams-with-antigravity/" /> <author> <name>Amulya Bhatia</name> </author> <category term="Antigravity" /> <category term="Engineering" /> <summary> This article is part of the Antigravity Engineering Series. Picture a refactoring task that touches 47 files across 3 modules. A single agent starts at file 1. By file 30, its context window is saturated with the memory of files 1–29 — code it no longer needs but can’t discard. Coherence degrades. The agent begins making contradictory changes. By file 40, it’s undoing work it did at file 1... </summary> </entry> <entry><title>Hook Contexts: Session, Turn, and Operation State in the Antigravity SDK</title><link href="https://iamulya.one/posts/hook-contexts-in-antigravity-sdk/" rel="alternate" type="text/html" title="Hook Contexts: Session, Turn, and Operation State in the Antigravity SDK" /><published>2026-07-02T13:00:00+02:00</published> <updated>2026-07-02T13:00:00+02:00</updated> <id>https://iamulya.one/posts/hook-contexts-in-antigravity-sdk/</id> <content src="https://iamulya.one/posts/hook-contexts-in-antigravity-sdk/" /> <author> <name>Amulya Bhatia</name> </author> <category term="Antigravity" /> <category term="Engineering" /> <summary> This article is part of the Antigravity Engineering Series. You’re building a token budget hook. It needs to track total tokens across the entire session. But it also needs to track tokens per turn to catch retry loops. And it needs to time individual tool calls to detect slow operations. Three different lifetimes. Three different scopes. If you use instance variables, you end up resettin... </summary> </entry> </feed>
