Skip to content

eFEC Platform Documentation

The eFEC platform is an event-driven financial entity compliance engine. Every business mutation flows through process_event, is signed by an actor key, and is recorded in an append-only hash chain.

This documentation set is intentionally lean: active specifications live under Specifications, draft direction lives under Proposals, and older planning artifacts are removed once promoted or superseded.

Start here

Need Document
Engine write path, events, signatures, chain rules Engine Specification
Core process/event/workflow model Core Engine Model
Workflow JSON syntax Workflow DSL v2
Workflow identity, namespaces, registries Workflow Paths and Namespaces
How the UI receives available actions Available Action Descriptors
How users build/sign/submit actions Universal Action Dialog
Canonical event construction Canonical Input and Event Builder
Draft product/architecture direction Proposals
Editor and workflow workspace model Workflow Workspace Editor

Current state

  • Workflow DSL v2 is active.
  • Canonical $path is workflow identity and organization.
  • Top-level workspaces are discovered dynamically from deployed workflow paths.
  • system/bootstrap is the only visible bootstrap workflow.
  • Business/demo workflows deploy through signed process_event events.
  • Event envelopes use canonical action.input; legacy action.data is rejected.
  • Server/Rust-WASM owns workflow evaluation; frontend renders server/core outputs and collects input.
  • Process timelines start at the process create event and show process-local actions.

Active proposal under review

Verification snapshot

After source reset/reseed, expected guardrails:

  • no zero-signature events,
  • no legacy action.data envelopes,
  • only system/bootstrap is visible as a bootstrap workflow,
  • no $category, no active v1 workflow shape, no basename version suffixes,
  • workflow deployment events are signed,
  • frontend does not evaluate workflow availability semantics.