Unified account (GTL ID)
One sign-in context for lab products — profiles, memberships, and session scope travel with the user.
Connectivity
Ecosystem & API connectivity
A unified architecture model: one identity, shared infrastructure, and interoperable services — designed for scale across the GodTech Labs platform.
Architecture & developer roadmap
Diagrams and API descriptions below reflect platform direction and planned integration — not live production endpoints or fully shipped products.
How services connect
Ecosystem continuity through a single account, shared layers, and consistent permission context.
Interoperability
Products designed to share storage references, metadata, and identity — not isolated silos.
Shared infrastructure
Identity, APIs, storage zones, security model, and developer surface — common foundation for every service.
Service-to-service relationships
Drive as file source, Docs/Sheets as structured layers, Mail for identity-linked messaging, Search for discovery.
Ecosystem data flow
User actions flow through GTL ID and the API layer before touching storage, indexes, and product UIs.
Ecosystem data flow
1
Users & clients
2
GTL ID
3
API layer
4
Ecosystem services
5
Storage & index
GTL ID — central identity layer
Hub-and-spoke model connecting productivity and discovery services under one permission-aware identity.
GTL ID
├── Docs
├── Drive
├── Sheets
├── Search
Mail
Docs
Drive
Sheets
Search
One identity
Single account and profile anchor — reduces duplicate credentials across the lab.
Shared access model
Product memberships and roles determine what each service may read or write.
Connected services
Mail, Docs, Drive, Sheets, and Search (Palmis) share the same identity context.
Permission-aware access
Infrastructure designed to check scope before storage or API mutations — progressive rollout.
OAuth & API layer (roadmap)
Third-party apps via documented scopes and consent — developer platform direction, not live for all products.
Account dashboard
Signed-in users manage profile, ecosystem, and security from account settings and GTL ID hub.
API connectivity model
Developer platform APIs — labeled by maturity. No API keys or live endpoints are issued from this page.
Partial (auth live)
Authentication API
Sessions and token flows via Supabase Auth today — OAuth for third-party apps on the integration roadmap.
Roadmap
GTL ID API
Profiles, roles, and product memberships for ecosystem-aware apps.
Architecture model
Storage API
Files, metadata, and controlled sharing atop the shared storage layer.
Planned
Search API
Indexing and Palmis / ecosystem queries as search infrastructure matures.
Roadmap
AI API
Assistants and contextual intelligence across services — guardrails and scoped access.
Statuses reflect roadmap and architecture — verify availability in developer documentation when published.
Interoperability model
How products are designed to work together — honest ecosystem direction, not full production coupling today.
Drive → file source
Designed to store versions and folders consumed by Docs attachments and Sheets imports.
Docs → documents on storage
Planned to reference Drive/cloud objects and shared metadata rather than duplicate blobs.
Sheets → structured data
Architecture direction: grids and exports orchestrated via storage and sync engine.
Mail → identity & notifications
Planned to connect GTL ID for addressing, alerts, and cross-product messages.
Search → discovery
Designed to index ecosystem content as Mail, Docs, Drive, and Sheets expose metadata.
AI → cross-service assist
Planned contextual help across products with permission-aware, scoped access.
Service dependency map (concept)
Logical dependencies for the ecosystem model — not a live service mesh diagram.
GTL ID
Mail
Search
Drive
Docs
Sheets
Drive → Docs / Sheets · GTL ID → Mail / Search