菜单
System architecture facts: components, data flow, integration boundaries. Load when implementing cross-component features, debugging integration issues, or onboarding to the codebase. Topics: Event sourcing for the billing audit log.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Project coding conventions extracted from chat history. Load when writing new code, naming things, designing APIs, or reviewing PRs. Topics: Cursor pagination is mandatory for all paged GraphQL endpoints.
Technical decisions made for this project, with reasoning and rejected alternatives. Load when proposing architectural changes, evaluating alternatives, or asked why a choice was made. Topics: Adopt OAuth 2.0 authorization code flow with PKCE for the customer portal SPA.
| name | ai-memory-system-architecture |
| description | System architecture facts: components, data flow, integration boundaries. Load when implementing cross-component features, debugging integration issues, or onboarding to the codebase. Topics: Event sourcing for the billing audit log. |
Auto-generated by ai-memory from AI chat history. Edit memories via
ai-memory list/extract/resolverather than this file — it is fully regenerated on everyai-memory rules --target skills.
The billing domain becomes event-sourced. The source of truth is an append-only billing_events Postgres table (InvoiceCreated, LineItemAdjusted, PaymentCaptured, etc.), each row carrying a SHA-256 hash chain over (prev_hash, payload, timestamp). The current invoices table becomes a read-side projection rebuilt from the log. The rest of the app stays on the existing CRUD model — only billing needs this.
Why: Event sourcing answers compliance directly: every state change is a first-class, immutable record. Hash-chaining provides tamper evidence without an external service. Scoping to billing keeps the operational cost contained.
Rejected: Shadow-table journaling rejected — couples write-side logic to bookkeeping and does not give tamper evidence. External audit-log service rejected — added vendor cost without measurable gain over an in-database hash chain.
