diff --git a/docs/user-stories.md b/docs/user-stories.md index 8e58b1a..5d13c2d 100644 --- a/docs/user-stories.md +++ b/docs/user-stories.md @@ -1,20 +1,21 @@ # AITokenPool — Product User Stories -> v1.0（2026-08-14）· Core product-design document. UI/backend implementations follow this document. -> Aligned with [docs/architecture.md](./architecture.md) and the UI prototype in [`ui/`](../ui/). +> **v1.1（2026-08-14）· Restructured.** The document is now organized by **deployment scenario first, then user type** (场景 → 用户类型 → story): `## 公共场景 Public` / `## 企业场景 Enterprise`, each listing its user types with Goals / Pain points / User stories / Key flows. Content from v1.0 is reused, with ownership re-assigned to scenes. +> v1.0（2026-08-14）· Initial version (flat role layout). +> Core product-design document. UI/backend implementations follow this document. Aligned with [docs/architecture.md](./architecture.md) and the UI prototype in [`ui/`](../ui/). --- -## 1. Product Model & Terminology +## 1. Product Model & Terminology（产品模型与术语） **One product, two deployment scenarios** (not two feature sets): -- **Public edition** — deployed on the public internet. Anyone can register, share idle API keys to earn points, and spend points to consume models shared by others. -- **Enterprise edition** — deployed on an internal network. The administrator (IT) puts purchased keys into the key pool and allocates monthly point quotas to members. +- **Public edition（公共版）** — deployed on the public internet. Anyone can register, share idle API keys to earn points, and spend points to consume models shared by others. +- **Enterprise edition（企业版）** — deployed on an internal network. The administrator (IT) puts purchased keys into the key pool and allocates monthly point quotas to members. The feature set is **identical**; the difference is *who is motivated to share* (everyone in public; only the admin in enterprise). **Roles are permission differences, not product differences** — the admin additionally sees the Admin view (key pool / members / usage reports / organization), regular users do not. -### Core mechanism +### Core mechanism（核心机制） | Term | Definition | |---|---| @@ -27,70 +28,60 @@ The feature set is **identical**; the difference is *who is motivated to share* | **Quota / allocation (配额/分配)** | Enterprise: monthly point quota per department and per member. | | **Admin view** | Role-only view: key pool management, member management, usage reports, organization (department) management. | -### Architecture (from docs/architecture.md) +### Architecture（架构，from docs/architecture.md） Centralized (方案 A): **the platform hosts keys and executes calls** — the platform is the only trusted executor. Metering is trustworthy, responses are real (direct upstream connection), and there is no tampering/cheating surface. Layered: Gateway (axum) · Key pool (encrypted) · Metering engine (token counting) · Ledger (points) · Marketplace (sharing) · Admin console (Web). --- -## 2. Role Definitions +## 2. 公共场景 Public Scenario（公共场景） -### R1. Visitor / New User（访客 / 新用户） +> **Scene description（场景说明）**: The public edition is deployed on the **public internet** — anyone can register, share idle keys, and consume models with points. **Everyone has sharing motivation** (monetize idle subscription quota), so the sharing marketplace is the core of this scene. Registration is open; roles are determined by the account (the platform operator is planned, not yet implemented). The feature set is identical to the enterprise edition; only *who shares* differs. -| | | -|---|---| -| **Identity** | Unregistered person who reached the platform (public edition; also applies to a prospective employee in enterprise). | -| **Goals** | Understand what AITokenPool is, how points work, which models are available and at what price; register/login with minimal friction. | -| **Pain points** | No idea how AI token sharing works; fear of leaking their own API key; unclear pricing; registration friction (must choose a plan before seeing anything). | +### 2.1 用户类型 A — 访客 / 新用户 Visitor / New User（未注册，浏览了解） -### R2. Regular User, Public Edition（普通用户 · 公共版） +#### Goals（目标） -| | | -|---|---| -| **Identity** | Registered public user. | -| **Goals** | Get points (top up / earn), browse the marketplace, consume models (chat or API) with points, track balance and transactions. | -| **Pain points** | Balance runs out mid-task; no single place to see spend vs. earnings; expensive flagship models drain points quickly; not sure which shared key is reliable. | +- Understand what AITokenPool is, how points work, which models are available and at what price. +- Register/login with minimal friction and start using the platform. -### R3. Sharer（分享者 —— 公共版普通用户的一种行为角色） +#### Pain points（痛点） -| | | -|---|---| -| **Identity** | A regular public user who has idle subscription quota (Claude/ChatGPT/GLM/DeepSeek…) and wants to monetize it. | -| **Goals** | List an idle key in seconds (provider/model, declared quota, key — nothing else), have the platform price it, earn points when others consume, monitor earnings, pause/resume/relist/delete listings at will. | -| **Pain points** | Worries about key security (platform must encrypt & never display plaintext to others); worried about one user draining the quota; wants to stop sharing at any time; wants clarity on what they earned and why. | +- No idea how AI token sharing works; fear of leaking their own API key; unclear pricing; registration friction (must choose a plan before seeing anything). -### R4. Enterprise Admin（企业管理员） +#### User Stories（用户故事） -| | | -|---|---| -| **Identity** | IT/administrator of an enterprise deployment (internal network). | -| **Goals** | Configure the key pool (add/revoke upstream keys), manage departments (CRUD + monthly point allocation), manage members (top-up, change department), review usage reports by model/member to control cost. | -| **Pain points** | Cost overrun by a few heavy users; members in the wrong department; keys hitting quota limits unnoticed; no visibility into which model consumes the budget; new members landing without a department. | +- **US-1** As a visitor, I want to browse the model marketplace before registering, so that I can evaluate models and prices first. + - AC: Marketplace is browsable without login; search, provider filter, and sort (price/context) work; prices shown in points with USD/CNY reference. +- **US-2** As a visitor, I want to see a clear explanation of the points mechanism (1 USD = 1,000 points), so that I can decide whether to join. + - AC: Points explanation visible from the landing/login page; conversion rate stated explicitly. +- **US-3** As a new user, I want to register/login with an email, so that I can start using the platform. + - AC: Single login entry (no public/enterprise choice at login); registration creates an account with zero points; role (admin vs. user) is determined by the account. -### R5. Enterprise Member（企业成员） +#### Key Flow（关键流程）— browse → understand → register -| | | -|---|---| -| **Identity** | An employee with points allocated by the admin. | -| **Goals** | Use models through one entry point with allocated points, view transactions, request more points when running low. | -| **Pain points** | Doesn't know how many points they have; gets blocked mid-work when quota runs out; unclear how to request more; no record of what they spent. | +```mermaid +flowchart LR + A[Land on platform] --> B[Browse marketplace without login] + B --> C[Learn points mechanism] + C --> D[Register / login] + D --> E[Account created with 0 points] +``` ---- +1. Visitor lands on the login page and browses models/pricing first (US-1, US-2). +2. Registers with email → account with 0 points (US-3); continues into the Regular User flow (J-1). -## 3. User Stories +### 2.2 用户类型 B — 普通用户（消费者）Regular User / Consumer（注册，用点数消费模型） -Format: **"As a \, I want \, so that \."** Each story lists Acceptance Criteria (AC). +#### Goals（目标） -### 3.1 Visitor / New User +- Get points (top up / earn), browse the marketplace, consume models (chat or API) with points, track balance and transactions. -- **US-1** As a visitor, I want to browse the model marketplace before registering, so that I can evaluate models and prices first. - - AC: Marketplace is browsable without login; search, provider filter, and sort (price/context) work; prices shown in points with USD/CNY reference. -- **US-2** As a visitor, I want to see a clear explanation of the points mechanism (1 USD = 1,000 points), so that I can decide whether to join. - - AC: Points explanation visible from the landing/login page; conversion rate stated explicitly. -- **US-3** As a new user, I want to register/login with an email, so that I can start using the platform. - - AC: Single login entry (no public/enterprise choice at login); registration creates an account with zero points; role (admin vs. user) is determined by the account. +#### Pain points（痛点） -### 3.2 Regular User（Public） +- Balance runs out mid-task; no single place to see spend vs. earnings; expensive flagship models drain points quickly; not sure which shared key is reliable. + +#### User Stories（用户故事） - **US-4** As a regular user, I want to top up points, so that I can consume models. - AC: Wallet shows current balance; top-up flow (placeholder per current prototype: 充值/提现 temporarily unsupported, "即将上线") reflects into balance and a "topup" transaction record. @@ -101,51 +92,7 @@ Format: **"As a \, I want \, so that \."** Each stor - **US-7** As a regular user, I want to view my transactions, so that I can reconcile my spend and earnings. - AC: Transactions page is the single source of truth for consume/earn/topup/withdraw; tabs (all/consume/earn) + MRT-style table with column sort, column filter, pagination; wallet page links to it. -### 3.3 Sharer - -- **US-8** As a sharer, I want to list an idle key with just provider/model/declared quota, so that I can start earning points with minimal effort. - - AC: Listing form requires provider, model, API key (password input), declared quota; reference price auto-computed from model price table (fallback default price if model has no pricing data — no error); platform stores key encrypted; key never shown in plaintext to others. -- **US-9** As a sharer, I want to see my listings with masked keys, quota usage, and earnings, so that I can monitor performance. - - AC: Sharing page shows statistics + my listings (key masked like `sk-****1234`); each row shows used/quota, unit price, total earnings, status. -- **US-10** As a sharer, I want to pause/resume/relist/delete a listing, so that I control when my key is consumed. - - AC: Pause = stop taking requests, resumable; delete = permanent removal from platform, irreversible, requires confirmation; relist reactivates a paused/off listing. -- **US-11** As a sharer, I want to know when my key is consumed, so that I can see earnings accumulating. - - AC: Each consumption creates an "earn" transaction (partner model, tokens, +points); notification toggle in Settings ("共享 key 被消费时通知"). - -### 3.4 Enterprise Admin - -- **US-12** As an enterprise admin, I want to add upstream keys to the key pool, so that members can use purchased models. - - AC: Admin view → Key pool: add key (provider/model/key/quota); key shown masked; statuses ok / limit / exhausted / revoked; revoke disables a key immediately. -- **US-13** As an enterprise admin, I want to manage departments (CRUD + monthly point allocation), so that budget is distributed per organization structure. - - AC: Organization tab: department list with member count, monthly allocation, used, remaining, status; add/edit/delete department; deleting a department leaves its members "unassigned" (未分配) — see E-03. -- **US-14** As an enterprise admin, I want to manage members (top-up / change department), so that individuals get the right quota and access. - - AC: Member tab: change department via dropdown (existing departments + "未分配"); arbitrary top-up amount with **positive-integer validation**; new registered members default to "unassigned". -- **US-15** As an enterprise admin, I want usage reports by model and by member, so that I can control cost and spot heavy users. - - AC: Usage tab shows by-model and by-member point consumption; numbers consistent with the ledger. -- **US-16** As an enterprise admin, I want to optionally close external registration, so that the enterprise deployment stays internal-only. - - AC: Organization settings include "关闭外部注册（企业内网部署）" switch; when enabled, only invited/existing accounts can log in. - -### 3.5 Enterprise Member - -- **US-17** As an enterprise member, I want to log in and see my allocated points, so that I know my budget. - - AC: Dashboard/wallet shows balance = allocation − consumed; monthly allocation visible. -- **US-18** As an enterprise member, I want to consume models through the same marketplace UI, so that I use any model from the key pool with one entry point. - - AC: Same marketplace/chat/API flow as public; consumption deducts from member points; insufficient balance blocks with a clear message. -- **US-19** As an enterprise member, I want to view my transaction records, so that I can see what I spent and when. - - AC: Transactions page lists consume records (and any admin top-up adjustments) with timestamps. -- **US-20** As an enterprise member, I want to request more points when my balance is low, so that I can keep working. - - AC: Low-balance notification (Settings toggle); request flow (per prototype: "成员自助申请加额需管理员审批" toggle in org settings); request reaches admin. - -### 3.6 Shared (all users) — API Key Management - -- **US-21** As any user, I want to manage platform API keys (CRUD + one-click copy), so that I can integrate tools/scripts securely. - - AC: Settings → API Key: generate with a name; rename; delete requires confirmation ("删除后该 key 立即失效"); search by name; list shows masked values (`atk_live_****xxxx`); copy provides the full value, with a `file://` fallback (select + Ctrl/Cmd+C) when clipboard API is restricted. - ---- - -## 4. Key User Journeys - -### J-1 Public: New user — register to first consumption +#### Key Flow（关键流程）— J-1: register → first consumption ```mermaid flowchart LR @@ -165,7 +112,28 @@ flowchart LR 5. Picks an available model and consumes via chat/API (US-6). 6. Points deducted per metered tokens; checks Transactions for the record (US-7). -### J-2 Public: Sharer — upload key to first earning +### 2.3 用户类型 C — 分享者 Sharer（普通用户的行为角色：上架闲置 key 赚点数） + +#### Goals（目标） + +- List an idle key in seconds (provider/model, declared quota, key — nothing else), have the platform price it, earn points when others consume, monitor earnings, pause/resume/relist/delete listings at will. + +#### Pain points（痛点） + +- Worries about key security (platform must encrypt & never display plaintext to others); worried about one user draining the quota; wants to stop sharing at any time; wants clarity on what they earned and why. + +#### User Stories（用户故事） + +- **US-8** As a sharer, I want to list an idle key with just provider/model/declared quota, so that I can start earning points with minimal effort. + - AC: Listing form requires provider, model, API key (password input), declared quota; reference price auto-computed from model price table (fallback default price if model has no pricing data — no error); platform stores key encrypted; key never shown in plaintext to others. +- **US-9** As a sharer, I want to see my listings with masked keys, quota usage, and earnings, so that I can monitor performance. + - AC: Sharing page shows statistics + my listings (key masked like `sk-****1234`); each row shows used/quota, unit price, total earnings, status. +- **US-10** As a sharer, I want to pause/resume/relist/delete a listing, so that I control when my key is consumed. + - AC: Pause = stop taking requests, resumable; delete = permanent removal from platform, irreversible, requires confirmation; relist reactivates a paused/off listing. +- **US-11** As a sharer, I want to know when my key is consumed, so that I can see earnings accumulating. + - AC: Each consumption creates an "earn" transaction (partner model, tokens, +points); notification toggle in Settings ("共享 key 被消费时通知"). + +#### Key Flow（关键流程）— J-2: upload key → first earning ```mermaid flowchart LR @@ -184,7 +152,54 @@ flowchart LR 4. Other users consume → sharer earns points, `earn` transaction + notification (US-11). 5. Sharer monitors earnings; pauses/resumes/re-lists/deletes at will (US-10). -### J-3 Enterprise: Admin — key pool to employees using models +### 2.4 用户类型 D — 平台运营者 / 管理员 Platform Operator / Admin（规划中 Planned） + +#### Goals（目标，规划中） + +- Moderate the public marketplace, handle violations/abuse, monitor market health (success rates, availability), and maintain trust. + +#### Pain points（痛点，规划中） + +- Abusive sharers (fake keys, over-declared quota), unreliable listings hurting consumer trust, and no operational console today. + +#### User Stories（用户故事，规划中） + +> **规划中（Planned）**: the operator role is not yet defined in the current prototype (`ui/` has no operator view). Stories will be added in a later iteration; the centralization architecture (platform-hosted keys) already gives the operator the technical levers (revoke, suspend, audit) needed to enforce moderation. + +#### Key Flow（关键流程，规划中） + +- TBD — will be defined when the operator console is scoped. + +--- + +## 3. 企业场景 Enterprise Scenario（企业场景） + +> **Scene description（场景说明）**: The enterprise edition is deployed on an **internal network**. The administrator (IT) purchases model plans, puts keys into the key pool, and allocates monthly point quotas to departments/members. **Only the admin has sharing (key-provisioning) motivation**; members consume with allocated points through one entry point. External registration can be closed to keep the deployment internal-only. Feature set identical to public; the Admin view is role-gated. + +### 3.1 用户类型 A — 企业管理员 Enterprise Admin（IT：配置 key 池、部门管理、成员管理、用量报表） + +#### Goals（目标） + +- Configure the key pool (add/revoke upstream keys), manage departments (CRUD + monthly point allocation), manage members (top-up, change department), review usage reports by model/member to control cost. + +#### Pain points（痛点） + +- Cost overrun by a few heavy users; members in the wrong department; keys hitting quota limits unnoticed; no visibility into which model consumes the budget; new members landing without a department. + +#### User Stories（用户故事） + +- **US-12** As an enterprise admin, I want to add upstream keys to the key pool, so that members can use purchased models. + - AC: Admin view → Key pool: add key (provider/model/key/quota); key shown masked; statuses ok / limit / exhausted / revoked; revoke disables a key immediately. +- **US-13** As an enterprise admin, I want to manage departments (CRUD + monthly point allocation), so that budget is distributed per organization structure. + - AC: Organization tab: department list with member count, monthly allocation, used, remaining, status; add/edit/delete department; deleting a department leaves its members "unassigned" (未分配) — see E-03. +- **US-14** As an enterprise admin, I want to manage members (top-up / change department), so that individuals get the right quota and access. + - AC: Member tab: change department via dropdown (existing departments + "未分配"); arbitrary top-up amount with **positive-integer validation**; new registered members default to "unassigned". +- **US-15** As an enterprise admin, I want usage reports by model and by member, so that I can control cost and spot heavy users. + - AC: Usage tab shows by-model and by-member point consumption; numbers consistent with the ledger. +- **US-16** As an enterprise admin, I want to optionally close external registration, so that the enterprise deployment stays internal-only. + - AC: Organization settings include "关闭外部注册（企业内网部署）" switch; when enabled, only invited/existing accounts can log in. + +#### Key Flow（关键流程）— J-3: key pool → employees using models ```mermaid flowchart LR @@ -204,7 +219,28 @@ flowchart LR 5. Employee logs in, sees allocated quota (US-17), consumes via marketplace (US-18). 6. Admin reviews usage reports by model/member and rebalances budget (US-15). -### J-4 Enterprise: Employee — login to consume to requesting more points +### 3.2 用户类型 B — 企业成员（员工）Enterprise Member / Employee（用管理员分配的点数消费、查看交易、申请加额） + +#### Goals（目标） + +- Use models through one entry point with allocated points, view transactions, request more points when running low. + +#### Pain points（痛点） + +- Doesn't know how many points they have; gets blocked mid-work when quota runs out; unclear how to request more; no record of what they spent. + +#### User Stories（用户故事） + +- **US-17** As an enterprise member, I want to log in and see my allocated points, so that I know my budget. + - AC: Dashboard/wallet shows balance = allocation − consumed; monthly allocation visible. +- **US-18** As an enterprise member, I want to consume models through the same marketplace UI, so that I use any model from the key pool with one entry point. + - AC: Same marketplace/chat/API flow as public; consumption deducts from member points; insufficient balance blocks with a clear message. +- **US-19** As an enterprise member, I want to view my transaction records, so that I can see what I spent and when. + - AC: Transactions page lists consume records (and any admin top-up adjustments) with timestamps. +- **US-20** As an enterprise member, I want to request more points when my balance is low, so that I can keep working. + - AC: Low-balance notification (Settings toggle); request flow (per prototype: "成员自助申请加额需管理员审批" toggle in org settings); request reaches admin. + +#### Key Flow（关键流程）— J-4: login → consume → request more points ```mermaid flowchart LR @@ -227,26 +263,39 @@ flowchart LR --- -## 5. Edge & Exception Scenarios +## 4. 跨场景通用能力 Cross-Scene Shared Capability（两个场景共有） -| # | Scenario | Expected behavior | -|---|---|---| -| E-01 | **Key invalid / revoked**（key 失效/被撤销） | Listing shows status (public: off/paused; enterprise: revoked); requests routed away from it; consumer sees "key unavailable" instead of an error loop; sharer/admin can re-upload or remove. | -| E-02 | **Quota exhausted**（额度用尽） | Key pool status → `exhausted` / listing stops taking requests; no further deduction attempted; admin sees limit/exhausted states to re-provision; consumer gets a clear "quota exhausted, pick another" message. | -| E-03 | **Department deleted**（部门被删除） | Members of the deleted department become **unassigned (未分配)**; they are not counted in any department summary; admin can re-assign them; their points balance is untouched. | -| E-04 | **Insufficient points**（点数不足） | Request is blocked before any upstream call; clear message with current balance and required points; no negative balance allowed; user is directed to top up / request more. | -| E-05 | **API key leak / compromise**（API Key 泄露） | Settings: delete key immediately (with confirmation, "删除后该 key 立即失效"); platform-issued keys are revocable and take effect instantly; users are encouraged to rotate; upstream keys are never exposed in plaintext anywhere in the UI. | -| E-06 | **New member, no department**（新成员未分配） | New registrations default to **unassigned**; they still receive the default member quota (per org settings); admin assigns them later. | -| E-07 | **Model with no pricing data**（模型无定价数据） | Listing still succeeds with the "default price" fallback; marketplace shows the price; later iterations may add pricing. | -| E-08 | **Top-up with invalid amount**（非法充值金额） | Admin arbitrary top-up validates **positive integer**; zero/negative/non-numeric input is rejected with a message. | -| E-09 | **Clipboard restricted (file://)**（剪贴板受限） | One-click copy falls back to select-the-key + Ctrl/Cmd+C guidance, so the user can still obtain the full key. | -| E-10 | **Single heavy user draining budget** | Usage reports (by member) surface it; admin can top up/adjust or change department allocation; low-balance alerts help the member self-regulate. | -| E-11 | **Availability flapping**（可用性抖动） | Marketplace shows `busy` availability for models with no ready key; retry/choose-another guidance; no silent failure. | -| E-12 | **Duplicate / conflicting listings of the same key** | Platform detects the same upstream key listed twice and warns the sharer; prevents double counting of the same quota. | +### 4.1 API Key 管理 API Key Management（所有用户） + +- **US-21** As any user, I want to manage platform API keys (CRUD + one-click copy), so that I can integrate tools/scripts securely. + - AC: Settings → API Key: generate with a name; rename; delete requires confirmation ("删除后该 key 立即失效"); search by name; list shows masked values (`atk_live_****xxxx`); copy provides the full value, with a `file://` fallback (select + Ctrl/Cmd+C) when clipboard API is restricted. + +> 适用场景（Applies to）: **公共 + 企业**（公共版用户与企业管理员的平台 API Key 都走同一设置页）。 + +--- + +## 5. Edge & Exception Scenarios（边界 / 异常场景） + +> 标注所属场景：**【公共】** 公共场景 · **【企业】** 企业场景 · **【通用】** 两个场景通用。 + +| # | 场景 Scenario | 所属场景 Scene | Expected behavior | +|---|---|---|---| +| E-01 | **Key invalid / revoked**（key 失效/被撤销） | 【通用】 | Listing shows status (public: off/paused; enterprise: revoked); requests routed away from it; consumer sees "key unavailable" instead of an error loop; sharer/admin can re-upload or remove. | +| E-02 | **Quota exhausted**（额度用尽） | 【通用】 | Key pool status → `exhausted` / listing stops taking requests; no further deduction attempted; admin sees limit/exhausted states to re-provision; consumer gets a clear "quota exhausted, pick another" message. | +| E-03 | **Department deleted**（部门被删除） | 【企业】 | Members of the deleted department become **unassigned (未分配)**; they are not counted in any department summary; admin can re-assign them; their points balance is untouched. | +| E-04 | **Insufficient points**（点数不足） | 【通用】 | Request is blocked before any upstream call; clear message with current balance and required points; no negative balance allowed; user is directed to top up / request more. | +| E-05 | **API key leak / compromise**（API Key 泄露） | 【通用】 | Settings: delete key immediately (with confirmation, "删除后该 key 立即失效"); platform-issued keys are revocable and take effect instantly; users are encouraged to rotate; upstream keys are never exposed in plaintext anywhere in the UI. | +| E-06 | **New member, no department**（新成员未分配） | 【企业】 | New registrations default to **unassigned**; they still receive the default member quota (per org settings); admin assigns them later. | +| E-07 | **Model with no pricing data**（模型无定价数据） | 【公共】 | Listing still succeeds with the "default price" fallback; marketplace shows the price; later iterations may add pricing. | +| E-08 | **Top-up with invalid amount**（非法充值金额） | 【企业】 | Admin arbitrary top-up validates **positive integer**; zero/negative/non-numeric input is rejected with a message. | +| E-09 | **Clipboard restricted (file://)**（剪贴板受限） | 【通用】 | One-click copy falls back to select-the-key + Ctrl/Cmd+C guidance, so the user can still obtain the full key. | +| E-10 | **Single heavy user draining budget**（单个重度用户耗尽预算） | 【企业】 | Usage reports (by member) surface it; admin can top up/adjust or change department allocation; low-balance alerts help the member self-regulate. | +| E-11 | **Availability flapping**（可用性抖动） | 【公共】 | Marketplace shows `busy` availability for models with no ready key; retry/choose-another guidance; no silent failure. | +| E-12 | **Duplicate / conflicting listings of the same key**（同一 key 重复/冲突上架） | 【公共】 | Platform detects the same upstream key listed twice and warns the sharer; prevents double counting of the same quota. | --- -## 6. Alignment with UI Prototype & Architecture +## 6. Alignment with UI Prototype & Architecture（与 UI 原型 / 架构对齐） | Aspect | Source of truth | Alignment | |---|---|---|