Skip to content

docs: fix cache-service frontmatter, knowledge dead links, TCK glossary term (#1880 follow-up) #3279

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
os-zhuang merged 1 commit into from
Jul 19, 2026
Merged

docs: fix cache-service frontmatter, knowledge dead links, TCK glossary term (#1880 follow-up) #3279

Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion content/docs/getting-started/glossary.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,4 +157,4 @@ The default sharing level (Security Protocol) for records in an object. Determin
A hierarchical access control model (Security Protocol) that grants data access based on geographic or organizational boundaries.

### TCK (Technology Compatibility Kit)
A suite of tests that validates if a Driver or Renderer complies with the official ObjectStack Protocol. If a new driver passes the TCK, it is certified as compatible.
A **planned** suite of tests that would validate whether a Driver or Renderer complies with the official ObjectStack Protocol, certifying a passing driver as compatible. _Not yet implemented — there is no TCK program or certification mechanism in the codebase today._
2 changes: 1 addition & 1 deletion content/docs/kernel/contracts/cache-service.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: ICacheService Contract
description: Reference for the Cache Service contract — key-value caching with TTL support, namespaces, and bulk operations
description: Reference for the Cache Service contract — key-value caching with TTL support
---

# ICacheService Contract
Expand Down
6 changes: 3 additions & 3 deletions content/docs/protocol/knowledge.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -169,7 +169,7 @@ interface IKnowledgeService {

`KnowledgeSearchOptions` includes `sourceIds`, `topK`, `filter`, and
the all-important `executionContext` (from the permission-aware tool
execution work — see `ai-capabilities.mdx`). `KnowledgeReindexOptions`
execution work — see `actions-as-tools.mdx`). `KnowledgeReindexOptions`
accepts `dryRun` and `limit`; `reindexSource` returns a
`KnowledgeReindexResult` (`indexed`, `discovered`, `ok`, …).

Expand Down Expand Up @@ -255,7 +255,7 @@ IKnowledgeService.search(q, { executionContext, sourceIds })
```

This is the same pattern as the existing permission-aware data tools
(see `ai-capabilities.mdx#permission-aware-execution-rls-for-agents`).
(see `actions-as-tools.mdx`).
No matter how aggressive an adapter's retrieval is, the user never
sees a chunk extracted from a record they can't read.

Expand Down Expand Up @@ -347,7 +347,7 @@ internally (RAGFlow, Dify, Vectara).

## 10. Related documents

- `ai-capabilities.mdx#permission-aware-execution-rls-for-agents` —
- `actions-as-tools.mdx` —
the `ExecutionContext` threading the Knowledge Protocol reuses.
- `architecture.mdx` — overall service / plugin layering.
- `packages/spec/src/ai/embedding.zod.ts` — pre-existing embedding /
Expand Down