ARCHFORGE
← Back to the studio

THE TEAMPeople who decide · seats that argue

A small team. A full bench.

Archforge is deliberately small. The people here hold the decisions and put their names on the architecture. Beneath them sits a bench of thirty-six AI seats, each with one job, one question it is allowed to ask, and a chair it answers to.

Maryam Khallad

Qimam Fellow · Class of 2026

Member 01 · Engineering

Maryam Khallad

Solutions Architect & Founding Backend Engineer

Maryam designs how Archforge's systems are put together before they are built, and owns the backend they run on: the APIs, the data model, the services and the path to production. She is a fourth-year Software Engineering student at Al-Ahliyya Amman University and a working full-stack engineer, shipping customer websites, mobile apps, specialist portals and end-to-end booking flows.

She leads the way she builds: in public, with a team behind her, and with the result on the record.

ASP.NET CoreC#SQL ServerREST APIsDockerCloudReactReact Native
27 / 5,000+

Qimam Fellow, Jordan · Class of 2026

One of 27 selected from more than five thousand applicants to the McKinsey-founded leadership fellowship.

IEEE CS

Chairwoman, Computer Society · AAU

Runs the chapter's workshops, technical sessions and campus booths, with support from IEEE Region 8.

2nd

IMPAKATHON 2026 · CareConnect

Co-built an AI wearable and app that predicts meltdowns in autistic children before they happen.

42

42 Amman · core curriculum

Accepted into the core programme and represented 42 Amman, a Crown Prince Foundation programme, at her university.

NTP 2026

Master of Ceremonies · National Technology Parade

Hosted the 13th parade and served as a supervisor; her IEEE CS team took first place in two tracks.

Full stack

Engineer · EMCare

Customer website, mobile application, backend APIs, specialist portal, admin systems and databases.

THE BENCHVOAC · the orchestration room

Thirty-six seats. One chain of command.

Every project that reaches Archforge is read first by the Chief Architect, who wakes only the seats it actually needs. Five chairs each merge their specialists into one ruling. Thirty specialists each hold a single question, and none of them decides. People do.

Supervisor · the chiefThe Chief ArchitectReads the project and casts the seats it actually needs
Chair · backendThe Backend ChairMerges the backend seats into one ruling and one prompt
API ContractRoute shape, verbs, status codes, versioning, idempotency
Data ModelTables, keys, indexes, migrations, what the schema forbids
Auth and SessionsWho is allowed in, who is allowed what, and how it fails
State and ConsistencyRaces, concurrent writers, transactions, stale writes
IntegrationsThird-party APIs, webhooks, retries, rate limits, timeouts
Background WorkQueues, crons, long jobs, and finishing what was started
Chair · interfaceThe Interface ChairMerges the interface seats into one ruling and one prompt
Interface StructureScreens, routing, and where client state actually lives
InteractionForms, taps, latency, optimistic updates, error surfaces
Mobile and ViewportThe 390px phone as the real device, not the small case
AccessibilitySemantics, keyboard, focus, contrast, screen readers
Client PerformancePayload, render cost, caching, offline, install
Visual SystemTokens, type, hierarchy, and one language across screens
Chair · platformThe Platform ChairMerges the platform seats into one ruling and one prompt
Deploy PathHow code gets to production and how it comes back
Edge RuntimeServerless limits: CPU, wall clock, subrequests, cold start
Storage and CostWhich store, what it costs, and where the bill surprises
ObservabilityLogs, health checks, and knowing it broke before a user does
Networking and DNSDomains, TLS, routes, proxies, tunnels
Secrets and ConfigWhat is a secret, where it lives, how it rotates
Chair · modelsThe Model ChairMerges the AI seats into one ruling and one prompt
Prompt ArchitectureSystem prompts, structure, and output you can rely on
Model RoutingWhich model, what it costs, how slow, and the fallback
Agent OrchestrationHow many agents, in what order, and who reads whom
Retrieval and ContextWhat the model is given, and whether it is grounded
EvaluationHow you know the model output got better or worse
Tool UseFunction calling, tool schemas, sandboxes, blast radius
Chair · assuranceThe Assurance ChairMerges the quality seats into one ruling and one prompt
Test StrategyWhat to test, at what layer, and what to skip
Security ReviewAuthorization holes, injection, exposure, dependencies
Failure ModesWhat breaks first, how it degrades, what the user sees
Data IntegrityValidation at the boundary, and never losing what was written
Performance ProfilingMeasure, find the real hot path, then change one thing
Release ReadinessThe honest checklist between "it works" and "it shipped"
36Seats on the bench
1Chief architect
5Chairs
30Specialists

Why a bench, not a crowd. Thirty wired seats beat a hundred declared ones. A seat is added only when a real gap shows up, and each one answers under the same rules: it has not seen the repository until it is shown, it never states a guess as a fact, and its ruling goes to a chair, not to production.