brawliot/abs

How brawliot/abs works

This repository implements a business-transaction workflow platform: users submit actions through a web UI, text may be interpreted into an intent, policies judge whether a lifecycle transition is allowed, and the runtime records events from which state is derived. Around that core are business archetypes, rule/fact evaluation, process generation and diagnosis, presentation, and tenant-aware hosting. The README is empty; connections below are limited to source excerpts and SOURCE INDEX references, so unsampled subsystem links are omitted where their callers are not shown.

Main entry points: action-handler.ts Action handler · derivation.ts State derivation · catalog.ts Archetype catalog · server.ts HTTP server

Components 21

User interaction

HTTP server web/server.ts
Action handler web/action-handler.ts
Intent interpreter interpreter/interpret.ts
UI rendering web/render-app.ts

Transaction model

Archetype catalog archetypes/catalog.ts
Archetype composition archetypes/composition.ts
Lifecycle model core/lifecycle.ts
Domain elements elements/subtypes.ts
State derivation core/derivation.ts
Domain events core/events.ts

Rules and facts

Policy judge policies/judge.ts
Fact provider facts/provider.ts

Configuration and insight

Process composer composer/compose.ts
Process generator generator/generate.ts
Business diagnosis diagnosis/engine.ts
Insight presenter presenter/present.ts

Runtime platform

Event store core/event-store.ts
LLM client llm/client.ts
Identity and tenancy policies/identity.ts
Tenant routing hosting/pool-router.ts

Other components

User

Connections 23

User → HTTP server: submits actions web/server.ts
HTTP server → Action handler: routes actions web/server.ts
HTTP server → UI rendering: renders views web/server.ts
Action handler → Intent interpreter: interprets input web/action-handler.ts
Action handler → Policy judge: requests judgment web/action-handler.ts
Action handler → State derivation: derives current state web/action-handler.ts
Action handler → Archetype composition: checks composition blocks web/action-handler.ts
Action handler → Event store: reads event history web/action-handler.ts
Action handler → Domain events: uses transition events web/action-handler.ts
Archetype catalog → Archetype composition: supplies definitions archetypes/composition.ts
Archetype catalog → Lifecycle model: defines workflows
Archetype catalog → Domain elements: uses element types
State derivation → Lifecycle model: derives from lifecycle core/derivation.ts
State derivation → Domain events: derives from events core/derivation.ts
Policy judge → State derivation: checks transition policies/judge.ts
Policy judge → Fact provider: evaluates fact rules policies/judge.ts
Tenant routing → Event store: configures tenant store hosting/pool-router.ts
Tenant routing → Identity and tenancy: configures identity store hosting/pool-router.ts
Business diagnosis → Archetype composition: uses archetype composition diagnosis/engine.ts
Process generator → Business diagnosis: supports process analysis
Process composer → Process generator: produces process input
Insight presenter → UI rendering: feeds user-facing insight
Intent interpreter → LLM client: extracts with LLM

Drawn by GitDiagram on October 2, 2026 from the repository's file tree, README and source files. Read as Markdown ·