niuniu/lijiaoqiao
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(sql): clarify active schema boundaries and status constraints

Browse Source
This commit is contained in:
Your Name
2026-04-17 20:12:05 +08:00
parent ebd11867c3
commit f48fca565b
5 changed files with 676 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
sql/postgresql/platform_core_schema_v1.sql
View File

@@ -1,5 +1,10 @@
-- Platform core schema baseline (PostgreSQL 15)
-- Purpose: provide non-supply core domain tables required by PRD P0/P1.
-- Boundary:
-- - This file is the platform-side fresh setup baseline under repository root /sql/postgresql.
-- - audit_events in this file belongs to the platform/core domain timeline.
-- - It is not the same baseline as supply-api/sql/postgresql/partition_strategy_v1.sql.
-- - Do not stack both audit_events definitions into one fresh database without an explicit schema/database split.
-- Updated: 2026-03-27
BEGIN;

4
sql/postgresql/token_runtime_schema_v1.sql
View File

@@ -1,5 +1,9 @@
-- Token runtime schema baseline (PostgreSQL 15)
-- Purpose: persistent storage for platform token lifecycle and audit timeline.
-- Boundary:
-- - auth_platform_tokens and auth_token_audit_events belong only to platform-token-runtime.
-- - auth_token_audit_events is the token-runtime local audit timeline, not a replacement for platform_core_schema_v1.sql::audit_events.
-- - This file can be initialized independently from the platform core schema.
-- Updated: 2026-03-30
BEGIN;