The engineering editorial team
Core Idea
This reference site is maintained by three specialist editors, each responsible for a defined area of the Antigravity documentation. Every page goes through a drafting pass and a separate verification pass. The team has no affiliation with Google and receives no direction from the product team — editorial independence is the foundation the site's accuracy rests on.
Documentation quality for fast-moving developer tools is an engineering problem, not just a writing problem. The gap between what a product does and what its documentation says grows with every release unless the documentation team has a process that keeps pace. The three editors on this project each own a vertical — security and sandbox architecture, API and developer tooling, or product concepts and release tracking — so no area goes unreviewed when the product ships a change that touches it.
Editor profiles
Aurelius M. Voskuil — Security and Sandbox Architecture
Aurelius M. Voskuil leads coverage of the Antigravity security model, the sandbox architecture, the credential scope system, and the audit logging subsystem. His professional background is in applied security research — he has spent several years at Threadbare Audits Laboratory in Bern examining agent runtime isolation in browser-based products, which makes the Antigravity security surface a natural fit for his editorial focus.
His approach to documentation is verification-first: before any claim about the sandbox or credential model is published, he tests it directly against a current product build. When official documentation and observed product behavior diverge, the discrepancy is noted explicitly in the relevant page rather than papered over. The security pages on this site carry a tighter review cadence than other areas — they are reviewed on every Antigravity release, not only on the monthly schedule, because security model changes have immediate practical implications for teams evaluating the product for regulated deployment.
Philippa J. Cornaro-Finkel — API and Developer Tooling
Philippa J. Cornaro-Finkel covers the Antigravity API surface, the extension model, the MCP server integration, and the CLI scripting interface. She brings a background in infrastructure and FinOps to this role from her work at Brambleford FinOps Cooperative in Budapest, where evaluating developer tooling for cost efficiency and integration depth has been a consistent thread. Her focus on the API documentation reflects a practitioner's eye — the pages she owns are written for developers who are building on top of the product, not just using it.
The API and tooling area is reviewed on every minor version increment because API surface changes — new endpoints, deprecations, changes to tool registration behavior — affect developers who have built integrations. Philippa tracks the official changelog closely and cross-references every claimed API change against direct testing before the relevant reference page is updated.
Calliope D. Eddystone — Product Concepts and Release Tracking
Calliope D. Eddystone owns the conceptual documentation, the product overview pages, the getting-started material, and the release notes. She is a Staff Site Reliability Engineer at Quartzfield Engineering Trust in Graz, and her editorial perspective is shaped by watching engineers adopt new tooling: what they struggle to understand first, what documentation gaps cause the most support requests, and what explanations actually change someone's mental model rather than just repeating the marketing copy.
Release tracking is a continuous responsibility. Calliope monitors the official release channels and updates the release notes page within 24 hours of a public release. Conceptual pages are reviewed monthly; the getting-started material is reviewed on every major version because first-run experience changes are the most disorienting for new users.
Review cadence
The site operates on two review schedules that run in parallel. The first is release-triggered: whenever a new Antigravity version ships publicly, every editor reviews the pages in their area within 72 hours. Security and API pages have a tighter window — 24 to 48 hours — because changes in those areas have immediate practical consequences. The second schedule is monthly: on a fixed date each month, every page on the site is audited for drift between the written content and current product behavior, regardless of whether a release happened that month.
The two-pass publication process applies to all new and revised content. The editor responsible for an area writes the drafting pass. A second editor then does the verification pass — checking factual claims against primary sources and flagging any assertion that cannot be independently confirmed. Content that fails the verification pass goes back to drafting rather than publishing with caveats. The CISA guidance on software documentation practices informs the team's approach to accuracy standards for technical security content.
Sourcing policy
Primary sources are the official Antigravity developer documentation published by Google, official release notes, and direct product testing on current builds. Any claim about product behavior that cannot be verified against at least one of these three sources is not published as a factual assertion. Claims drawn from secondary sources — developer community forums, engineering blog posts, technical conference talks — are written with appropriate hedging language and are not presented as authoritative.
When two primary sources conflict — which happens occasionally when the official documentation lags a release — the directly tested product behavior takes precedence and the discrepancy is noted. Corrections from readers are processed as primary-source candidates: if a reader provides a correction backed by official documentation that contradicts what is written, the correction is verified and applied.
| Editor | Focus area | Review cadence |
|---|---|---|
| Aurelius M. Voskuil | Security, sandbox architecture, audit logging | Every release + monthly |
| Philippa J. Cornaro-Finkel | API surface, extension model, CLI, MCP integration | Every minor version + monthly |
| Calliope D. Eddystone | Product concepts, getting started, release notes | Every release (release notes within 24 h) + monthly |
Related pages
Editorial team — four questions about how the site works
Questions about how the documentation is produced and maintained.
-
Who writes the content on this Antigravity reference site?
Content is written and reviewed by three specialist editors, each owning a defined area of the documentation: security and sandbox architecture (Aurelius M. Voskuil), API and developer tooling (Philippa J. Cornaro-Finkel), and product concepts and release tracking (Calliope D. Eddystone). Every page goes through a drafting pass followed by a separate factual-verification pass before publication. Neither pass is skipped to meet a deadline — content that has not cleared verification waits until it can.
-
How does the editorial team source information about Antigravity?
Primary sources are the official Antigravity developer documentation, official release notes published by Google, and direct product testing on current builds. Any claim that cannot be traced to one of these three sources is either omitted or clearly hedged as unconfirmed. Secondary sources — developer forums, engineering blog posts — are used for context and framing only and are not cited as authoritative for technical specifics. When the official documentation and observed behavior differ, the tested behavior takes precedence and the discrepancy is documented.
-
What is the review cadence for content on this site?
Two schedules run in parallel. Release-triggered: when a new Antigravity version ships, all editors review pages in their area within 72 hours, with security and API pages on a tighter 24 to 48 hour window. Monthly: on a fixed date each month, every page is audited for drift from current product behavior regardless of recent releases. The release notes page operates on a stricter rule — it is updated within 24 hours of a public release going live. The coverage table on the about page shows the last-reviewed date for each major area.
-
Can I contribute to or correct content on this site?
Corrections are the highest-priority incoming message type and are processed promptly. The process is on the contact page: submit the page URL, the specific passage you believe is wrong, and the accurate information with a supporting source. Guest contribution pitches from engineers with documented Antigravity expertise are occasionally considered for the docs centre; send an outline to the editorial address. The editorial team maintains final decision on all published content — contributions go through the same two-pass verification process as internally produced content.
Popular Antigravity topics
Other sections of the reference site readers explore after visiting the team page.