Features - User Management (Phase 4.1): - Database: Add user_modules table for fine-grained module permissions - Database: Add 4 user permissions (view/create/edit/delete) to role_permissions - Backend: UserService (780 lines) - CRUD with tenant isolation - Backend: UserController + UserRoutes (648 lines) - 13 API endpoints - Backend: Batch import users from Excel - Frontend: UserListPage (412 lines) - list/filter/search/pagination - Frontend: UserFormPage (341 lines) - create/edit with module config - Frontend: UserDetailPage (393 lines) - details/tenant/module management - Frontend: 3 modal components (592 lines) - import/assign/configure - API: GET/POST/PUT/DELETE /api/admin/users/* endpoints Architecture Upgrade - Module Permission System: - Backend: Add getUserModules() method in auth.service - Backend: Login API returns modules array in user object - Frontend: AuthContext adds hasModule() method - Frontend: Navigation filters modules based on user.modules - Frontend: RouteGuard checks requiredModule instead of requiredVersion - Frontend: Remove deprecated version-based permission system - UX: Only show accessible modules in navigation (clean UI) - UX: Smart redirect after login (avoid 403 for regular users) Fixes: - Fix UTF-8 encoding corruption in ~100 docs files - Fix pageSize type conversion in userService (String to Number) - Fix authUser undefined error in TopNavigation - Fix login redirect logic with role-based access check - Update Git commit guidelines v1.2 with UTF-8 safety rules Database Changes: - CREATE TABLE user_modules (user_id, tenant_id, module_code, is_enabled) - ADD UNIQUE CONSTRAINT (user_id, tenant_id, module_code) - INSERT 4 permissions + role assignments - UPDATE PUBLIC tenant with 8 module subscriptions Technical: - Backend: 5 new files (~2400 lines) - Frontend: 10 new files (~2500 lines) - Docs: 1 development record + 2 status updates + 1 guideline update - Total: ~4900 lines of code Status: User management 100% complete, module permission system operational
2.2 KiB
2.2 KiB
通用能力层
层级定义: 跨业务模块共享的核心技术能力
核心原则: 可复用、高内聚、独立部署
📋 能力清单
| 能力 | 说明 | 复用率 | 优先级 | 状态 |
|---|---|---|---|---|
| 01-LLM大模型网关 | 统一管理LLM调用、成本控制、模型切换 | 71% (5/7) | P0 | ⏳ 待实现 |
| 02-文档处理引擎 | PDF/Docx/Txt提取、OCR、表格提取 | 86% (6/7) | P0 | ✅ 已实现 |
| 03-RAG引擎 | 向量检索、语义搜索、RAG问答 | 43% (3/7) | P1 | ✅ 已实现 |
| 04-数据ETL引擎 | Excel JOIN、数据清洗、数据转换 | 29% (2/7) | P2 | ⏳ 待实现 |
| 05-医学NLP引擎 | 医学实体识别、术语标准化 | 14% (1/7) | P2 | ⏳ 待实现 |
🎯 设计原则
1. 可复用性
- 多个业务模块共享
- 避免重复开发
2. 独立部署
- 可以独立为微服务
- 支持独立扩展
3. 高内聚
- 每个能力职责单一
- 接口清晰
4. 领域知识
- 包含业务领域知识
- 不是纯技术组件
📊 复用率分析
LLM网关 - 71%复用率(最高优先级)
- AIA(AI智能问答)
- ASL(AI智能文献)
- PKB(个人知识库)
- DC(数据清洗)
- RVW(稿件审查)
文档处理引擎 - 86%复用率(已实现)
- ASL、PKB、DC、SSA、ST、RVW
RAG引擎 - 43%复用率(已实现)
- AIA、ASL、PKB
📚 快速导航
快速上下文
- [AI对接] 通用能力快速上下文.md - 2-3分钟了解通用能力层
核心能力
🔗 相关文档
最后更新: 2025-11-06
维护人: 技术架构师