Installing Veritas

Veritas is a registered WarmHub component — a packaged set of shapes, subscriptions, and credentials you install into any repo where you want reputation-weighted consensus over subjective-logic opinions.

Prerequisites

• An existing WarmHub repo to install into.
• A wh CLI authenticated against the org that owns the repo. See Getting access if you have not set this up yet.

Install

wh component install warmhub/veritas --repo [your-org]/[your-repo]

After the command returns, your repo has the four Veritas shapes and three subscriptions watching for new opinions. The CLI tracks the install so you can manage and tear it down later. (One prerequisite worth knowing: the four shape names Certainty, Support, Opposition, and Consensus must be absent or already owned by com.warmhub.Veritas — a pre-existing user-owned shape under any of those names will fail the install with a shape-ownership error. Retract or rename the conflicting shape and rerun if you hit that.)

Confirm the install succeeded:

wh component list --repo [your-org]/[your-repo]
wh component view com.warmhub.Veritas --repo [your-org]/[your-repo]

Veritas appears under three identifiers, each used by different commands:

Identifier	Form	Used by
Install source	warmhub/veritas	wh component install
Component ID	com.warmhub.Veritas	wh component view, teardown, and other lifecycle commands
Display name	veritas	wh component doctor (additionally; other commands need the full ID)

wh component list output shows the component ID — copy from there when you need it.

What gets installed

Shapes

Shape	Purpose	About target
Certainty	A source’s opinion about an assertion. The primitive bet that wagers source reputation.	An assertion (binary proposition).
Support	The belief that one assertion is evidence for another.	A Pair collection of two assertions, first → second.
Opposition	The belief that one assertion is evidence against another.	A Pair collection of two assertions, first → second.
Consensus	Veritas’s consolidated readout. Written by Veritas only.	An assertion (consolidating its Certainty opinions) or a Pair (consolidating its Support / Opposition opinions).

All four shapes carry belief, disbelief, uncertainty, and optional alpha. Certainty, Support, and Opposition additionally require a source wref — the thing whose reputation is wagered — and accept an optional rationale string. Consensus has no source or rationale; it is Veritas’s own consolidated readout, not a wager. See Writing opinions for examples.

Subscriptions

Veritas subscribes to changes on the three input shapes so it can re-solve whenever a new opinion lands:

Subscription	Triggers on
veritas-certainty	Add, revise, or retract of any Certainty assertion.
veritas-support	Add, revise, or retract of any Support assertion.
veritas-opposition	Add, revise, or retract of any Opposition assertion.

Webhook delivery is provisioned automatically — no setup required on your end.

Verifying health

Run health checks any time to confirm all declared resources are present and active:

wh component doctor veritas --repo [your-org]/[your-repo]

A successful wh component install should land Veritas in ready — setup provisions the webhook signing secret for you, so you do not need to populate any credential keys yourself. If doctor reports credentials-required or degraded, something went wrong during setup or a resource has drifted; if it reports paused, that’s the expected state after wh component teardown and is not an error. See Component lifecycle for the full state machine and recovery guidance — these are generic component states, not Veritas-specific. For credential-set inspection and key management specifically, see the wh credential commands.

Pausing

Pause all Veritas subscriptions without removing the shapes or assertions:

wh component teardown com.warmhub.Veritas --repo [your-org]/[your-repo]

Teardown pauses Veritas’s subscriptions — incoming Certainty, Support, and Opposition changes will no longer trigger a re-solve. Existing Consensus, Certainty, Support, and Opposition assertions remain in place. Resuming requires explicitly re-enabling each subscription with wh sub resume <subscription-name> — reinstalling the component does not unpause them.

Teardown is the only safe lifecycle operation today. A complete uninstall flow that removes component-owned shapes and the credential set is not yet supported — use wh component teardown to disable Veritas, and contact support if you need a full removal.

Next steps

• Writing opinions — how to author Certainty, Support, and Opposition, and how to read Consensus.
• Overview — the conceptual model behind the four shapes.