Getting started

Jive keeps reported status aligned with evidence-backed integrity across your scope hierarchy.

Requirements

• A basic scope tree with outcome milestones (for example, "Design approved" -> "API finalized" -> "Launch ready")
• Access to at least one evidence provider (GitHub is available now)
• Optional claim sources (Jira, docs, or manual attestation)

Fast path (15 minutes)

1. Sign up and create (or join) a Jive organization.
2. Connect GitHub and select the repositories you want to observe.
3. Create a scope tree (product -> feature -> project).
4. Add milestones (and optional tasks) under the project.
5. Define criteria in the onboarding Criteria form (approved PR, required checks, deploy signals).
6. Map claim sources (Jira, docs, or manual attestation) and link criteria to claim triggers.
7. Review integrity badges (Verified, Drift, Unverified, Unknown).
8. Optional: publish a Jive status check to block merges when integrity is not verified.

Need help connecting GitHub? See the GitHub integration guide.

Onboarding criteria form

Use a structured form during onboarding so criteria are explicit and repeatable across teams.

Recommended fields:

• Criterion name
• Scope (product, feature, project, or milestone)
• Evidence source (for example GitHub checks, approvals, deploy signals)
• Requiredness (required or optional)
• Freshness window (how long evidence is valid)
• Optional claim trigger link (for Drift checks)

Evaluator section (required):

• Evaluator type (all_of, any_of, threshold, or custom rule)
• Inputs (selected evidence signals and filters)
• PASS condition
• FAIL condition
• UNKNOWN condition (missing, stale, or partial evidence)

This evaluator section defines the evaluation logic users expect. Without it, criteria are descriptive only and cannot be computed deterministically.

First scope example

Project: Release Service B

Claimed state:

• Jira status = Done

Criteria:

• Deployment signal for Service B = production
• QA approval status = approved

Result:

• Drift if Jira says Done but criteria FAIL or UNKNOWN.
• Verified once evidence passes and all criteria are satisfied.
• Unverified if a claim exists but no linked criteria can verify it yet.

Next steps

• Add more scope layers across teams and dependencies.
• Expand criteria to cover upstream services, QA, and approvals.
• Invite additional teams and define ownership boundaries.
• Enable guardrails where you want evidence-required actions.
• Configure audit retention and export if you need compliance evidence.