Offline Demo: From Inputs to Local Simulation
Generate fictional inputs, validate configuration and inspect a timeline-based local KabuForge simulation.
Create fresh fictional inputs
First complete the quickstart. Run from the source root with the same active environment and a new output directory.
kabuforge demo --out output/demo
python -m framework_v2.cli validate output/demo/paper.json
python -m framework_v2.cli history output/demo/backtest.json --timeline output/demo/timeline.json --out output/historyInspect and reproduce the local run
The demo writes configurations and synthetic snapshots. Validation checks their schema and fields. History consumes an explicit timeline and produces reports and a local SQLite ledger under output/history. Review targets, risk results, order intents and simulated events together.
What this example proves
Keep runs separate
Preserve the generated inputs, configuration, timeline, source tag and environment with each result. Compare runs only when source identity, inputs and environment match. This supports reproduction of the software simulation, not a claim of reproducible real-market performance.
Applies to: v0.1.1 · Public source docs/DEMO.md
Reviewed · KabuForge