Seed Infrastructure

The make seed-full command populates the entire Ngwenya platform with realistic, production-representative test data using a 22-archetype approach. Every user archetype represents a specific permission/tier/role combination to maximize coverage of platform capabilities.

Quick Start

# Prerequisites: infrastructure containers must be running
make infra-up

# Full platform seed — all 22 archetypes, orgs, verticals, social, commerce, enterprise
make seed-full

# Individual phases (can run independently)
make seed-users        # Auth users → Postgres (21 users + guest token)
make seed-profiles     # User profiles → nodes MongoDB
make seed-verticals    # Orgs + all 11 malets
make seed-blogs        # Blog posts for all malets

# Clean everything and start fresh
make seed-clean && make seed-full

Environment Variables

Seed Architecture

Two-Plane Approach

The seed system mirrors the platform's architectural split:

Phase Execution Order

Phase 1: Auth users (Postgres)         → 21 users + 1 guest token + platform admins
Phase 2: User profiles (nodes/MongoDB) → 20 profiles (2 deliberately missing)
Phase 3: Organizations & Teams         → 2 orgs (PRO + ENTERPRISE), teams, memberships
Phase 4: Verticals (seed-all.ts)       → 11 malets, products, services, experiences
Phase 5: Blog Posts                    → ~22 posts across all malets
Phase 6: Social graph                  → 40+ follows, 7 wishlists, 16+ likes
Phase 7: Commerce                     → 8 orders, 4 carts, 8+ reviews
Phase 8: Community                    → 5 discussions, 17+ comments, 3 posts
Phase 9: Enterprise                   → SAML, SCIM, custom roles, SIEM, audit events
Phase 10: Meilisearch Reindex          → Rebuild search indexes (non-fatal if unavailable)

File Structure

scripts/db/verticals/
├── shared/
│   ├── config.ts          # GATEWAY_URL, MONGODB_URI, POSTGRES_URI, TOKEN
│   ├── gql-client.ts      # GraphQL client with user impersonation
│   ├── mongo.ts           # Lazy Mongoose connection factory
│   ├── ids.ts             # oid(), daysAgo(), daysFromNow(), img()
│   └── users.ts           # 22 users, 2 orgs, 11 malet definitions
├── seed-full.ts           # Master orchestrator (all phases)
├── seed-users.ts          # Phase 1: Auth users (Postgres)
├── seed-profiles.ts       # Phase 2: User profiles (MongoDB)
├── seed-orgs.ts           # Phase 3: Organizations + Teams
├── seed-all.ts            # Phase 4: All 11 verticals
├── seed-social.ts         # Phase 6: Follows, wishlists, likes
├── seed-commerce.ts       # Phase 7: Orders, carts, reviews
├── seed-community.ts      # Phase 8: Discussions, comments, posts
├── seed-enterprise.ts     # Phase 9: SAML, SCIM, roles, SIEM
├── clean.ts               # Drops all seed collections
└── seed-{vertical}.ts     # One per vertical (11 total)

User Archetype Matrix

🔶 Solo Operators (Starter Tier — No Org)

These users own a single malet without an organization. They exercise Starter tier limits (1 malet, 3 members max).

🔷 AfriArts Collective (Pro Tier — Teams, 4 Malets)

Exercises org-scoped billing, team-based access, vertical roles, multi-malet management.

Malets: venue-demo, gallery-demo, tour-demo, restaurant-demo Teams: "Events & Culture" (Thabo, Zanele), "Food & Tours" (Naledi, Sipho, Bongani)

🟣 Circuit Board Inc. (Enterprise Tier — SAML/SCIM)

Exercises unlimited malets, SAML SSO, SCIM, SIEM, custom RBAC, 3% commission.

Malets: tech-store-demo, pixel-vault-demo

🟢 Platform Admins (Tower Access)

🟡 Consumers (7 Behavioral Archetypes)

Organization Summary

Tier Capabilities

Activity Coverage Matrix

Social Activity

Commerce Activity

Community Activity

Adding New Seed Users

1. Define the user in shared/users.ts:

export const USER_NEW_ARCHETYPE: SeedUser = {
    id: 'b1a2c3d4-e5f6-7890-abcd-XXYY00000001', // deterministic UUID
    handle: 'new-handle',
    displayName: 'Full Name',
    email: 'name@domain.test',
    description: 'What this user exercises',
};

2. Add to getAllUsers() array
3. Add to seed-profiles.ts bio map (or it gets a default bio)
4. Register in auth — seed-users.ts auto-inserts all getAllUsers() members
5. Add activity in seed-social.ts, seed-commerce.ts, etc. as needed

Idempotency

All scripts are safe to re-run:

• Auth users: ON CONFLICT (id) DO NOTHING for Postgres inserts
• Malet creation: ensureMalet() checks for existing handle first
• Product creation: ensureProduct() checks for existing slug+maletId before creating
• MongoDB inserts: wrapped in try/catch that skips E11000 duplicate key errors
• Deterministic IDs: User UUIDs are hardcoded in shared/users.ts
• Meilisearch reindex: Phase 10 automatically reindexes (non-fatal if Meilisearch is unavailable)

For a completely clean state, run make seed-clean before seeding.

Troubleshooting

Related

• Vertical Seeding Infrastructure — Per-vertical entity details and catalog integration
• Platform Admin Provisioning — Tower access and invite-chain provisioning
• Gateway — GraphQL API and subgraph architecture
• Tower — Admin dashboard and analytics
• Error Tracking — GlitchTip integration for crash reporting
• Custom RBAC — Role-based access control
• SIEM Event Streaming — Security audit event streams
• Teams & Sub-Groups — Organization structure and role-based access
• Wishlists & Collections — Custom lists and social sharing
• Database Backup & Disaster Recovery — Backup scheduling, restore procedures, and storage configuration