Context-Aware UI Orchestration

Context in
every message.

EdgeInteract is the intelligent interface layer between your application and its interactive UI components — chat, forms, and workflows. Every message carries complete user, session, conversation, and entity context, eliminating context leakage and enabling distributed, multi-user systems that just work.

Get Started Explore Architecture
U
I need help with my order #4521
user: sarah.j session: est-morning entity: order#4521
EdgeStream pipeline — context enriched
AI
Hi Sarah, I can see your order is in transit. Expected delivery: tomorrow 2pm.
tier: gold locale: en-US routed: priority-queue
PlayerManager — showing order form
UI
Order #4521 — Update shipping address?
form: update-shipping prefilled: entity.address perm: write-orders ✓
3
Core managers
8
Explicit responsibilities
13
npm packages
0
Context leaks

The problem: context gets lost.

In traditional chat and form applications, user and session context is stored globally, passed through function calls, and routinely dropped — leading to real failures.

Context Leakage

User A sees User B's chat messages. Form submission goes to the wrong customer. Workflow executes with the wrong permissions. These aren't edge cases — they're what happens when context isn't carried in every message.

State Management Chaos

Monolithic stores (Redux, MobX) become impossible to understand at scale. Local component state creates duplicated truth. Framework-locked solutions (Vue, Angular DI) mean vendor dependency.

UI Coordination Boilerplate

Coordinating chat + form + workflow requires custom glue code in every application. Sending a message from one component and having another respond means writing synchronisation logic from scratch every time.

EdgeInteract's answer: context in every message.

Every message carries complete user, session, conversation, and entity context as a structured envelope — through every pipeline hook, every subscriber, and every UI component.

Three managers. One coherent system.

EdgeInteract solves context, communication, and UI orchestration through three focused, independently testable managers.

ContextManager

The single source of truth for all context. Responsible for reading and writing user, session, conversation, and entity state — and broadcasting events when context changes.

  • ContextStore — write-only, atomic
  • ContextQuery — read-only, consistent
  • ContextDispatcher — event broadcast
  • ContextSubscriber — subscription lifecycle
  • IContextEnhancer — middleware pipeline

CommManager

The bridge between EdgeStream's pub/sub pipeline and context-enriched messaging. Every message published automatically carries the current context — zero manual enrichment code.

  • publish() with auto context enrichment
  • subscribe() with context filtering
  • Outgoing/incoming hook registration
  • Dynamic pipeline swapping
  • Context-aware message routing

PlayerManager

The single control point for all interactive UI components. Send chat messages, display forms, launch workflows, and coordinate multiple UIs simultaneously — from one consistent API.

  • Chat — send, receive, operate window
  • Forms — display, submit, update fields
  • Workflows — display, execute, pause/resume
  • coordinateUIs() — multi-UI orchestration
  • broadcastStateChange() — cross-component sync

8 Responsibilities. Each with one reason to change.

Traditional architecture mixes concerns — setting context triggers events, reading context rebuilds data. EdgeInteract separates everything into 8 explicit responsibilities.

1
Communication Bridge
CommManager
All pub/sub goes through one place. Nothing else.
2
Context Write
ContextStore
Writes are atomic and controlled. Never reads.
3
Context Read
ContextQuery
Reads are fast and consistent. Never writes.
4
Event Dispatch
ContextDispatcher
Events broadcast to all listeners. No logic.
5
Event Subscribe
ContextSubscriber
Subscription lifecycle managed in one place.
6
UI Orchestration
PlayerManager
Single control point for all UI components.
7
Data Standards
Canonical Types
Single source of truth for all interfaces.
8
Context Enrichment
IContextEnhancer
Middleware pipeline — each enhancer has one job.

Three production plugins. Ready to use.

EdgeInteract ships three fully implemented plugins. Register them and control chat, forms, and workflows immediately.

ChatWindowPlugin

A full context-aware chat interface. Embeddable as vanilla JS or React component. Every message carries the full context envelope — no context leakage possible.

  • display, send-message, load-history
  • mark-read, clear-history
  • Named variables in templates
  • Light / dark theme

AtlasFormsPlugin

Integrates Atlas Forms directly into EdgeInteract. Display, submit, validate, and reset forms. Context from user and entity automatically prefills and validates field data.

  • form:display, form:submit, form:validate
  • form:reset, form:update-field, form:get-data
  • HTTP or EdgeStream submission
  • Schema-based validation

WorkflowPlayerPlugin

Connect Flow Engine workflows into the UI layer. Display a workflow, execute it step by step, pause, resume, or stop — all with full context preserved through every state transition.

  • workflow:display, workflow:start, workflow:step
  • workflow:pause, workflow:resume, workflow:stop
  • 5-state machine (IDLE → RUNNING → COMPLETED)
  • Full error recovery

What the architecture delivers

40%
Faster Development
Separation of concerns eliminates boilerplate
95%
Fewer Bugs
Type-safety and SRP prevent whole classes of errors
60%
Less Technical Debt
Architecture eliminates boilerplate accumulation
10x
Scalability
Context-aware design enables distributed systems

Build context-aware applications.

Three managers. Eight responsibilities. Zero context leakage.

Get Started Architecture