Skip to content

docs(specs): adk-flair TypeScript addendum (seam verified, deltas from Python design) #335

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tps-flint merged 1 commit into from
Aug 6, 2026
Merged

docs(specs): adk-flair TypeScript addendum (seam verified, deltas from Python design) #335

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 38 additions & 0 deletions specs/ADK-FLAIR-ADAPTER.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -189,3 +189,41 @@ regardless), per-user Flair principals, any Flair server changes.
- Hardening follow-up (phase 2, not a gate): `FLAIR_ALLOW_REMOTE_URL=<exact
URL>` compared against the resolved URL, instead of `=1` — kills the
"set the flag, then typo'd the URL" mode.

---

## TypeScript adapter addendum (2026-08-06, seam verified against adk-js v1.6.0)

Everything above ports except as noted. Source-verified facts: `@google/adk`
(github.com/google/adk-js) defines `BaseMemoryService` as a two-method TS
interface (`addSessionToMemory`, `searchMemory`) — stable since inception;
`PreloadMemoryTool` behaves like Python's (every-turn, exception-swallowing,
`parts[0].text` query, text-only injection); `Runner({memoryService})` and
`AdkApiServerOptions.memoryService` accept third-party implementations with
zero forking.

**Package:** `packages/adk-flair-js` in the flair monorepo, npm name
`@tpsdev-ai/adk-flair`. Being a normal npm workspace package, it rides the
release train — Nathan's minor-match policy costs nothing here; version
alignment is automatic.

**Deltas from the Python design:**
1. **Registration story changes** — adk-js has NO memory URI registry (its
session/artifact URI resolvers are closed if-chains; no memory flag on the
dev CLI at all). Ship: exported `FlairMemoryService` class + README showing
`new Runner({ memoryService })` and a ~10-line `AdkApiServer` wrapper entry
for dev-UI use. No `flair://` scheme.
2. **Interface surface is exactly two methods** — `addEventsToMemory`/
`addMemory` may exist as extra methods (Vertex parity) but nothing in ADK
calls them; document that.
3. **Timestamp units:** adk-js `Event.timestamp` is epoch MILLISECONDS
(Python: seconds). `MemoryEntry.timestamp` out is an ISO string. Do not
port Python's seconds assumption.
4. Everything else ports verbatim: compound tag `adk:<app>:<user>` with colon
sanitization, mandatory-userId-or-empty, per-hit tag re-verification,
timeout budget (2s lifecycle: connect 0.5/read 1.5), localhost-free /
`FLAIR_ALLOW_REMOTE_URL=1` gate, key parse-and-validate in ctor with
variable-named errors, deterministic record ids, silent-degrade health
warning. The 9-test integration suite is the conformance spec — the TS
package implements the same tests (explain-plan via the same server
support, portability, quickstart-parity with a real model).
Loading