Google Docs + Ambience.
Updated 2026-06-07 · Specs and docs
Seed Ambience with approved specs, RFCs, and policy decisions from Google Docs through the user's existing agent access.
Google Docs is where teams write the plan. Ambience turns the durable parts into context agents can actually reuse.
Ambience stores the reusable decision, convention, skill, failure, or reference. The original google doc stays visible as source context.
Example source-linked memories
Dashboard value metric definitions
Source: Google Doc: Value reporting spec
Use source-linked memories instead of raw transcript imports
Source: Google Doc: Context harness proposal
Docs become usable agent context
Long specs and RFCs are useful for humans, but agents need concise durable takeaways. Ambience can store the decisions, constraints, and references that should shape future sessions.
User-controlled inclusion
During onboarding or an optional sweep, the user chooses which approved documents are considered. Ambience asks what to include before seeding shared memory.
Source remains visible
The resulting memory can point back to the source document so the team can inspect the original context when precision matters.