Reference¶
Canonical lookups — the "what does field X look like" docs.
Available¶
| Doc | What it covers |
|---|---|
| Prisma models | Every field in every Prisma model — types, defaults, constraints, indexes |
| Environment variables | Every process.env.* the codebase reads, with defaults and where used |
| Tech stack | Per-layer inventory of dependencies, runtimes, and tools — versions, lockdown, gaps, risks |
| Competitive landscape | Global aggregator/builder competitor analysis + Lebanese surface; drives positioning for #28/#32/#41 |
| Personas | Lebanese buyer archetypes and behavior |
| Lebanese retailer audit | Per-retailer reference for 16 Lebanese tech retailers — 7 currently-scraped, 1 H-tier deferred (Cloudflare), 1 M, 3 L, 2 deferred for access blockers, 2 skipped — plus the scraper roadmap |
| Brand identity (DRAFT) | Voice, tone, microcopy patterns, forbidden phrases, worked examples — initial draft for the design partner to react to (#42) |
| Categories | Per-category profile for every product category 961tech indexes (or has decided not to index) — scope, key spec dimensions, retailer coverage, persona anchors, milestone target. Pairs with ADR-0010 |
| Legal + compliance baseline | Per-surface (affiliate / consumer / privacy) findings on what Lebanese law requires of 961tech as an affiliate-monetised aggregator at launch — gap vs EU/US norms, recommended baseline, and the explicit "needs lawyer review" register |
| Security baseline | Concrete security controls list with tier (M1/M2/M3) and owner (us / Cloudflare / Auth.js / Postgres / etc.); cross-linked to the threat model and RFC-0006 |
| KPIs | North-star + secondary + health metrics, ordered by tier; per-metric source, target, cadence; M1 vs M2 measurement set |
| Performance budget | Per-surface (frontend Core Web Vitals, bundle weight, backend query latency, scraper run-time, monthly cost) numeric targets anchored in Lebanese-mobile reality |
| Monetisation | Per-revenue-stream profile (CPS, CPC, hybrid, featured placement, B2B/SMB tier, data products) with peer-rate citations and Lebanese unit-economics estimates — supports RFC-0008 |
| AI discoverability | Per-surface reference (robots.txt for AI crawlers, llms.txt, schema.org / JSON-LD, OpenGraph, page-content shape, machine-readable feeds) for making 961tech citable by ChatGPT / Claude / Perplexity / Google AI Overviews / Apple Intelligence; drives RFC-0009 |
To write next¶
api-internal.md— internal API endpoints (currently just/api/go/r/[retailerId]/p/[listingId])s2s-postback.md— affiliate postback contract once defined in #17scraper-fixtures.md— convention for retailer HTML fixtures used in tests
What goes here¶
- API endpoints (request/response shapes, error codes)
- Database / Prisma model field definitions
- Environment variables
- Third-party contracts (S2S postback, retailer feed formats)
- Configuration knobs (
mkdocs.yml,next.config.ts, etc.)
What does NOT go here¶
- Why a model is shaped that way → ADR
- How the system uses these models → Architecture
- How to operate against these → Runbook