OSS-first docs
These docs teach the open system first: contracts, generated surfaces, runtimes, governance, and incremental adoption. Studio shows up as the operating layer on top, not as the source of truth.
Operate
Knowledge is part of the runtime, not a sidecar prompt hack.
When AI-native systems depend on external context, the context needs the same discipline as the rest of the stack. ContractSpec treats knowledge as typed, bounded, and governable so teams can reason about trust, isolation, and retrieval behavior.
How knowledge enters the system
- Define the trust category and retrieval expectations first.
- Bind tenant-owned sources explicitly to those knowledge spaces.
- Consume knowledge through capabilities and workflows, not through invisible prompt assumptions.
Categories
Separate canonical truth from operational notes, external material, and ephemeral working context.
Spaces
Define the storage and retrieval boundary for each knowledge domain.
Sources
Connect tenant-owned sources explicitly instead of letting context leak in through prompts alone.
Governance
Gate provider-backed mutations with dry-runs, approvals, idempotency, audit evidence, and outbound-send policy.
Provider-backed adoption
Wire Gmail and Google Drive ingestion through checkpointed deltas, tombstones, watches, and Connect evidence.
Examples
See how support, compliance, and product systems consume trusted knowledge at runtime.
Tenant isolation
Keep tenant data, config, policies, and integrations separated at runtime.
Knowledge mutation governance
Gate provider-backed knowledge mutations with dry-runs, approvals, idempotency, audit evidence, and outbound-send policy.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.