Martenweave Examples
The core repository includes examples that can be validated and indexed locally. They are small enough to inspect, but realistic enough to demonstrate the registry workflow.
Core repository:
https://github.com/metalhatscats/martenweave-core/tree/main/examples
Northstar Mobility Group — Synthetic Pilot
Path:
examples/northstar_mobility_pilot
Best for:
- an explicitly fictional, multidomain SAP S/4HANA transformation scenario;
- Business Partner/Customer, Supplier, Material, Sales, Procurement, Logistics,
- deterministic CSV/XLSX profiling, intentional gaps, ownership blockers,
- a connected local Workbench driven by the same canonical repository.
and Finance relationships in one canonical model;
decisions, evidence, pending proposals, and cross-domain impact; and
Run the complete reproducible workflow:
bash scripts/demo_northstar_pilot.sh
Read the Northstar synthetic pilot walkthrough for the verified results, fictional roles, limitations, screenshot, and full command sequence.
Customer / Business Partner
Path:
examples/customer_bp_model
Best for:
- SAP Business Partner to Customer migration context
- customer sales area and customer group examples
- SAP table/field context such as
KNVV-KDGRP - decisions, issues, mappings, value lists, validation rules, and impact analysis
Run:
.venv/bin/martenweave validate --repo examples/customer_bp_model
.venv/bin/martenweave build-index --repo examples/customer_bp_model --jsonl
.venv/bin/martenweave impact FEP-S4-KNVV-KDGRP --repo examples/customer_bp_model
Synthetic Customer 360 Migration Demo
Path:
examples/synthetic_customer_migration_demo
Best for:
- a fully fictional, explicitly isolated demo dataset
- collecting and reconciling customer evidence from Nimbus CRM, Orbit Commerce, and Ledger AR
- mapping through the Atlas Migration Hub before the SAP S/4HANA target
- explaining field-level mappings, value normalization,
IntegrationFlow, andDataFlowSteplineage without showing client data

*Synthetic demo evidence: this local, read-only viewer is generated from fictional sources only. The SYS-DEMO-* identifiers, account references, customer names, and group values are invented for explanation and test use; they are not masked production data.*
Run:
.venv/bin/martenweave validate --repo examples/synthetic_customer_migration_demo
.venv/bin/martenweave build-index --repo examples/synthetic_customer_migration_demo --jsonl
.venv/bin/martenweave trace FEP-DEMO-HUB-GOLDEN-NAME --repo examples/synthetic_customer_migration_demo
.venv/bin/martenweave impact FEP-S4-KNVV-KDGRP --repo examples/synthetic_customer_migration_demo
Supplier / Vendor
Path:
examples/supplier_vendor_model
Best for:
- SAP supplier/vendor master-data patterns
- LFA1, LFB1, and LFM1 field endpoint examples
- gap-to-proposal workflow using a synthetic vendor extract
Run:
.venv/bin/martenweave validate --repo examples/supplier_vendor_model
.venv/bin/martenweave build-index --repo examples/supplier_vendor_model --jsonl
.venv/bin/martenweave gaps \
examples/supplier_vendor_model/data/samples/vendor_extract.csv \
--repo examples/supplier_vendor_model \
--check-model
Simple Product
Path:
examples/simple_product_model
Best for:
- first-time onboarding
- simple table mode
- small product CSV profiling
- understanding domains, entities, attributes, field endpoints, and value lists
Run:
.venv/bin/martenweave validate --repo examples/simple_product_model
.venv/bin/martenweave build-index --repo examples/simple_product_model --jsonl
.venv/bin/martenweave search "product" --repo examples/simple_product_model
Generic Product
Path:
examples/generic_product_model
Best for:
- non-SAP model registry use cases
- generic product data model examples
- system lineage and integration-flow examples
Run:
.venv/bin/martenweave validate --repo examples/generic_product_model
.venv/bin/martenweave build-index --repo examples/generic_product_model --jsonl
.venv/bin/martenweave scorecard --repo examples/generic_product_model
What Examples Are Not
- The example content is not certified by SAP.
- They are not customer implementations.
- They are not generated indexes to preserve by hand.
- They are not proof of a hosted SaaS workflow.
They are starter models for testing, learning, and contributing better scenarios.