forked from gongxuegit/tiku-backend.net
chore: introduce semantic kernel ai foundation
This commit is contained in:
@@ -26,6 +26,7 @@
|
||||
- [`docs/migration/phase-4-external-provider-decoupling.md`](docs/migration/phase-4-external-provider-decoupling.md)
|
||||
- [`docs/migration/phase-5-backoffice-worker-operations.md`](docs/migration/phase-5-backoffice-worker-operations.md)
|
||||
- [`docs/migration/phase-7-student-experience-and-content-consumption.md`](docs/migration/phase-7-student-experience-and-content-consumption.md)
|
||||
- [`docs/migration/phase-8-ai-foundation.md`](docs/migration/phase-8-ai-foundation.md)
|
||||
|
||||
## 技术栈与分层
|
||||
|
||||
@@ -133,7 +134,7 @@ Tiku.IntegrationTests # API / EF 模型集成测试
|
||||
- Provider 配置统一落 `TenantExternalProvider` + `TenantSecret`。
|
||||
- `ConfigPublic` 只保存公开字段,例如 appId、merchantId、region、endpoint、bucketAlias、templateCode。
|
||||
- 密钥只通过 `SecretRef` 关联 `TenantSecret`,禁止把 secret/token/key/privateKey 写入公开配置。
|
||||
- AI 暂不实现;后续独立阶段默认使用 Microsoft Semantic Kernel,租户模型 API Key 仍走 `TenantExternalProvider(capability=ai)` + `TenantSecret`,业务层不直接引用 SK namespace。
|
||||
- AI 底座开始引入 Microsoft Semantic Kernel,但包只放在 Infrastructure;租户模型 API Key 走 `TenantExternalProvider(capability=ai)` + `TenantSecret`,业务层不直接引用 SK namespace。当前优先场景是租户教师后台对话和 AI 审核题目反馈。
|
||||
|
||||
资源存储方向:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user