Giao diện
Sổ quyết định
Trang sinh tự động
Nguồn: docs/decisions/decisions.csv — file dự án dùng để ghi quyết định, có guard decisions:check trong CI. Câu quyết định giữ nguyên văn; bộ sinh chỉ nhóm và đếm.
490 mục.
| Trạng thái | Số mục |
|---|---|
| decided | 472 |
| open | 15 |
| deferred | 3 |
| Loại | Số mục |
|---|---|
| approved | 305 |
| open-item | 137 |
| question | 18 |
| assumption | 14 |
| contradiction | 11 |
| gate | 5 |
Cổng chặn (5)
Cổng là điều kiện chặn phát hành: còn mở thì phần phụ thuộc không được coi là sẵn sàng.
G-PP — open
Câu hỏi: Which physical PiPoint contract (auth/signature, status lookup, pagination, race handling, identity attestation) governs live integration?
Hệ quả nếu phát hành khi còn mở: No live PiPoint connector, live eKYC wallet link/create or live reconciliation transport; releases carry the mock/test double only and live behavior stays labelled not live.
Được làm trước: Adapter boundary, idempotency/status model, mock/test double, audit payload, explicit UNKNOWN/stale states, conformance tests against the double.
Chủ sở hữu: Operations/PiPoint
G-CP — decided
Câu hỏi: Which Campaign/Recurring policies (close condition, skip counting/cutoff, partial shortage) govern live recurring behavior?
Hệ quả nếu phát hành khi còn mở: Interim assumption 2026-10-07 (owner: "assume first, I change later"): the three policies are decided (close = per-product MOQ summed across cycles; skip = customer self-skip with a 72 h cutoff and forfeit review; partial shortage follow-up = DEC-CP-SHORTAGE-FOLLOWUP). Live Recurring is NOT switched on by this record: the code gate campaign.recurring_gate_open() stays a constant false until a task builds an operator go-live switch and UAT of Recurring passes; until then publishing, skip activation and checkout answer policy_undecided naming G-CP. AS-01/02 remain the versioned interim rule for full-Order refund. SUPERSEDED IN PART 2026-10-16 (team decision, #286; status and decision_basis unchanged, history kept): the go-live gate and its operator switch are retired, see DEC-CP-GATE-RETIRED. The three policies above stay interim assumptions.
Được làm trước: Recurring state machine, policy table and versioned evaluator interface, draft/preview, Group Buy, disabled live actions, AS-01/02 tests.
Chủ sở hữu: BO/PO
G-FIN — open
Câu hỏi: Which Finance policies (funds/vouchers, refund thresholds and roles, tolerance, live MoMo) govern manual financial posting and live payment?
Hệ quả nếu phát hành khi còn mở: No manual approval or financial posting in production and no live MoMo; thresholds/tolerance ship only as versioned configuration that fails closed. COD collected is never treated as remitted.
Được làm trước: Mock MoMo, COD collection/remittance state, receipt/refund/reconciliation shell, versioned threshold/tolerance schema with no invented defaults, maker != checker tests.
Chủ sở hữu: Finance/BO/MoMo
G-NOT — decided
Câu hỏi: Which production renderer, channels, templates and deep-link schema deliver CMS content and notifications?
Hệ quả nếu phát hành khi còn mở: Decided 2026-10-05: R1: in-app notifications only, copy keys in app localization, sanitized rich-text CMS, app-route deep links with a not-found fallback (DEC-NOT-*). No production notification delivery or production CMS renderer; in-app inbox/outbox are internal, nothing is sent externally.
Được làm trước: In-app events/outbox with recipient isolation, read-only CMS contract with safe renderer boundary, disabled delivery actions, deep-target fallback states.
Chủ sở hữu: Product/Ops
G-WEB — deferred
Câu hỏi: Which repository, stack, route owner and delivery plan host the User web checkout (UW-PAY-01..03)?
Hệ quả nếu phát hành khi còn mở: Deferred 2026-10-05: Parked by the owner (owner-questions #1): the User web checkout follows the MoMo SDK and is not built in R1. No User web checkout app is created; only the mobile flow with mock MoMo ships.
Được làm trước: Mobile and mock-MoMo work, API contracts for payment, mock scenario control; no new web app or route until decided.
Chủ sở hữu: Product/Architecture
Còn mở (15)
| Mã | Loại | Chủ sở hữu | Câu hỏi |
|---|---|---|---|
G-PP | gate | Operations/PiPoint | Which physical PiPoint contract (auth/signature, status lookup, pagination, race handling, identity attestation) governs live integration? |
DEC-PP-RACE | question | Operations/PiPoint | What idempotency and ordering guarantees does PiPoint give for concurrent or duplicate ISSUE/RELEASE/REDEEM requests, and how must the connector handle races? |
G-FIN | gate | Finance/BO/MoMo | Which Finance policies (funds/vouchers, refund thresholds and roles, tolerance, live MoMo) govern manual financial posting and live payment? |
DEC-FIN-TOLERANCE | question | Finance | What tolerance is accepted for MoMo amount or fee differences in reconciliation (OI-05)? |
DEC-FIN-MOMO-LIVE | question | BO/Finance | What is the live MoMo contract: fees, automatic refund support, reconciliation data format and callback security (OI-03)? |
DEC-AUTH-RECOVERY | open-item | Security/Support | How is identity recovery performed, and by whom with which audit, for legacy accounts without a verified phone (OTP-only, social or email-only)? |
DEC-S-CMS-LEGAL | contradiction | Legal | Who supplies and approves the Sale collaboration terms and privacy policy content shown in S45? |
DEC-DS-S-HERO-AA | open-item | Design (not decided by P0-12; the gate records a documented exception until the owner answers) | Does the Sale link hero keep the design-system gradient (orange to red to red-d) under white 10.5 to 15.5px text (2.6:1 on orange, 3.8:1 on red, 4.8:1 on red-d) as a documented contrast exception, or must the gradient s… |
DEC-DS-S-WARN-TEXT | open-item | Design (not decided by P0-12; the gate records a documented exception until the owner answers) | Does the Sale warning tone keep gold (#F5A30B) for text and button fills (white action text 2.1:1, gold on the warning tint 1.9:1, P0-28-D1 and D2), or must the warning text role map to the text-safe gold-ink (#8A5300, … |
DEC-DS-S-TAP-SIZE | open-item | Design (not decided by P0-12; the gate records a documented exception until the owner answers) | Are Sale hit areas 44px (Sale DS floor, iOS; hero Copy and Share buttons and PiSearchField) or 48dp on Android like PiButton (SALE-TAP-44 in the P0-12 gate)? |
DEC-DS-S-KIT-GAPS | open-item | Design (not decided by P0-12; the gate records a documented exception until the owner answers) | Which task adds each Sale component that approved frames draw but pi_ui does not export (stepper and ID-photo upload, rejection panel, contributing-order row, campaign picker, QR sheet, timeline, referral steps, profile… |
DEC-UPLOAD-AV | open-item | Security | Which malware-scan product and upload size policy protect private uploaded documents? |
DEC-G2S-GAP-09 | open-item | Owner / Design (#422; owner 28/10: canvas chưa chốt) | Khi canvas design Mua định kỳ được chốt và xuất, màn User App nào phải sửa để khớp bản chốt? |
DEC-G2S-GAP-11 | open-item | Owner / Product (#422; follow-up của GAP-G2S-01) | Nội dung G2-01 / U-20 lấy từ module Quản lý banner / content (BR-KPD-01) qua API nào và màn Admin nào soạn? |
DEC-G2S-GAP-12 | open-item | Owner / Product (#422; follow-up của GAP-G2S-03) | Số "+{n} hôm nay" của chiến dịch Mua định kỳ do Admin nhập theo chiến dịch ở module nào (hoặc hệ thống tính nếu Product đổi ý)? |
Hoãn (3)
| Mã | Loại | Chủ sở hữu | Câu hỏi |
|---|---|---|---|
G-WEB | gate | Product/Architecture | Which repository, stack, route owner and delivery plan host the User web checkout (UW-PAY-01..03)? |
DEC-WEB-CHECKOUT | question | Product/Architecture | Which repository, stack, route owner and delivery plan host the User web checkout surface (UW-PAY-01..03)? |
DEC-G2S-GAP-22 | open-item | Owner (29/10/2026, #422; design 29/10) | Ở G2-07 biến thể chưa có Ví của tôi, dòng Thưởng cam kết hiện thế nào khi FuncSpec ghi "vào ví chờ" nhưng hệ thống ghi NO_PIPOINT_ACCOUNT (không phát, không phát bù)? |
Đã quyết
472 mục đã quyết. Không liệt kê hết ở đây vì danh sách dài và nội dung thuộc từng module — tra theo mã trong docs/decisions/decisions.csv, hoặc xem Nhật ký kiến trúc cho các quyết định về kiến trúc và hạ tầng.
Mã quyết định xuất hiện trong comment của code (ví dụ DEC-VQM-18, DEC-377-DEPOSIT-RETRY-SAME-ORDER), nên tra ngược từ code về quyết định được.