mojohmojoh/ docs

mojoh docs: ERP modelling, migration and integration

start with memory. grow with flows. keep everything in sync.

These docs are for engineers, integration teams and design partners who want to use mojoh. Today you can define a type, map a source, build a flow and run a test migration. Start with Getting started below.

mojoh models your ERP truth as motes (typed records) and links (relationships). Think of motes as neurons, links as synapses, and long paths as memories the system can reuse. In practice, they're just typed records and relationships that your migrations, integrations, data quality checks and agents can reuse—no sci-fi required.

These docs are in early release. Full guides for ERP templates, flows, typed I/O and data quality flows are coming soon.

Concept FAQs

For more on how mojoh fits with warehouses and iPaaS, see co-existence and integrations.

Getting started

Coming soon

Here's the basic path people follow today. Detailed guides are coming, but you can already think in these steps:

  1. Define or reuse an ERP template type (e.g. GL, AP, AR).
  2. Connect your source systems and target ERP using mappings.
  3. Create a flow that prints migration or integration code for that template.
  4. Add typed I/O, rollback and audit so you can replay safely.
  5. Configure data quality checks and cleansing/enrichment steps on the same models and flows.
  6. Re-run these flows between test cycles instead of doing data quality in spreadsheets.

Core concepts (overview; detailed docs coming soon)

Enterprise knowledge — the facts, relationships and rules about your business captured as types and motes.

Information types — strongly typed entities (for example GL, AP, AR, vendors, customers) with auto-rendered pages.

Mappings — reusable relationships between sources and targets that can be carried across programmes.

Flows — ordered steps that transform and move data; mojoh uses these to print code.

Motes & links — the graph layer: motes store typed facts, links connect them.

Test & data quality — validation rules and failed-record capture on top of the same models and flows.This replaces the colour-coded spreadsheet filters teams use between test runs.

Cleansing & enrichment — cleansing flows run on the same models — not a separate platform.These flows are designed to be reused between cycles instead of one-off spreadsheet hacks.

ERP templates (coming soon)

SAP, D365 and Oracle patterns.

Flows (coming soon)

Transformations, checks, migrations.

Typed I/O (coming soon)

Guardrails and predictable writes.

For how mojoh fits with warehouses and iPaaS, see co-existence.

Co-existence

How mojoh works with your warehouse, model provider and iPaaS.

What's next: Upcoming docs will cover how to extend mojoh with new domains, apps and target systems.

For project-based ERP delivery support, talk to elfware.com.