NovAIC

AI-powered agent platform with mobile (iOS/Android) and desktop (macOS/Windows/Linux) clients.

Architecture

novaic/
├── novaic-app/                  # Tauri v2 前端 (React + TypeScript)
├── novaic-agent-runtime/        # Agent 运行时
├── novaic-gateway/              # API 网关
├── novaic-business/             # Business Service
├── novaic-device/               # Device Service
├── novaic-common/               # 共享库与配置
├── novaic-cortex/               # Cortex scope / step 服务
├── novaic-blob-service/         # Blob Service
├── novaic-mcp-vmuse/            # MCP VMuse 集成
├── novaic-quic-service/         # QUIC relay 服务
├── Entangled/                   # 同步引擎
├── byclaw-website/              # 官网
├── thirdparty/openclaw/         # 上游参考
├── docs/                        # 父仓文档（HANDOVER 纲要：README.md、architecture/、reference/、runbooks/）
├── scripts/                     # 构建/部署/运维脚本
└── examples/                    # 示例项目

Getting Started

# Clone with all submodules
git clone --recurse-submodules git@github.com:chriswangcq/novaic.git

# If already cloned, init submodules
git submodule update --init --recursive

Submodules

All services are independent Git repos managed as submodules. See .gitmodules for details.

Testing

During development, run focused tests for the changed component. For a cross-component or release-control change, run the canonical backend matrix once from the repository root:

scripts/run_all_tests.sh

The runner executes each backend submodule with its explicit package path. Avoid bare recursive pytest across the monorepo root; submodules are independent packages and some contract tests intentionally import sibling services.

CI/CD

All Coding Agents must follow docs/runbooks/grouped-ci-cd.md. GitHub is used for branches, PRs, and review only; repository GitHub Actions are disabled and main has no required Actions check. After merge, the Release Controller checks out the explicit commit supplied by the operator and runs its configured release quality gates. The operator must verify that commit is still the exact current origin/main before both the Staging dry run and the at-most-one actual run. Focused pre-merge testing remains the change author's responsibility. Native client releases are validated and signed separately. Prod and infrastructure mutations always require explicit authorization.