Current System

Purpose

Cape Town Market FAAS currently runs as a queue-driven finance platform with:

This document describes what is live now.

The landing page is the operator entrypoint.

Portal cards are declared in apps/portal-web/src/landing-model.ts.
Cards are rendered through the shared card builder in apps/portal-web/src/landing-card-builders.ts.
Card session/login/runtime behavior is bound in apps/portal-web/src/landing-card-runtime.ts.
Queue-backed portal login is active for statistics, debtors, cashier_client, creditors, and icapv.
admin is still a control-plane card without portal login.

Active workspaces run only on alpha3.

apps/portal-web/src/workspace-versions.ts normalizes retired alpha0, alpha1, and alpha2 inputs onto alpha3.
Workspace routes such as stats.ts, cashier.ts, admin.ts, and debtors.ts bootstrap the alpha3 route directly.
The live shell is owned by apps/portal-web/src/lanes/alpha3.

The alpha3 shell is the real workspace runtime, not a wrapper over a live legacy host.

manifest.ts defines app manifests and workspace revision labels.
host.ts owns bootstrap, browser title, edition context, and inspector binding.
base-template.ts owns the shared workspace hero, mode toggle, inspector toggle, and shell header structure.

The active backend is split across four main services:

These services run as the current operational topology described in Service Topology.

The project is currently oriented around:

This tree documents the current system only.

Historical notes, superseded plans, and older architecture narratives were moved to:

S:\development\CTM\documentation-archive\capetownmarket-faas\2026-03-29-doc-reset