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.
• No user-owned shape already using a Veritas shape name. The five names — Certainty, Support, Opposition, Consensus, Oracle — must be absent or already owned by the Veritas component (warmhub/veritas); a pre-existing user-owned shape under any of them fails the install with a shape-ownership error. Retract or rename the conflicting shape first.

Install

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

After the command returns, your repo has the five Veritas shapes and three subscriptions watching for new opinions. The CLI tracks the install so you can manage and tear it down later. (If a shape name collides with an existing user-owned shape, the install fails with a shape-ownership error — see Prerequisites above.)

Confirm the install succeeded:

wh component list --repo [your-org]/[your-repo]
wh component view warmhub/veritas --repo [your-org]/[your-repo]

Every wh component lifecycle command — install, view, doctor, teardown — addresses Veritas by its registered <org>/<name> ref, warmhub/veritas. The manifest’s reverse-DNS component.id (com.warmhub.Veritas) is manifest metadata, not a CLI argument.

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.	An Arc of two assertions, from → to.
Opposition	The belief that one assertion is evidence against another.	An Arc of two assertions, from → to.
Consensus	Veritas’s consolidated readout. Written by Veritas only.	An assertion (consolidating its Certainty opinions) or an Arc (consolidating its Support / Opposition opinions).
Oracle	A source pinned to fixed, maximum trust. A thing shape, not an assertion shape — you create one and name it as a source.	Not applicable — an Oracle is a thing, not an opinion about a target.

The four opinion shapes (Certainty, Support, Opposition, Consensus) 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.

Oracle is the one shape that is not an opinion. It is a thing you create to represent a definitionally-trusted source, with three optional fields — displayName, description, and an owner wref — and no opinion fields. See Oracles for when and how to use one.

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.

Credentials

Install provisions one credential set for Veritas, holding two shared secrets:

Secret	Used for
WEBHOOK_SIGNING_SECRET	Verifying the webhook deliveries WarmHub sends to the Veritas worker.
CLI_SIGNING_SECRET	Authenticating the reputation CLI calls the worker receives.

Setup populates both for you — you do not set either by hand. You can inspect the credential set with the wh credential commands.

Verifying health

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

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

A successful wh component install should land Veritas in ready — setup provisions the signing secrets for you, so you do not need to populate any credential keys yourself. doctor validates against the manifest recorded at install time. A current install includes all five shapes; if you installed Veritas before the Oracle shape existed, reinstall (or update) to refresh that record and add the fifth shape. If doctor reports degraded, something went wrong during setup or a resource has drifted; if it reports uninstalled, Veritas has been torn down. 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.

The reputation CLI

Once installed, Veritas exposes three commands for reading and seeding source reputation, dispatched through the component CLI:

wh component exec veritas list-reputations --repo [your-org]/[your-repo]
wh component exec veritas get-reputation --wref Source/research-team --scope WeatherClaim --repo [your-org]/[your-repo]
wh component exec veritas upsert-reputation --wref Source/research-team --scope WeatherClaim --belief 0.7 --disbelief 0 --uncertainty 0.3 --repo [your-org]/[your-repo]

See Reputation and the CLI for the reputation model, scopes, and seeding guidance.

Tearing down

Tear Veritas down without removing its shapes or assertions:

wh component teardown 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 — revokes the install’s tokens, and marks the component uninstalled. It is non-destructive: the five shapes stay in the repo, and all existing Consensus, Certainty, Support, and Opposition assertions and any Oracle things are left in place. You can still retract your own shapes, assertions, and things through the normal product surfaces without deleting the repo.

To bring Veritas back, reinstall it; the install record is revived. Because subscriptions are left paused, re-enable each one with wh sub resume <subscription-name> — reinstalling does not unpause them.

Next steps

• Writing opinions — how to author Certainty, Support, and Opposition, and how to read Consensus.
• Reputation and the CLI — read and seed source reputation.
• Oracles — pin a source to fixed, maximum trust.
• Overview — the conceptual model behind the five shapes.