Aleph Product Spec

Status: Private beta. Public launch Q3 2026. Owners: Rabih Naja (Founder & Chief Builder), Wassim Moumneh (Co-Founder & Chief Orchestrator) Last updated: 2026-04-23

---

1. What Aleph is

Aleph is the build engine, runtime substrate, tool registry, and document factory. It executes the pipeline that turns a brief into a deployed application and a full bundle of business-setup deliverables, under Shakeeb's orchestration.

Aleph is a sub-brand of Gnesis. It has a first-class dashboard. Users see Aleph whenever they look at how a build is going, what the runtime looks like, what tools are installed, or how the bundle is being produced.

Inside Aleph, the core build engine handles the code track; the Aleph Assembly Line sub-engine handles the bundle track (30+ business-setup documents). Same gate discipline, same audit log, same eject path. Two surfaces of one factory.

2. What Aleph is not

• Not a CI/CD service. Aleph owns the whole path from brief to running app, not just a pipeline stage.
• Not a scaffolding tool. Aleph keeps running after scaffold. Build, test, deploy, and operate all route through it.
• Not a DIY agent framework. Aleph is the opinionated engine that makes Shakeeb useful.
• Not user-facing as a product. Users interact with Shakeeb; Aleph runs underneath and shows its state in a dashboard.

3. The four roles

Aleph plays four roles in one system:

1. Build engine. Takes a brief and emits a deployed multi-tenant application. Every mutation is a git commit. Every commit runs gates. Every pass leads to a preview or a prod deploy.
2. Assembly Line. Takes the same brief and emits the 30+ business-setup documents across marketing, legal, compliance, finance, content, ops, sales. Every deliverable is a versioned artifact. Every generation records inputs, prompt envelope, and pipeline state. Every deliverable passes the Assembly Line acceptance gates before release (see Generated-Business-Standard §5).
3. Runtime substrate. The generated application runs on infrastructure Aleph provisions and operates. Observability, secrets, storage, compute, and scale live here.
4. Tool registry. The catalog of capabilities available to Shakeeb and to generated apps. Each tool is a declarative spec plus an implementation. The Assembly Line has its own tool sub-registry for document-production tools (voice-guide extractor, jurisdictional annotator, financial-model builder).

One engine, one dashboard, four roles.

4. The 7-stage pipeline

Aleph executes seven stages per project. Shakeeb orchestrates; Aleph acts.

1. Brief. Aleph stores and versions the brief produced by Shakeeb.
2. Plan. Aleph drafts architecture and data model proposals. Shakeeb walks the user through trade-offs.
3. Scaffold. Aleph generates the base repo from the opinionated stack.
4. Build. Aleph writes feature code. Every change is a commit. Every commit carries a Shakeeb decision record.
5. Test. Aleph auto-generates unit and e2e tests from the brief. The 17 Aleph gates and 6 CI gates run. Shakeeb self-reviews.
6. Deploy. Staging preview, user signoff on diff plus Shakeeb recommendation, production deploy.
7. Operate. Ambient monitoring. Cost, error, and usage anomaly surfacing. Change requests loop back to Build. Bundle delivery runs on a parallel cadence during this stage: legal pack day 3, finance pack day 5, marketing + content pack day 8, compliance pack day 10, ops + sales pack day 12, bundle closeout day 14. See Generated-Business-Standard §4.

The 72-hour end-to-end SLA runs from brief signoff for the code track. The bundle SLA runs on the 7-to-14-day cadence. No per-stage SLAs at launch on either track.

5. Gates

Every build passes through two stacks.

5.1 The 17 Aleph gates

Applied before code reaches CI. Representative classes (not an exhaustive list in this doc):

• Schema integrity (Drizzle migrations valid, no orphan foreign keys).
• Tenant scoping (every new table has tenant_id, every new query respects RLS).
• Secret hygiene (no literal secrets, no env reads outside approved config).
• i18n completeness (every new string has EN, AR, ES keys).
• a11y floor (WCAG 2.2 AA check on new UI).
• Auth coverage (every new route has an auth check or an explicit public declaration).
• Observability hooks (Sentry, PostHog, OpenTelemetry wired on new flows).
• Billing hook (every new usage-metered surface emits a meter event).
• Capability class (every new tool call declares its class).
• Rollback path (every write has a documented rollback).

The full list lives in Gnesis-Build-Engine.

5.2 The 6 CI gates

Standard CI on the generated repo.

1. Lint.
2. Typecheck.
3. Unit tests.
4. Integration tests.
5. E2E (Playwright).
6. Build artifact (Next.js build, Drizzle generate, bundle analyzer).

Target gate-pass rate first try: above 70 percent by Q3 2026.

5.3 The 8 Assembly Line gates

Applied to every business-setup deliverable before release (see Generated-Business-Standard §5 for the full spec).

1. Brief fidelity.
2. Voice conformance (customer brand voice guide or neutral default).
3. AI-pattern filter (no em dashes, no filler, specific nouns).
4. Jurisdictional annotation for region-dependent content.
5. Legal-review flag on every legal, compliance, or finance doc.
6. Consistency cross-check against sibling bundle documents.
7. Format integrity (Word opens clean, markdown renders, formulas evaluate).
8. Rebuild recipe included.

Target Assembly Line gate-pass rate first try: above 80 percent by Q3 2026.

6. Tool registry

Tools are declarative. Each tool ships:

• A name.
• A capability class (read, write, destructive).
• An input schema.
• An output schema.
• An implementation (code).
• A default posture override (optional).
• An owner and a version.

Tools are loaded per project at brief signoff. Custom tools can be installed by the tenant. Marketplace rollout is post-launch.

See Tool-Registry for the full schema and lifecycle.

7. Runtime substrate

7.1 Default stack

• Next.js 16 + React 19.
• tRPC v11.
• Drizzle with Drizzle Kit migrations, 23-migration numbered baseline.
• Per-tenant Postgres orchestrated by Coolify (default of record for Team and Business).
• Coolify for container orchestration and per-service deploy; GHCR for image registry.
• BullMQ on Redis for background jobs (retry plus dead-letter).
• MinIO for object storage in the default stack; S3/R2 supported via Tool Registry.
• next-intl for i18n with EN, AR, ES and RTL support.
• Better Auth for identity (MFA, magic link, OAuth, API keys, sessions, SAML/SCIM).
• Stripe for billing (cent-exact metering).
• OpenRouter as the AI routing layer; Anthropic primary, OpenAI plus Google as failover targets.
• Sentry plus PostHog plus OpenTelemetry plus the Gnesis telemetry dashboard for observability.

The stack is an opinionated default. Deviations are possible but tracked.

7.2 Isolation modes

Three modes, tier-defaulted, always overridable.

• Shared-schema RLS. Single Postgres, tenant_id on every row, RLS enforced. Default on Starter and Education cohort mode.
• Per-tenant Postgres on Coolify. Dedicated database per tenant with physical isolation. Default of record on Team and Business.
• VPC-Vault. Customer-owned cloud. Control plane orchestrates; data plane lives in the customer AWS, GCP, or Azure account. Default on Enterprise.

No hard gate on any mode. Downgrade and upgrade paths are both documented.

7.3 Secrets

Gnesis vault stores secret material. The vault UI is the authoring surface. Secrets sync to Coolify per-environment secrets (local, staging, production). Rotation rotates both.

7.4 Observability

Four layers:

1. Sentry for errors.
2. PostHog for product analytics.
3. OpenTelemetry traces and metrics.
4. Gnesis-hosted telemetry dashboard that rolls all three up per project.

8. Dashboard

The Aleph dashboard is user-facing. It is the only Aleph surface most users ever open.

8.1 Home

A grid of projects. Each card shows name, current stage, last build status, and last deploy.

8.2 Project page

Two primary elements.

1. Pipeline lane view. Seven lanes, one per stage. Current stage highlighted. Events flow under each lane.
2. Active build timeline. The most recent build expanded, phases horizontal (generating, testing, gating, deploying).

Drill-downs: file tree plus diff viewer per build. Decisions inbox accessible via project nav.

8.3 Live activity feed

Right rail. Commits, gate results, deploys, ambient events, tool calls, Assembly Line generations and gate results. Filterable.

8.4 Bundle lane

Separate lane under the project page. Shows all 33 bundle deliverables with status: not-yet-run, generating, ready-for-review, delivered. Clicking a deliverable opens the document viewer plus the audit record plus the rebuild recipe. See Surfaces-Spec §5 and §14.

9. APIs

9.1 Aleph API

Programmatic access to build, deploy, rollback, tool install, and audit log. Used by Shakeeb, by Gnesis CLI, and by Enterprise customers who want to drive Aleph from their own systems.

9.2 Aleph CLI

Thin wrapper around the API. Primary audience: developers who eject and keep using Aleph-compatible tooling locally.

10. Migrations

• Authoring: Drizzle Kit generates from schema changes.
• Review: Shakeeb attaches a risk note per migration (destructive, reversible, zero-downtime).
• Approval: human approval required before apply on production.
• Apply: Aleph runs the migration inside a transaction where possible; otherwise online-migration pattern with dual-write.

11. Rollback

• Commit-level rollback via git revert plus redeploy.
• Schema rollback via recorded Drizzle down-migration plus reconciliation note.
• Config and secret rollback from the audit log.

Rollback is always a first-class path. If a change has no rollback, it is classified destructive.

12. Failover

• Model failover chain (Anthropic, OpenAI, Google) is triggered only by provider outage or 5xx.
• Provider health checks run continuously; chain switch is automatic and logged.
• Voice degrade to text runs through the same health check.

13. Metrics (internal)

• Build-engine gate-pass rate first try: target above 70 percent by Q3 2026.
• Assembly Line gate-pass rate first try: target above 80 percent by Q3 2026.
• Mean time to first deploy (TTFD): target under 60 minutes.
• Mean time to full bundle (TTFB): target 10 days at launch, 7 days by end of 2026.
• Aleph p95 build duration: tracked, not public.
• Assembly Line p95 deliverable generation time: tracked, not public.
• Model-token cost per project per day: tracked, used for billing and anomaly detection (both tracks combined).

14. Open questions

Tracked in the Open-Questions-Ledger. Current top-of-stack items:

• Marketplace governance for third-party tools.
• Aleph API public surface scope at GA.
• Per-tenant Postgres tenancy limits before splitting clusters.
• VPC-Vault template footprint per cloud.

---

Related docs: Gnesis-Product-Spec, Shakeeb-Product-Spec, Gnesis-Build-Engine, Generated-App-Standard, Tool-Registry, Observability-Spec, Data-Model, Tenant-Model.