q792602257/agentic-mobile-control
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(workspace): record packaging boundary

Browse Source
This commit is contained in:
q792602257
2026-07-12 14:29:55 +08:00
parent 2e2ca9dc7d
commit c94b3efe87
3 changed files with 19 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/CONSTITUTION.md
+12 -1
View File
@@ -40,12 +40,23 @@ LLM dependencies enter at `runtime` through Planner behavior. HTTP and MCP
dependencies enter at `api`. No LLM, HTTP, or MCP dependency may appear in dependencies enter at `api`. No LLM, HTTP, or MCP dependency may appear in
`core`, `driver`, `device`, or `tools`. `core`, `driver`, `device`, or `tools`.
## Packaging Boundary
The repository is a uv workspace with `device-agent-runtime` as the root
member and outer platform packages as separate members. The cloud platform is
owned by `packages/cloud-platform` and may depend on the Runtime through an
explicit workspace source; the Runtime distribution must never depend on or
package `cloud`.
All Python members share the committed root `uv.lock`. The Vue/Vite `console/`
remains outside the Python workspace and keeps its independent npm lifecycle.
## Change Discipline ## Change Discipline
Future changes must keep the dependency direction: Future changes must keep the dependency direction:
`core` -> `driver`/`device` -> `tools` -> `perception` -> `storage` -> `runtime` `core` -> `driver`/`device` -> `tools` -> `perception` -> `storage` -> `runtime`
-> `api`. -> `api` -> optional outer workspace applications.
When a change needs a new external integration, add it at the adapter layer When a change needs a new external integration, add it at the adapter layer
that owns that concern, not at the domain or device boundary. that owns that concern, not at the domain or device boundary.
docs/ROADMAP.md
+6
View File
@@ -80,6 +80,12 @@ coordinated execution while preserving the same device/runtime boundaries.
Add device pools, scheduling, plugins, and platform APIs for distributed Add device pools, scheduling, plugins, and platform APIs for distributed
execution across many devices. execution across many devices.
The packaging baseline is complete: `device-agent-runtime` remains the root uv
workspace member, while the existing `cloud` modules and SDK are published by
the one-way dependent `device-cloud-platform` member under
`packages/cloud-platform`. A deployable control plane and Host Agent execution
loop remain separate follow-up work.
## Long-Term Direction ## Long-Term Direction
The long-term v2.0 direction is a "DeviceOS" / Universal Device Runtime: one The long-term v2.0 direction is a "DeviceOS" / Universal Device Runtime: one
openspec/changes/uv-workspace-packaging/tasks.md
+1 -1
View File
@@ -36,4 +36,4 @@
- [x] 5.1 Run OpenSpec validation for `uv-workspace-packaging` and confirm all workspace-packaging scenarios are covered by automated checks. - [x] 5.1 Run OpenSpec validation for `uv-workspace-packaging` and confirm all workspace-packaging scenarios are covered by automated checks.
- Strict OpenSpec validation passed. Sync/lock, member metadata, dependency direction, import compatibility, wheel ownership, isolated installation, Runtime entry points, and frontend independence were covered by automated commands or tests. - Strict OpenSpec validation passed. Sync/lock, member metadata, dependency direction, import compatibility, wheel ownership, isolated installation, Runtime entry points, and frontend independence were covered by automated commands or tests.
- [ ] 5.2 Update the project index and runtime/package documentation to record the new workspace layout and canonical commands. - [x] 5.2 Update the project index and runtime/package documentation to record the new workspace layout and canonical commands.