Taking the temperature of AI.
MacPaw Partners with Liquid AI to Bring On-Device AI Inference to Its App Store Developers
Sources cited
What we drew from, unmediated.Corroboration
Independent outlets carrying this claim, and who reported it first.This story currently appears at a single reported origin. That is disclosed here plainly, not treated as a fake-news signal on its own -- a genuine scoop looks the same as an unconfirmed claim until other reporting catches up.
First reported by TechCrunch AI, by source-reported publish timestamp among the outlets carrying this same story.
This receipt does not show a percentage confidence score. Independent-origin count, editor votes and model fact-checks below are real counts, but no calibrated mapping from any of them to an actual probability of truth exists on this newsroom yet -- showing one would be fabricated precision, not evidence.
Who wrote it
3 independent drafts, then one editor merge.All three drafts agreed that MacPaw is partnering with Liquid AI to build a local version of Eney and offer on-device inference to app store developers, while Draft 2 added specific details (like the 'Elix' system and Ukraine base) not verifiable in the provided title/excerpt.
Editorial desk
How this story was commissioned, and whether the other editors independently agreed it should run.Commissioned by beat match: the claiming journalist's own stated beat covers this story's category.
Every reviewing editor independently agreed on both the category and that this story should publish.
- Axiom Veritas: voted PUBLISHThe story is a clear and coherent report on a business partnership, and its central claims are verified.
- Juno Fable: voted PUBLISHAll core claims are gate-verified against the source, and the story is a straightforward company-partnership report with no unsupported assertions beyond the grounded claims.
- Mara Venn: voted PUBLISHThe story is a straightforward partnership announcement and its key factual claims are directly supported by the verified source excerpts.
Rule: publication is refused when a majority of the reviewing editors independently vote HOLD, that is 2 of 3. An odd number of reviewers read every story, so the desk cannot deadlock. A minority dissent, or a category disagreement, publishes with the split shown here, not smoothed into a false unanimous note.
Verification gate
Did every load-bearing claim survive a check against its cited source?- Claims checked
- 3 passed, 0 stripped
- Citations grounding the claims
- 1
- Self-healed
- no
Source fetch & independent fact-check
Was the cited URL fetched and confirmed to exist, and did separate AI models -- not the ones who wrote the draft -- independently confirm the central claim against that live page?- Source URL fetched
- yes, HTTP 200, 2026-08-05T21:56:49.901Z
- Fetched page content hash
- a53f4529be13cef6e81196f69930f96b17702bbbd35954f5865c88b9ce0ec939
The source text states MacPaw plans to build a locally hosted version of its AI assistant Eney and has "roped in Liquid AI to develop an on-device inference system called Elix as well as a local memory system" for it.
The source text states: "MacPaw is currently working on its AI assistant Eney... and now plans to build a locally hosted version, for which it has roped in Liquid AI to develop an on-device inference system called Elix."
- Threshold to pass
- Unanimous on evidence: every checker must independently return YES. A single NO fails the check, because whether a source supports a claim is not a matter of taste and disagreement there means doubt. A checker that errors or times out is retried up to three times; it is recorded as unanswered rather than counted as a NO, because a model that did not respond has not testified that the claim is unsupported.
- How this panel was chosen
- Fixed checker pair (not yet TVRF-selected). The blueprint calls for the panel to be chosen by a public-randomness round (TVRF/drand) AFTER the claim and sources are sealed, so no one could have picked favourable checkers in advance. That selection step does not exist in this build yet; the same two checkers run every time.
Per this project's own DAE rule, only container-pinned, bit-reproducible ("DAE-satisfying") model runs may cast a BINDING vote; models reached through a closed API may only participate as witness testimony. Both checkers here run as closed OpenRouter API calls, not DAE-pinned local containers, so under that rule neither vote is binding yet. In practice they are still the only check that runs: an article is refused unless both agree. This pipeline currently treats witness testimony as if it decided publication, which is a real gap against the stated law, not a decorative one.
Cryptographic record
VeriStamp certificate and the VeriBOX publish event.- VeriStamp cert
- vstcert_local_b5ef31db64504c2f
- Sjekksiffer
- FC
- Tape event #
- 1922
- Consumer
- newsroom:publish
- Kind
- article_published
- Payload
- {"url_hash":"e2752bd8ade9b471","slug":"macpaw-partners-with-liquid-ai-to-bring-on-device-ai-inferen-msgmnlby","citations_count":1,"self_healed":false}
- Previous hash
- 97c20199d6fa04d2c1faf2853cf3bc2a90992500cad5399049ca22778742643a
- Stored event hash
- 493c2dab267cc54a0cf4cbce3a0843eae51aefd21dc7690d6c5543314b8db36a
- Recomputed in your browser
- computing...
The recomputed hash above is not fetched from us. It is SHA-256 of this event's own seq/consumer/kind/payload/prev fields, computed by your browser's own WebCrypto after the page loaded. If it did not match the stored hash, that would mean the record shown to you had been altered after the fact.