Ateva

Privacy-first beta for independently verifiable AI wait time and developer attention.

The beta validates wait-state detection without awarding rewards. Settlement stays fail-closed until an independently verifiable attestation integration is deployed and reviewed; advertisers are not billed for beta waits.

Architecture

This monorepo (pnpm workspaces + Turborepo) contains:

Package	Description
apps/api	NestJS REST API — auth, campaigns, ledger, payouts, fraud detection, extensions
apps/web	Next.js frontend — developer, advertiser, and admin dashboards
apps/cli	CLI tool — register device, report wait states, check earnings
apps/vscode-extension	VS Code extension — detects wait states, displays sponsored ads
packages/shared	Shared types, Zod contracts, HMAC signing, constants
packages/config	Zod-validated environment schema shared by all apps
packages/db	Prisma schema, migrations, and client re-exports
packages/ui	Shared UI components
packages/eslint-config	Shared ESLint flat config

Quickstart

# Install dependencies
pnpm install --frozen-lockfile

# Generate Prisma client
pnpm --filter @ateva/db generate

# Start database and Redis-backed local rate limiting
docker compose up -d postgres redis

# Start API dev server
pnpm --filter ateva-api dev

# Start web dev server (in another terminal)
pnpm --filter ateva-web dev

The API serves interactive OpenAPI docs at /api/v1/docs (spec: /api/v1/docs-json) once the API is running.

Make targets

A Makefile wraps common workflows: make dev, make build, make typecheck, make lint, make test, make db-migrate, make db-studio. Run make help.

Quality Gates

pnpm run typecheck   # all workspace packages (config, ui, shared, db, api, cli, vscode, web)
pnpm run lint        # ESLint across all workspaces (style warnings allowed)
pnpm run build        # all workspace packages via Turborepo
pnpm run test        # full suite (API unit/contract/e2e-http + CLI + web + VS Code)
                      # DB-backed API specs require DATABASE_URL + JWT_SECRET (>=32 chars)
pnpm audit --prod    # production dependency vulnerability audit

Note: Tests that touch the database require Postgres and Redis running locally. Start them with docker compose up -d postgres redis and ensure DATABASE_URL, JWT_SECRET (≥32 chars), and other required env vars are set via .env or the shell. See Environment Reference for the full list.

Private beta wait telemetry

Use ateva run -- <AI command> [arguments...] to let the CLI supervise a real local AI-tool process lifecycle, for example ateva run -- claude --version. It sends only a normalized tool type and lifecycle timing—never the command arguments, prompt, or command output.

This is pilot telemetry, not settlement proof. The current device-held signing key cannot independently prove an unmodified client observed a wait, so these events remain non-billable and rewards are disabled until an independently attestable integration is deployed and reviewed.

Core Features

• Auth: Email/password signup, Google OAuth, JWT refresh rotation + reuse detection, password reset, TOTP 2FA with encrypted secrets
• Campaigns: Draft → submitted → approved → active lifecycle with budget/bid validation
• Ledger: Three-ledger accounting (earnings, advertiser, platform) with 60/30/10 revenue split
• Payouts: Multi-provider architecture with PayPal Payouts, Stripe Connect, and Wise wired, Razorpay/Payoneer/Dodo stubs fail-closed in production, hold periods by trust level, optional 2FA gating
• Fraud: Redis-backed rate limits, brute-force lockouts, CTR analysis, self-click detection, trust scoring, automatic earning holds
• Extensions: HMAC-signed event pipeline per device, privacy-enforced, idempotent, with password/Google/support device-secret recovery
• Referrals: Code-based referral system with $5 reward on first payout
• Compliance: Consent ledger, data-retention cron, and admin/user erasure paths that revoke sessions and API keys
• API Keys: Machine-to-machine auth with scoped, expirable keys

Runtime state of the money features

The features above are implemented and tested, not switched on. Every money path is behind a runtime setting that fails closed when its row is absent, so a fresh database starts fully disabled (runtime-config.service.ts):

Switch	Default	Gates
ads.global	off	serving any ad at all
wait.earnings	off	settlement; also requires an external attestation issuer
deposits.global	off	advertiser funding
payouts.requests	off	developer payout requests
payouts.auto	off	automated payout processing

Only an admin/super_admin can flip them. Payout rails: paypal_email and manual are available (both admin-processed by hand); PayPal Payouts, Stripe Connect and Wise are complete but credential-gated; Payoneer, Razorpay and Dodo Payments are stubs that are refused at registration.

This is the beginning of the README. Read the rest at the original. Read the full README ↗