Woopra

Build me a focused customer journey analytics workflow for the personal core of Woopra. Requirements:

- Use exactly this stack: Next.js 15 + TypeScript + ClickHouse + PostgreSQL. Model data sources, dated observations, derived metrics, and report snapshots; keep stable source IDs and timestamps.
- Paid product context: Customer profiles, journey reports, retention, triggers, and integrations. Build only this DIY scope: Build a narrow customer journey analytics collector for one site or app, ingest first-party events, and show a small set of decision-ready reports.
- For customer journey analytics, define the event schema and a permitted first-party source.
- Ingest events with stable IDs, aggregate the requested metric, and retain raw rows for audit.
- Show a dated report with filters and CSV export.
- Use a local web page with input, progress, review, and export views. Required input or access: deploy target; ClickHouse or SQLite for low volume.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A replayed batch cannot double-count events; missing or late data must be labelled in the report.
- Out of scope: high-volume ingestion and retention; bot and identity resolution. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

# AGENTS.md — Build guide for Woopra

## Project scope
Build a narrow customer journey analytics collector for one site or app, ingest first-party events, and show a small set of decision-ready reports.

Catalogue verdict: no. Do not mistake the interface for the product. Woopra's durable value is ingestion, storage, reliability, which a solo one-shot build cannot reproduce responsibly. The prompt therefore builds only the closest honest personal consolation tool.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- deploy target
- ClickHouse or SQLite for low volume
- first-party tracking script
- Explicit README warning that this is a consolation build, not a production replacement

## Stack and architecture
- Use exactly this stack: Next.js 15 + TypeScript + ClickHouse + PostgreSQL.
- Model data sources, dated observations, derived metrics, and report snapshots; keep stable source IDs and timestamps.
- Interface for this customer journey analytics workflow: a local web page with input, progress, review, and export views.

## Security and data integrity
- A replayed batch cannot double-count events; missing or late data must be labelled in the report.
- Validate imported records and file paths; keep user data within the storage location named in the prompt.
- State the practical limit: high-volume ingestion and retention.

## Agent implementation rules
- Project rule, data: Model data sources, dated observations, derived metrics, and report snapshots; keep stable source IDs and timestamps.
- Project rule, behavior: For customer journey analytics, define the event schema and a permitted first-party source.
- Project rule, recovery: A replayed batch cannot double-count events; missing or late data must be labelled in the report.

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this customer journey analytics operation with sample or user-owned data: For customer journey analytics, define the event schema and a permitted first-party source.
- Show a concrete result or export: Show a dated report with filters and CSV export.
- State the practical limit: high-volume ingestion and retention.

## Engineering roadmap
1. Phase 1, architecture and data: Use exactly this stack: Next.js 15 + TypeScript + ClickHouse + PostgreSQL. Model data sources, dated observations, derived metrics, and report snapshots; keep stable source IDs and timestamps.
2. Phase 2, implement: For customer journey analytics, define the event schema and a permitted first-party source.
3. Phase 3, implement: Ingest events with stable IDs, aggregate the requested metric, and retain raw rows for audit.
4. Phase 4, review and output: Show a dated report with filters and CSV export.
5. Phase 5, recovery and acceptance: Verify this invariant with a saved fixture: A replayed batch cannot double-count events; missing or late data must be labelled in the report. State the practical limit: high-volume ingestion and retention.

## Paid-product capabilities outside this build
- high-volume ingestion and retention
- bot and identity resolution
- session replay privacy tooling
- enterprise governance and integrations

## Implementation prompt
Build me a focused customer journey analytics workflow for the personal core of Woopra. Requirements:

- Use exactly this stack: Next.js 15 + TypeScript + ClickHouse + PostgreSQL. Model data sources, dated observations, derived metrics, and report snapshots; keep stable source IDs and timestamps.
- Paid product context: Customer profiles, journey reports, retention, triggers, and integrations. Build only this DIY scope: Build a narrow customer journey analytics collector for one site or app, ingest first-party events, and show a small set of decision-ready reports.
- For customer journey analytics, define the event schema and a permitted first-party source.
- Ingest events with stable IDs, aggregate the requested metric, and retain raw rows for audit.
- Show a dated report with filters and CSV export.
- Use a local web page with input, progress, review, and export views. Required input or access: deploy target; ClickHouse or SQLite for low volume.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A replayed batch cannot double-count events; missing or late data must be labelled in the report.
- Out of scope: high-volume ingestion and retention; bot and identity resolution. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.