From d978730202e125dd1c50c6ab4ab66e762ded903b Mon Sep 17 00:00:00 2001 From: Amirhossein Khalili Date: Thu, 20 Aug 2026 18:44:31 +0330 Subject: [PATCH] docs(import): approve docker bootstrap workflow --- docs/IMPORT-WORKFLOW-SPEC.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/IMPORT-WORKFLOW-SPEC.md b/docs/IMPORT-WORKFLOW-SPEC.md index bd3a769..4edfebb 100644 --- a/docs/IMPORT-WORKFLOW-SPEC.md +++ b/docs/IMPORT-WORKFLOW-SPEC.md @@ -1,6 +1,6 @@ # One-Time CSV-to-PostgreSQL Import Workflow Specification -- Status: Decision-ready draft — stakeholder approval required +- Status: Approved specification — implementation not yet authorized - Capability: Data foundation bootstrap - Depends on: Approved PostgreSQL physical schema - Implementation authorization: Not granted @@ -169,7 +169,7 @@ Progress logging is rate-limited by time or aggregate row milestones rather than - Ask first: replace the dataset, resume or delete failed staging, change batch/resource limits, add Python, alter normalization, or run against a non-empty fact database. - Never: run on a timer, import on every restart, expose an importer port, bake the dataset into an image, auto-migrate in application startup, log raw rows/tokens/secrets, or silently truncate production tables. -## Decision batch for approval +## Resolved decisions 1. Use Bash for Docker orchestration and the compiled Go importer for CSV/database work; do not add Python. 2. Run import during the explicit `first-start.sh` bootstrap, not ordinary container startup or restart.