Can I vibe code Commanders Act?

Build a hybrid Tag Management System and Server-Side Event Processing Engine in Node.js, TypeScript, and React.

Data Model:
1. Workspace: { id, name, domain, created_at }
2. EventSchema: { id, workspace_id, event_name, payload_schema_json }
3. ConsentProfile: { id, user_id, consent_given: boolean, categories: string[], tcf_string: string, updated_at }
4. TagRule: { id, workspace_id, trigger_event, destination_type: 'client' | 'server', endpoint_url, headers_json, payload_template_json }
5. EventLog: { id, workspace_id, event_name, consent_status, payload, delivery_status, attempts, response_code, created_at }

Core API & Pipeline Requirements:
1. Ingestion Endpoint (`POST /v1/event`): Accept JSON payloads containing `event_name`, `user_id`, `anonymous_id`, `context` (user-agent, ip, url), and `consent_string`.
2. Consent Engine: Parse IAB TCF v2.2 strings and Google Consent Mode v2 flags. Drop or suppress event fields matching non-consented categories (e.g., 'ad_storage', 'analytics_storage') prior to payload transformation.
3. Edge Tag Loader Script (`/sdk.js`): Generate an optimized client-side JS snippet that intercepts window.dataLayer events, evaluates local consent state, and sends payloads to the server-side ingestion endpoint via fetch/beacon.
4. Server-Side Routing Pipeline: Queue incoming valid events using BullMQ and Redis. Worker nodes evaluate TagRules, substitute dynamic tokens in `payload_template_json` (e.g. `{{user.id}}`, `{{context.ip}}`), and dispatch HTTP POST requests to third-party endpoints (e.g., Meta CAPI, Google Measurement Protocol).
5. Identity Stitching: Update a Redis key mapping `anonymous_id` to `user_id` upon receiving explicit login events, merging past unauthenticated event streams into a unified profile record.

Dashboard (React + Tailwind):
1. Tag & Trigger Configurator: Interface to create rules linking event names to webhooks with custom JSON payloads.
2. Consent Governance Panel: Visual toggles to test how events get redacted under different TCF consent configurations.
3. Real-Time Stream Inspector: Live WebSocket feed displaying incoming raw events alongside outgoing server-side API dispatch logs and HTTP response statuses.

Out of Scope:
- Native mobile SDKs (iOS/Android)
- Dynamic drag-and-drop web crawler tag discovery
- Automated visual element selectors for auto-tagging
- Direct integration with enterprise offline CRMs beyond HTTP webhooks

Failure Handling:
Implement exponential backoff retries (3 attempts max) for failed destination webhooks with a Dead Letter Queue (DLQ) exposed in the dashboard. Ensure IP address masking and PII stripping execute synchronously before Redis queuing.

$ each button prefixes agent-specific run instructions · build your own product, never copy proprietary code, trademarks or designs