B4 · Proof · OEM DC/DC (anon.) PoC · 2 rules Topology anonymised
The rule set decides
whether it ships.
Every INSERT runs through the grammar: if a test lacks its requirement, the state is illegal — and the gate stays closed. Not because someone says no, but because the graph computes no.
INSERT in — verdict out.
The instrument runs the real sequence: a test without a requirement violates R1, the release is rejected — only FIX heals the state, then the same traversal produces four artifacts from one source.
▸ No workaround, no override — the rejection is the feature
Standards become rules in the project graph.
ViFACTS! is the core of Viprove: ontology plus rule engine. Every check a traversal, every result a sealed entry — release gating comes from the graph, not from meetings.
One INSERT becomes four artifacts.
Release notes, budget delta, SOW adjustment, stakeholder info — produced by the same traversal, sealed from a single source. No report copied by hand. Artifacts written by the graph itself.
The graph reads where the project lives.
Reads
Tracker items, requirements, tests — via REST API + webhooks
Transforms
CB object → graph nodes + edges · every event = INSERT/UPDATE against the rules
Writes back
Verdict, comment, workflow transition · 4 artifacts · sealed
Honest status.
What this demo is — and what it is not.