# Enterprise data and static portal continuation prompt

Status: PREPARED / IMPLEMENTATION_NOT_STARTED. Date: 2026-10-24.
Use only after the maintainer selects construction of a named scope.

Read AGENTS, FAST_EXECUTION, current PROGRESS, DELIVERY_WORKFLOW, the
[ESP roadmap](Roadmap.md#enterprise-data-and-static-public-portal),
[execution plan](docs-planning-ENTERPRISE_DATA_STATIC_PORTAL_PLAN.md) and
[product contract](docs-product-ENTERPRISE_DATA_STATIC_PORTAL_CONTRACT.md).
Then read only the selected task's code/tests and referenced FQ/RST evidence.

Start with ESP-00. Inspect actual local/remote maintained dev/main history and
occupied worktrees; the planning base was local dev 5c9f5204 and its cached remote
ref diverged. Do not infer current synchronization or readiness from this prompt.
Preserve foreign edits, reconcile the local planning patch and use an isolated
worktree when required. No force push, destructive reset or stashing others' work.

Execute one bounded task at a time. Reuse Directory, Official, Quality/FQ,
Rust station-prep and existing Jobs; never create a competing station/quality
ledger. Respect source-specific native clocks, exact full-establishment identity,
historical company context, source statuses and public field allowlists. FQ
acceptance and source activation must be checked against current evidence.

Data-first: ESP-00 → 01 → 02/03 → 04 → 05/06 → 07. Then complete ESP-08–13
for the selected public slices, followed by scoped hosting/automation/performance/
preview/publication ESP-14–18. Slash-separated tasks describe dependencies, not
permission for parallel agents. ESP-08 may be prototyped after 00/01 with labelled
synthetic data; unsupported official sources stay explicitly pending.

Document B-BR-ESP/BUC before behavior; use RED → GREEN → REFACTOR. Critical
SQL/jobs/migrations/auth/privacy/concurrency changes need immediate negative,
failure, real-PostGIS and recovery tests. Record exact acceptance executables at
task opening. Do not substitute compilation, mocks or source code for runtime
evidence; preserve existing tests and fix known failures before dependent work.

Extend the existing static landing stack. Essential pages work without JS;
search downloads only bounded versioned public files. Inspect browser traffic
to prove no Abastevo API, ANP API or third-party search dependency. Pin all data
and identity revisions, verify complete release payloads before switching and
prove correction-safe rollback without exposing private artifacts.

Keep source switches default-off until their actual operational scope is
selected. Do not mutate VPS/shared edge/CDN/DNS, launch live load, publish the
site or procure services from the planning request alone. Prepare reviewable
local configuration/artifacts first and apply the session's actual authorization.
No private business accounts/teams, receipts/NFC-e, paid data delivery, billing,
new numeric risk score, iOS or Stage D implementation is included here.

Treat 16 GB and 5,000 active clients as sizing hypotheses. Freeze hardware,
workload, resource stop limits and metrics before capacity tests. Separate source
freshness, Abastevo publish lag, browser responsiveness and VPS/CDN throughput.

Update concise PROGRESS and scoped evidence per tested checkpoint; commit owned
changes atomically on maintained dev or the permitted isolated delivery path.
No construction PR/CI polling or repeated aggregate suite for record-only edits.
Final authorized protected delivery requires current Quick verification and all
applicable checks; merged wiki publication, website deployment and G09/app release
retain their independent scopes. State PLANNED, LOCAL_DONE, INTEGRATION_PENDING,
INTEGRATED and externally accepted deployment/capacity truthfully.