What it does
Each flow is a protocol FSM. You run it on a lab host or in the pipeline — exit codes and JUnit either way.
States wait, transitions check and extract, then send. Schema-enforced at load. You author the procedure once.
run-flow and run-suite exit 0 on pass. Gate the pipeline on the exit code, or capture JUnit with -output.
NGAP, NAS, SBI, REST, and GTP-U on the unsigned binary. PFCP is licensed — not community, not on the unsigned floor.
kind: flow
name: registration
role: gnb
states:
- id: start
send: RegistrationRequest
- id: wait_accept
check: RegistrationAccept
extract: suci$ d3x-run run-flow registration \
-templates ./d3x-templates \
-output junit.xml
ok registration 184ms
exit 0How you run it
You run a binary on your host. An optional UI can embed next to it. That is not our cloud console.
On-prem CLI
d3x-run on the lab host or in CI. No SaaS buy button. No cloud console to log into.
Optional embedded UI
A Runner UI can sit beside the CLI for operators who want a screen. It is local to the binary.
Worker daemons
If you attach workers, they are Runner daemons on a lab host — dispatch jobs, return reports. Not an LLM.
Who it's for
People who already run a 5G SA core and need a tester on the wire.
Drive NGAP, NAS, SBI, and GTP-U against the core you already operate. Same YAML the pipeline will run.
Exercise the procedures your NF claims to support. Fail the build when a check misses.
One-shot CLI, exit codes, JUnit. Unsigned floor is 1000 UE — load is licensed.