Where everything lives

The workspace repository is C:\Users\chris\Documents\Siemens\innexis-vsi, a private git repository (origin on GitHub, branch master). Pull before writing, push after committing, stage by name. Generated twin folders, the SysML kernel and build products are ignored.

Pipelines and tools (repository root)

file	role
extract_icd.py	Teamcenter read: interfaces, port assignments, signals, directions, to an ICD JSON
port_owners.py	Teamcenter read: which logical block owns each port (BOM structure), to owners.json
icd_to_vsi.py	ICD JSON to vsiBuild command file, with grouping, exclusions, --python-blocks, an assumptions file per run
gateway_map.json	declared interface-class to protocol mapping, reviewable
sysml2vsi.py	SysML v2 text to vsiBuild command file (reverse of the exporter)
vsi2sysml.py	command file to SysML v2 package plus diagram views
vsi_cmd.py	the command-file parser vsi2sysml.py imports; keep the two together
validate_sysml.py	runs the OMG pilot kernel headless on a SysML v2 file
vsi_viz.py	command file to an HTML twin diagram; since 2026-09-10 it lives in the vsi-message-flow repository (the pages under viz\ stay here as evidence)
msp2_dump.py, msp2_author_icd.py, msp2_author_ports.py	authored the MSP-2 ICD and ports in Teamcenter
port_owners.py, probes\	the port-write probes that cracked exportCollection
wildfire_grouped.vsi.cmd, wildfire_py.vsi.cmd, msp2_A.vsi.cmd, msp2_B.vsi.cmd, msp2_A_sysmlblock.vsi.cmd	the generated command files, each with its .assumptions.md
README.md	the chronological log of the work, newest first; LICENCE-REQUEST.md the licence history
HANDOFF-message-animation.md	the brief for animating message flow over a twin

Glue and checking

folder or file	role
twin_glue\generic_stim.h, generic_stim.py	the stimulus primitives, C++ and Python, same formula
twin_glue\apply_glue_generic.py	writes the glue into every component's user regions from the command file; writes glue_wiring.json
twin_glue\check_traces.py	verifies a run from the traces; --selftest proves the checker
twin_glue\README.md	roles, periods, the CAN mute, run history with numbers
msp2_glue\	the scripted MSP-2 scenario: header, host-side test, apply script

Evidence

folder	role
runs\DATE-TIME-TWIN-RESULT\	traces, the glue_wiring.json that goes with them, checker output, fabric log excerpt; runs\README.md indexes them
runs\evidence\	as-generated broken files and control command files for reported defects
sysml\	the SysML v2 exports and the hand-authored Msp2_A_sysmlblock.sysml
viz\	rendered twin diagrams and the Modeler's per-bus SVGs
templates\	eight two-component command files with a README, each built and run

Twin folders (not tracked, regenerated by vsiBuild)

location	twin
innexis-vsi\workspace\WildfireDT	63 C++ blocks
innexis-vsi\workspace_A\Msp2DT_A, workspace_B\Msp2DT_B	MSP-2 candidates
D:\wfpy\WildfirePyDT	Wildfire with 4 Python blocks (short path for MAX_PATH)
D:\wfpy\Msp2DT_S	the SysML-driven MSP-2 twin

Inside a twin folder: TWIN.vsi and TWIN.dt (what vsiSim reads), src\COMPONENT\ (one folder per component with its skeleton and the glue's stimulus files), Makefile and Makefile.clientN and Makefile.server, vsi.build\_objs (executables, Python gateway extensions), vsi.sim\_logs (fabric log, one log per component, the trace CSVs), glue_wiring.json.

Outside the repository

location	role
D:\InnexisVSI\innexis_home\vsi_2026.2	the VSI installation; docs\ holds the vendor PDFs; env_vsi.ps1 and env_vsi.win.txt the environment
C:\ProgramData\Siemens\License Server\ActiveLicenses	the licence files, one per issued increment set; saltd.log one level up
C:\Users\chris\Documents\Siemens\vsi-docs-kb	this knowledge base's content
C:\Users\chris\Documents\Siemens\vsi-knowledge-base	the local site that serves it on port 3026
roadmap.xcelerator.us, lane vsi	every shipped item with its evidence pointer