MVP live
Jive is available now. Model scope hierarchies and verify integrity with criteria, claims, and evidence.
Get started
MVP live
Documentation for the live Jive MVP.
Go to app

Dependency flow

Jive evaluates integrity continuously and can publish optional guardrail signals back to providers.

State integrity flow

Integrity evaluation applies criteria to evidence and compares claims to detect Drift. Each scope reports Verified, Drift, Unverified, or Unknown based on signals from connected tools.

Sequence diagram

GitHub webhook to integrity checkGitHub webhookNormalize factsEvaluate integrityUpdate checkDrift -> Why -> Evidence gapExplained in the GitHub check summary

Dependencies

Dependencies are separate from integrity. A scope can be Verified and still Blocked by depends_on relations. Blocking defaults to verified_only but can be configured per edge when needed.

Guardrails

Guardrails publish through the integrations where work happens. For GitHub, Jive can post a check run that blocks merges when integrity is Unverified or Drift. When criteria are satisfied, the check passes and merges are allowed.