diff --git a/AGENTS.md b/AGENTS.md
index faf2660..e810593 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -28,9 +28,9 @@ This repository owns deployment concerns only. Backend and frontend directories
 ## Operational baseline
 
 - Everything runs through Docker, Docker Compose, Bash scripts, and environment files/templates.
+- The CSV-to-PostgreSQL workflow is a one-time administrative bootstrap/recovery command, never a scheduled ingestion service. ZarinPal owns future production payment writes.
 - Nginx is the only public entry point. PostgreSQL and internal services are not internet-exposed.
 - Health checks distinguish liveness from readiness.
 - Backups are encrypted where supported, validated, retention-aware, and paired with rehearsed restores.
 - Restore operations must validate the exact destination and require an explicit production confirmation guard.
 - CI/CD deploys immutable revisions, runs pre/post-deploy checks, and has a documented rollback.
-
diff --git a/CAPABILITY-MAP.md b/CAPABILITY-MAP.md
index d2ed1a3..181bb9a 100644
--- a/CAPABILITY-MAP.md
+++ b/CAPABILITY-MAP.md
@@ -13,7 +13,7 @@ The hackathon demo will seed one account per merchant. Where merchant profile fi
 
 | Order | Capability | Responsibility | Depends on | MVP |
 |---:|---|---|---|:---:|
-| 1 | Data foundation | PostgreSQL model, ingestion, provenance, validation, quality reporting, synthetic merchant profiles | — | Yes |
+| 1 | Data foundation | PostgreSQL model, one-time CSV bootstrap, provenance, validation, quality reporting, synthetic merchant profiles; future source writes are owned by ZarinPal | — | Yes |
 | 2 | Identity and access | Merchant credentials, sessions, tenant isolation, demo account seeding | Data foundation | Yes |
 | 3 | Analytics engine | Deterministic metrics, cohorts, trends, diagnostic drill-downs, traceability | Data foundation | Yes |
 | 4 | Merchant API | Stable authenticated interfaces for dashboard data and analytics | Identity and access, analytics engine | Yes |
@@ -52,4 +52,3 @@ Build sequence: data foundation → identity and analytics → API → dashboard
 ## Required capability specs
 
 Each capability spec must define objective, scope/non-scope, actors, functional requirements, data/API contracts, security and privacy requirements, failure behavior, observability, tests, acceptance criteria, migration/rollback considerations, and unresolved decisions. A capability may enter implementation only after its spec status is marked **Approved**.
-