Generated from cat-harness/processes/ui/web-app-publish.bpmn by gen-processes-viz.ts — do not edit here. All processes · cat-harness processes

Publish a web app — declared, translated, built at its own route

Process_WebAppPublish · strict · 7 step(s)

How any layer publishes an interactive app it holds as source, without becoming a harness. The layer declares a web-app directory; the app’s UI strings go through the harness’s own translation process; the harness’s apps visualiser (Tool web-app-build) checks, builds and publishes it at <locale>/<harness>/apps/<id>/, with no site chrome, loaded only when a reader opens it (skill web-apps).

BPMN diagram: Publish a web app — declared, translated, built at its own route

How it connects

  • Called by: no call activity names this process
  • Calls: Multi-locale translation
  • Presented on: no docs page section shows this diagram
  • Running instances: none recorded

Lanes — who acts

lanerolewhat it does here
App authorauthorThe person or agent who holds the app’s source in a content layer. They declare it; they never write a publish script for it.
CI/CD Pipelinebuild-pipelineFixed programs, registered Tools, with no judgement in them.
Translatorstranslation-source-leadThe source-language lead and the locale translators of the harness’s translation process. The app’s strings are one more template to them.

Steps

Every one of the 7 step(s) is documented.

steplaneskill / sub-processwhat it does
Declare the web-app directory
A_Declare
App authorweb-appsThe layer declares a directory of kind web-app in its <name>.json and puts a web-app.json (web-app/0.1.0) at its root: id, title, description, how it builds, the languages it ships (the site’s six UN languages: ar, en, es, fr, ru, zh), the layer directories it reads at build time (contentFrom), a size budget, and for a copied app its licence and source. Its UI strings are one flat catalog in the source language (i18n.catalog). No publish script, no site.build.keep, no harness of its own.
Extract the app’s translation templates
A_Extract
CI/CD Pipelineweb-appsTool web-app-build (web-apps:build --extract): the catalog becomes translations/<locale>/apps/<id>.pot in the declaring layer, one ui-string entry per key with the key as msgctxt. This is the app’s “refresh the templates” step, named in the layer’s AGENTS.md so the translation watcher runs it too.
Translate into each locale
Call_Translate
Translatorscalls Multi-locale translationThe harness’s multi-locale translation, unchanged: the templates are merged into each locale’s .po, new and fuzzy strings are translated with the fixed terms, the gates run, and each locale is its own PR. Afterwards the translation watcher (Process_TranslationRefresh) keeps them current as the catalog moves.
Check the declaration and translations
A_Check
CI/CD Pipelineweb-appsTool web-app-build (web-apps:build --check): the manifest parses, package.json has the build script, a lockfile pins exact versions, no two layers claim one app id, every template is current, and no translation drops or adds a {placeholder}. Untranslated strings are reported, not failed: the app falls back to the source text per string.
Fix the declaration or the catalog
A_Fix
App authorweb-appsThe author fixes what the check named (the manifest, the lockfile, a clashing id, a stale template) and commits again. A translation that dropped a placeholder goes back to its locale’s translator through the same PR route.
Build into its own chrome-less route
A_Build
CI/CD Pipelineweb-appsTool web-app-build (web-apps:build, run with the other declared visualiser writers): each locale’s strings are written to <i18n.out>/<locale>.json from the .po (building is the injection), the app installs from its lockfile and builds, and the build is copied to <locale>/<harness>/apps/<id>/ with every page marked folio-navbar: none and rendered-by: web-app-build; the apps/ index lists every app with its size. No other page embeds an app, so it loads only when a reader opens its route.
Review the size against its budget
A_Size
CI/CD Pipelineweb-appsThe index flags an app over its sizeBudgetMB; the site size review reads it with the rest of the site. Over budget is a finding for the author, never a silent publish.

Decisions

Every one of the 1 decision(s) is documented.

decisionwhat decides itbranches
Declaration and translations valid?
GW_Valid
Answered by the check’s exit code.yes → Build into its own chrome-less route
no → Fix the declaration or the catalog

folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed dev