Available now · free
Evidence Preflight
Up to three non-confidential caller-supplied claims. Structural triage only; no source fetching or verification.
Run the preflight →Commercial-use evidence layer · maha-public-evidence-workflows/1.0
From a claim-shaped question to a governed machine delivery.
These worked examples connect Maha’s existing evidence and machine infrastructure. They show what passes, what refuses, what can be independently recomputed, and which commercial step is actually available.
Every input is synthetic. No customer submission, private corpus passage, credential, release authority, payment, or completed sale is represented.
Proposed · purchase disabled
Bounded Evidence Dossier · $250
Up to ten bounded claims in a digest-bound JSON-LD and PDF package. The published offer is informational, not checkout.
Read the offer boundary →Private engagement
Licensed evidence retrieval · $1,250/month
The developer plan contract exists, but its evidence runtime is not publicly callable. Access starts with a scoped private integration.
Discuss an integration →8 worked examples
Evidence Preflight examples
Eight examples run synthetic claims through the real deterministic compiler: complete packets, metadata-only citations, missing locators, unsupported inference, identity failure, rights uncertainty, and mixed outcomes.
5 steps · 3 refusals · digest-bound
Preflight a DOI with an exact locator
A complete structural packet can be routed to source inspection, while the preflight still refuses to call the claim verified.
Open worked example →
5 steps · 3 refusals · digest-bound
Preflight a public URL and authorized excerpt
The caller supplies the excerpt and locator; the tool checks structure while making no claim that it opened the URL.
Open worked example →
5 steps · 3 refusals · digest-bound
Route a metadata-only source honestly
The preflight keeps bibliographic identity separate from content evidence and blocks the claim before inspection.
Open worked example →
5 steps · 3 refusals · digest-bound
Catch an unsupported causal inference
Lexical and scope checks route the claim for revision; they do not attempt to settle causality.
Open worked example →
5 steps · 3 refusals · digest-bound
Refuse an invalid source identity
The source remains unresolved even when the excerpt looks relevant; topical text cannot repair a broken identity.
Open worked example →
5 steps · 3 refusals · digest-bound
Refuse an unlocated excerpt
A reader must be able to find the passage in the declared version; an excerpt without location stays blocked.
Open worked example →
5 steps · 3 refusals · digest-bound
Keep rights and access uncertainty visible
No. Access status and reuse basis remain separate fields, and either can block further processing.
Open worked example →
5 steps · 3 refusals · digest-bound
Preflight three claims with mixed outcomes
Each claim receives its own decision; one complete claim cannot make two incomplete claims look ready.
Open worked example →
6 worked examples
Dossier and calculation-receipt examples
Six examples cover package verification, coordinated tampering, reproducible interval arithmetic, absent calculations, PDF derivation, and runtime-witness binding.
5 steps · 3 refusals · digest-bound
Verify a JSON-LD Evidence Dossier package
Recompute file, passage, claim, and package digests before reading the document as a coherent evidence artifact.
Open worked example →
5 steps · 3 refusals · digest-bound
Detect manifest and payload tampering
The outer package digest binds the manifest, so coordinated edits still fail unless the package identity also changes.
Open worked example →
5 steps · 3 refusals · digest-bound
Recompute a deterministic calculation receipt
The verifier repeats a fixed-point interval operation from explicit inputs, units, arithmetic policy, and kernel identity.
Open worked example →
5 steps · 3 refusals · digest-bound
Preserve an absent calculation instead of inventing one
It records that no calculation applies and keeps the calculation attachment empty.
Open worked example →
5 steps · 3 refusals · digest-bound
Render a PDF only after package verification
The human-readable report is derived from already-verified package data and never becomes a second source of truth.
Open worked example →
5 steps · 3 refusals · digest-bound
Bind a runtime witness to a dossier claim
It binds execution environment, inputs, outputs, seeds, and artifacts to claim and dossier identifiers without claiming independent reproduction.
Open worked example →
6 worked examples
Governed MCP retrieval and release guides
Six guides connect discovery, identity, entitlement, exact active releases, quota, replay, private delivery receipts, and acknowledgement.
5 steps · 3 refusals · digest-bound
Discover capability before requesting evidence
Read public capability and boundary documents first; discovery describes a tool but grants no entitlement.
Open worked example →
5 steps · 3 refusals · digest-bound
Bind machine identity to a narrow entitlement
A credential, client, grant, plan, tool, validity window, and quota are bound into one immutable grant snapshot.
Open worked example →
5 steps · 3 refusals · digest-bound
Retrieve only an exact active released revision
The execution binds the selector to an active release, its target digest, release digest, and canonical path before returning evidence.
Open worked example →
5 steps · 3 refusals · digest-bound
Refuse stale releases and substituted selectors
Selector, request digest, active release, and execution reservation remain bound; changing any one creates a conflict rather than a convenient fallback.
Open worked example →
5 steps · 3 refusals · digest-bound
Meter one execution and replay it safely
An identical request reuses the original execution identity and bytes; changed material under the same request ID is refused.
Open worked example →
5 steps · 3 refusals · digest-bound
Acknowledge a digest-bound evidence delivery
The receipt joins execution, request, projection, release, record revision, canonical path, and substantial publication into one independently checkable identity.
Open worked example →
Public workflow pages
20
Registry digest
sha256:ff1891c8a5eb47c80557c38dca0742e3ebd389621a37b97bf1d7cd6cd1b28940