Program execution

Workstreams

Stable workstream records replace the former initiative cards: objective, explicit owner, repository lane, dependency kind, evidence gate, state, and next safe action.

Wave matrix

Workstream 01Seal the seamsComplete Workstream 02CI meshAt risk Workstream 03Deploy-readyAt risk Workstream 04Observe everywhereAt risk Workstream 05Frauthy protects FrauthyComplete Workstream 06Cuitty adopts FrauthyNot started Workstream 07TUI & status siteIn progress

Workstream ledger

Filter workstreams

Program state

7 workstreams

Workstream 01

Seal the seams

Complete

Real auth, real persistence, real verification, real streams — no stub left on a product path. The admin portal and marketplace currently ship with no authentication at all.

Owners: Program orchestrator
Repositories: market, admin, cloud, protocol
Evidence: 8/2

Next safe actionMaintain evidence freshness

Workstream 02

CI mesh

At risk

Every repo's CI runs green without org secrets; token-gated live jobs skip green; devops aggregates all repos; coverage floors everywhere. Today the sandbox CI is a silent no-op and devops' reusable workflows have zero callers.

Owners: Program orchestrator
Repositories: protocol, sdk, cloud, market, admin, site, infrastructure, devops, sandbox, brand, root
Evidence: 8/2

Next safe actionNo cross-repo dispatch wiring — orchestrate.yml never triggered

Workstream 03

Deploy-ready

At risk

Dockerfiles, dispatch-gated deploy workflows, a Terraform target that provisions real resources, secrets plumbing — one human decision away from hosted. Nothing is deployed anywhere today.

Owners: Program orchestrator
Repositories: cloud, infrastructure, market, admin, site, devops
Evidence: 8/2

Next safe actionNo cross-repo dispatch wiring — orchestrate.yml never triggered

Workstream 04

Observe everywhere

At risk

OTLP in all four SDKs and all services, the devops portal turned into a live dashboard, per-hop sandbox assertions — with optional mirroring to Cuitty Observe. Today only the TypeScript SDK and the protocol crates emit traces.

Owners: Program orchestrator
Repositories: sdk, market, admin, cloud, devops, sandbox, infrastructure
Evidence: 8/2

Next safe actionNo cross-repo dispatch wiring — orchestrate.yml never triggered

Workstream 05

Frauthy protects Frauthy

Complete

market and admin authenticate their own surfaces through @frauthy/sdk-ts sessions — the product enforcing access to the product.

Owners: Program orchestrator
Repositories: market, admin, sdk
Evidence: 8/2

Next safe actionMaintain evidence freshness

Workstream 06

Cuitty adopts Frauthy

Not started

Cuitty's auth service (BetterAuth-based) adopts Frauthy as its abstraction layer — the flagship external dogfood. Prerequisite landing here: protocol's BetterAuth provider adapter (PROTO-8). The cuitty-side work happens in that workspace.

Owners: Program orchestrator
Repositories: protocol, root
Evidence: 8/2

Next safe action`frauthy tui` live dashboard unbuilt (spec 05 B.4 headline; cui-modeled)

Workstream 07

TUI & status site

In progress

The `frauthy tui` live dashboard plus up/down/logs presets (modeled on ~/Code/cuitty/cui), and this versioned status site with its markdown ingestion pipeline.

Owners: Program orchestrator
Repositories: root, research
Evidence: 8/2

Next safe action`frauthy tui` live dashboard unbuilt (spec 05 B.4 headline; cui-modeled)