genichin
362b008940
551777b feat: add interface contract and data model baseline support to bootstrap-baseline f17e086 feat: add bootstrap seed file support to bootstrap-baseline skill be85338 feat: introduce lightweight change path, change-req skill, and release feedback loop 949bb40 docs(skill): new-discovery 병렬 Discovery 및 active-cycle 처리 규칙 강화 7f96130 docs: fix draft-req skill template paths 94b1445 diff --git a/.github/skills/draft-batch-design/SKILL.md b/.github/skills/draft-batch-design/SKILL.md index 5f87d00..944e075 100644 --- a/.github/skills/draft-batch-design/SKILL.md +++ b/.github/skills/draft-batch-design/SKILL.md @@ -1,6 +1,6 @@ --- name: draft-batch-design -description: "Use when: drafting the design document for an existing batch, running /draft-batch-design with a BAT ID, filling docs/batches/<BAT_ID>/design.md, or recording architecture and interface decisions before implementation." +description: "Use when: drafting the design document for an existing batch, running /draft-batch-design with a BAT ID, filling docs/batches/<BAT_ID>/design.md, recording architecture and interface decisions before implementation, or planning updates to docs/project-structure.md and docs/runtime-flows.md." argument-hint: "예: bat-001 또는 docs/batches/bat-001_20260424_scaffold" user-invocable: true --- @@ -9,27 +9,43 @@ user-invocable: true d1ce3ce 프로세스 완전 변경 git-subtree-dir: .vendor/stage-pilot git-subtree-split: 551777bc7009ee133fbaab1267ca324f1dc3c6bb
3.2 KiB
3.2 KiB
Sample Host Project Data Model
- Baseline Mode: declared
- Baseline Seed: .stagepilot/bootstrap/baseline.yaml
- Status: confirmed
- Owner: Platform Team
- Last Updated (KST): 2026-04-30 16:30
- Source Discovery / Batch: bootstrap-baseline
Project Summary
- Python-based API service for curated market data analysis.
Primary Domain
- financial analytics
Primary Persistence Backend
- PostgreSQL
Purpose
- This document captures the initial data model baseline after StagePilot bootstrap.
- It provides a shared reference for later REQ, delivery, migration, and verification work.
Scope
- Covers core entities, relationships, lifecycle rules, and persistence assumptions for the sample host project.
- Does not replace ORM code, migrations, or detailed acceptance criteria.
Model Summary
- Market Snapshot :: normalized raw and curated market data for a tracked symbol
- Analytics Snapshot :: derived metrics computed from a Market Snapshot
Entity: Market Snapshot
- Purpose: represent the latest curated market data for a tracked symbol
- Source of Truth: PostgreSQL
market_snapshotstable - Lifecycle: collected -> normalized -> published -> superseded
Key Fields
symbol:: string :: tracked market identifiercaptured_at:: timestamp :: time the upstream data snapshot was collectedpayload:: json :: normalized market data stored for API responses and analytics inputs
Relationships
Analytics Snapshot:: derived from one published Market Snapshot
State Rules
- only one published snapshot per symbol should be treated as current
- superseded snapshots remain queryable for audit or replay use cases
Entity: Analytics Snapshot
- Purpose: represent derived metrics calculated from a market snapshot
- Source of Truth: PostgreSQL
analytics_snapshotstable - Lifecycle: queued -> computed -> published -> superseded
Key Fields
symbol:: string :: tracked market identifierderived_at:: timestamp :: time analytics were computedmetrics:: json :: derived indicators and summary values
Relationships
Market Snapshot:: source snapshot used to compute analytics
State Rules
- published analytics must reference an existing published or superseded market snapshot
- analytics should be recomputed whenever a new published market snapshot replaces the current one
Shared Consistency Rules
symbolidentifiers must remain consistent across snapshot and analytics entities- analytics records must not exist without a corresponding source market snapshot
Persistence / Integration Notes
- refresh jobs write Market Snapshot rows before recomputing Analytics Snapshot rows
- future retention and archival policies are not defined yet
Current Gaps / Planned Changes
- exact table schema and indexing strategy are still undecided
- historical retention policy is still undecided
Update Triggers
- Update this document when a core entity, key field, or relationship changes.
- Update this document when lifecycle or persistence behavior changes.
- Update this document when a batch introduces a migration, backfill, or breaking data assumption.
Change Log
- 2026-04-30: bootstrap-baseline created the initial data model baseline from declared project inputs.