2 Commits

Include renames

Author	SHA1	Message	Date
chenchenandClaude Opus 4.8	5dc99946f0	docs(design): HM product tiers (Individual/Teams/Enterprise) + commercialization boundaries ... Aligns HM's capabilities to three tiers mirroring Claude's proven split, grounded in HM's existing primitives. Defines positioning + billing per tier, a capability × tier matrix (use layer = Individual; manage/allocate = Teams; compliance/hard- enforcement/private = Enterprise) with HM code landing points, the Teams-hook vs Enterprise-moat rationale, HM's differentiators over Claude (gateway-side hard cost control, signed per-org policy push, server-side hard enforcement, native agent catalog), a P0–P3 rollout mapping, and the open pricing decisions to settle. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-05 16:53:44 +08:00
chenchenandClaude Opus 4.8	88240dc79e	docs(design): HM team-control design referencing Claude Code enterprise paradigm ... Synthesizes Claude's admin-setup/authentication/server-managed-settings/settings/ managed-mcp/auto-mode docs into a team-management design for HM, mapped onto the analogy (client≈Claude Code, HM≈Claude.ai admin console, AM≈cloud agent) and grounded in HM's existing primitives (new-api users/groups/sk-token model-limits/ quota, plus our V2 device auth, resource bindings, agent templates, /v1 gateway). Covers org/team/seat model, roles, allocation, managed-settings push over the V2 channel, managed agent/tool catalog, auth/SSO, auto-mode, audit, and a phased plan. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-05 16:27:50 +08:00