Team

7 humans with one shared engine. Every machine gets the full config; identity is one login (<name>@databayt.org) that works across the CRM workspaces and Slack.

Team Members

Abdout — Founder & Tech Lead

Visionary. Engineering everything: architecture, full-stack, deployment, the kun engine itself.

Ibrahim — Senior Fullstack & Mobile Engineer

Highly skilled fullstack web and mobile engineer. Ships product features across the stack and owns the mobile lane (ios-app + android-app). Code review, architecture sparring, complex end-to-end work alongside Abdout.

Moutaz — Product Engineer (business + sales + AI + network)

Experienced software engineer with strong business, sales, AI, and network skills. Turns ideas into shippable specs, runs customer-facing motion, owns the Albayan pilot, and tightens the engineer ↔ business loop.

Ali Aseel — QA + Sales

MBA + CS, educated at a tech hub (India's current tech scene) — strong in business. Tests features (reports issues on GitHub), manages sales@databayt.org. Outreach for schools, sponsors, investors, early adopters, leads, clients, contributors. Login: aseel@databayt.org.

Moed — Business Development + Copywriting

Well educated and loves to read. Good in business, sales, copywriting, and networking — the words-and-relationships lane of the business team.

Samia — R&D

The most talented and gifted on the team — well-read: languages, voice-over, copywriting, brainstorming, argument (she steelmans the debates). Research on Claude/Anthropic products, sharing economy models, revenue distribution. Core vision contributor.

Sedon — DevOps & Facilitator

Reality-driven — practical thinking grounded in reality, very smart, brings a different perspective. Owns the DevOps lane (deploys, infra cadence, environment upkeep), facilitates the business team, clears blockers. Saudi operations: bank account, physical presence, payments.

One Login Everywhere

Each member has one identity — <name>@databayt.org — that works on every workspace:

Logins: abdout, aseel, sedon, moutaz, ibrahim, samia, moed.

Config — Universal

Every machine gets the full config: all agents, all skills, the full MCP fleet, all hooks (live counts: .claude/engine.json). The machine — not the person — is the unit of capability, so any machine can run any task. Role is a label + a secrets-trust tier; it does not limit what the computer can do.

What still varies: which API keys a machine holds, scoped by the Gist that person is handed. An MCP server without its key just doesn't connect (harmless).

Setup

One command — installs or updates the full config + runs a health check. The role arg is just a label:

Copy# macOS/Linux
cd ~/kun && bash .claude/scripts/setup.sh engineer
 
# Windows (PowerShell)
cd ~/kun; .\.claude\scripts\setup.ps1 -Role engineer

Re-run anytime to update config after pulling latest from git. Fresh machine? Start from Onboarding instead — one paste does everything.

Daily Workflows

Abdout — Builder

> "dev"                    # Start dev server
> [build features]         # Full agent fleet
> "build"                  # Validate
> "push"                   # Commit + push
> "deploy"                 # Ship to Vercel

Ibrahim — Fullstack & Mobile

> "dev"                    # Start dev server
> [build features]         # Full agent fleet, web + mobile
> Code review on changes   # Architecture + correctness pass
> "build"                  # Validate
> "push"                   # Commit + push

Moutaz — Product Engineer

> Translate ideas → specs (issue + acceptance criteria)
> Albayan pilot ownership  # Walkthroughs, feedback loop
> Customer interviews / feedback synthesis
> Shape the engineer ↔ business handoff

Ali Aseel — QA + Sales

QA:
> Test features from URL checklists on GitHub Issues
> Report bugs as comments (not WhatsApp)
> Re-verify fixes, check off boxes

Sales (sales@databayt.org):
> Outreach: schools, sponsors, investors, early adopters, contributors
> Track pipeline in the CRM (hogwarts workspace)

Moed — Business Development

> Copywriting              # Proposals, outreach copy, product messaging
> Network building         # Partners, communities, leads
> Partner with Aseel on outbound

Samia — R&D

Cowork:
> Research Claude/Anthropic products
> Study sharing economy models
> Voice-over + Arabic content
> Contribute to core vision

Sedon — DevOps & Facilitator

> DevOps lane              # Deploys, infra cadence, environment upkeep
> Facilitate business team # Unblock Aseel + Moutaz + Moed
> Reality-check plans      # The different perspective
> Saudi operations         # Bank, payments, physical presence
> Batch weekly             # Monday map, Friday delivery

Config Health Monitoring

Each team member's config is verified continuously. Results report to a shared GitHub issue.

Copy# Check local health
bash ~/.claude/scripts/health.sh
 
# Check + report to GitHub
bash ~/.claude/scripts/health.sh --report
 
# Windows
.\.claude\scripts\health.ps1
.\.claude\scripts\health.ps1 -Report

Or use the /health command inside Claude Code:

• /health — local check + team dashboard from GitHub
• /health report — post local health to GitHub
• /health all — show all team members' latest status

Checks: core files exist, JSON valid, engine counts match engine.json, permissions correct, CLI + agent fleet installed, config staleness.