Integration · connectors + two modes
The graph reads
where the project lives.
Codebeamer, vTestStudio, Jira, Git, CI — connectors are the senses of the twin. Every event becomes an INSERT/UPDATE against the rule set, and every verdict is written back.
No live tool needed.
The simulator plays the real pipeline: webhook from codeBeamer, transform into the graph, rule check, writeback. Violate R1 first, then request the release — the gate refuses.
▸ SPEC-CB-001 · what/why public · mapping internal
Deliver or connect.
Not every project needs a live connection from day one. The grammar works in both modes — the difference is how deep the graph sits in the toolchain.
Five senses, one grammar.
Direct DB coupling: unsupported by the tool vendor, breaks audit trails and permissions — and breaks on the first schema drift.
REST API + webhooks only. Every event is a check-mandatory INSERT, writeback as comment, workflow transition and artifact — traceable and versioned.
Honest status.
What is specified — and what is still mock.