正在加载视频...

视频加载失败

加载此视频时出现问题。这可能是由于临时网络问题，或视频可能不可用。

What does it cost to sort 1,700 emails with Jev? I gave JEV each full email object: - Subject - body - sender No special changes. Jev sent back 4 values for each email: - Category: work, shopping, finance, security - Priority: low to urgent - Spam score: a... show more

The Startup Ideas Podcast (SIP) 🧃

48,152 subscribers

11,588 次观看 • 6 天前 •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

3 条评论

Miles S. 的头像

Miles S.6 天前

inbox triage just became background noise

Hai Nguyen 的头像

Hai Nguyen5 天前

is it really that cheap and fast or just because it’s new and doesn’t that many users

Greg Standford 的头像

Greg Standford5 天前

Category: work 😅

相关视频

How does Jev work? Jev takes two things: your input and an output schema. The schema gives the structure of the answer you want. I send an email. My schema asks for two fields: is spam, and a category from marketing, finance, or spam. Jev returns: - is spam: 0.90 - category: spam That is a 90% chance of spam. Jev selects the category only from the list I give it. It writes no sentences. The 0.90 is a number object, so my code can use it immediately without extra processing. Jev shows no reasoning. You get the answer and nothing more, so some people do not trust it. Use Jev for choices your code must make fast and at low cost: spam or normal, buy or no buy, reply or escalate.

How does Jev work? Jev takes two things: your input and an output schema. The schema gives the structure of the answer you want. I send an email. My schema asks for two fields: is spam, and a category from marketing, finance, or spam. Jev returns: - is spam: 0.90 - category: spam That is a 90% chance of spam. Jev selects the category only from the list I give it. It writes no sentences. The 0.90 is a number object, so my code can use it immediately without extra processing. Jev shows no reasoning. You get the answer and nothing more, so some people do not trust it. Use Jev for choices your code must make fast and at low cost: spam or normal, buy or no buy, reply or escalate.

The Startup Ideas Podcast (SIP) 🧃

12,032 次观看 • 5 天前

$jev is insane 🤯 here is jev playing smash bros against itself he is controlling all 4 different characters. and literally deciding whats the best move to play against itself all within a fraction of a second i used over 22 million tokens to play this match and it only cost me a couple of cents... jev does not replace gpt6 astra but the possibilities with its instant response time are endless$

jev is insane 🤯 here is jev playing smash bros against itself he is controlling all 4 different characters. and literally deciding whats the best move to play against itself all within a fraction of a second i used over 22 million tokens to play this match and it only cost me a couple of cents... jev does not replace gpt6 astra but the possibilities with its instant response time are endless

Mau Baron

311,292 次观看 • 6 天前

Jev has been blowing up lately. If you've got the Jev API but don't know how to play around with it yet, you can just copy this checklist. 1. jev-ultrafast A high-speed browser Agent built with Browser Use. Jev only judges "what to do, which element to click" at each step, and only calls the small model when typing is needed. Searching for a flight on Google Flights takes about 7 seconds. 2. fast-jev-compaction Context compression for Claude Code. Before each tool call, have Jev judge if there's anything still useful; delete the useless stuff, and keep the original text without rewriting it. 3. json-render Vercel Labs' generative UI framework. In experiments, Jev doesn't write JSON token by token; it just handles selecting components, properties, and layouts. 4. typesafe-mcp Best for people who just got the API. Plug Jev into Claude Code, Claude Desktop, Codex, and Pi, and do Choice / Score / Noul anytime. 5. jev-mcp Ready-made Agent judgment toolkit: fact-checking, content screening, semantic ranking, classification, and information extraction. 6. SemDecide Turn Jev into a command-line tool. Directly classify, score, and filter in the Shell—great for hooking up to crawlers, CI, and data pipelines. 7. jev-codex-router First have Jev judge how hard this round of programming tasks is, then decide the model tier, reasoning depth, and speed mode. 8. Winnow Context garbage collection for Claude Code. When Read / Bash / Grep spits out a ton of stuff, Jev first judges which parts are really relevant to the current task. 9. jev-review Before code review, run it through Jev first to pick out high-risk changes, then hand them off to a pricier big model or a human. Comes with a local dashboard. 10. Blink Use Jev as a code repository navigator. At each directory level, judge which files are most relevant to the current issue, then keep digging down. Copy these complete Jev blueprints - then read full Jev setup below ↓ ↓

Jev has been blowing up lately. If you've got the Jev API but don't know how to play around with it yet, you can just copy this checklist. 1. jev-ultrafast A high-speed browser Agent built with Browser Use. Jev only judges "what to do, which element to click" at each step, and only calls the small model when typing is needed. Searching for a flight on Google Flights takes about 7 seconds. 2. fast-jev-compaction Context compression for Claude Code. Before each tool call, have Jev judge if there's anything still useful; delete the useless stuff, and keep the original text without rewriting it. 3. json-render Vercel Labs' generative UI framework. In experiments, Jev doesn't write JSON token by token; it just handles selecting components, properties, and layouts. 4. typesafe-mcp Best for people who just got the API. Plug Jev into Claude Code, Claude Desktop, Codex, and Pi, and do Choice / Score / Noul anytime. 5. jev-mcp Ready-made Agent judgment toolkit: fact-checking, content screening, semantic ranking, classification, and information extraction. 6. SemDecide Turn Jev into a command-line tool. Directly classify, score, and filter in the Shell—great for hooking up to crawlers, CI, and data pipelines. 7. jev-codex-router First have Jev judge how hard this round of programming tasks is, then decide the model tier, reasoning depth, and speed mode. 8. Winnow Context garbage collection for Claude Code. When Read / Bash / Grep spits out a ton of stuff, Jev first judges which parts are really relevant to the current task. 9. jev-review Before code review, run it through Jev first to pick out high-risk changes, then hand them off to a pricier big model or a human. Comes with a local dashboard. 10. Blink Use Jev as a code repository navigator. At each directory level, judge which files are most relevant to the current issue, then keep digging down. Copy these complete Jev blueprints - then read full Jev setup below ↓ ↓

rody

194,422 次观看 • 3 天前

Jev is cool. So is it's OSS companion, Laya. The Latest Cool Thing In AI™ tends to get a lot of hype, sometimes without everyone even understanding it. So... what is this thing? Jev is an AI model that consumes input and produces output VERY differently than chat, claude, grok. The input is two things: 1) Text state to assess. Email, html, code, whatever. 2) A set of questions which will be asked about the attached state. The canonical example from TypeSafe's docs is to identify the urgency of a support ticket. We pass the model the customer text + a single noul question "is this urgent?". Jev returns a full set of JSON. This JSON is not generated with token-by-token autoregression. Jev is not trained to produce sequences of text tokens, rather to answer questions, and guarantees well-formed responses. In the example below, we see it produces a 0.99 probability (on a 0-1.0 scale) that the answer is "yes." Jev supports exactly three types of questions (seconds example in video): a) Noul: 0–1 probability that the answer to a yes/no question is "yes." b) Choice: Ask question with pre-defined set of answers. Jev chooses the best and assigns probabilities to each. c) Score: Ask question with pre-defined scale of answers. Jev produces a position on the scale. Jev computes answers for all questions in parallel, making responses super fast even for many questions in a single request. This might seem like a narrow set of capabilities, but in the right contexts leads to incredible potential. It also makes for a useful API / primitive for programming, since the outputs are... *ahem*... type-safe and predictable in structure. Jev is not going to replace LLMs for writing your code, auto-generating your docs, or being at the core of an agent harness. But Jev IS incredibly cool, and will be used to build a lot of amazing tech. Hope this helps.

Jev is cool. So is it's OSS companion, Laya. The Latest Cool Thing In AI™ tends to get a lot of hype, sometimes without everyone even understanding it. So... what is this thing? Jev is an AI model that consumes input and produces output VERY differently than chat, claude, grok. The input is two things: 1) Text state to assess. Email, html, code, whatever. 2) A set of questions which will be asked about the attached state. The canonical example from TypeSafe's docs is to identify the urgency of a support ticket. We pass the model the customer text + a single noul question "is this urgent?". Jev returns a full set of JSON. This JSON is not generated with token-by-token autoregression. Jev is not trained to produce sequences of text tokens, rather to answer questions, and guarantees well-formed responses. In the example below, we see it produces a 0.99 probability (on a 0-1.0 scale) that the answer is "yes." Jev supports exactly three types of questions (seconds example in video): a) Noul: 0–1 probability that the answer to a yes/no question is "yes." b) Choice: Ask question with pre-defined set of answers. Jev chooses the best and assigns probabilities to each. c) Score: Ask question with pre-defined scale of answers. Jev produces a position on the scale. Jev computes answers for all questions in parallel, making responses super fast even for many questions in a single request. This might seem like a narrow set of capabilities, but in the right contexts leads to incredible potential. It also makes for a useful API / primitive for programming, since the outputs are... ahem... type-safe and predictable in structure. Jev is not going to replace LLMs for writing your code, auto-generating your docs, or being at the core of an agent harness. But Jev IS incredibly cool, and will be used to build a lot of amazing tech. Hope this helps.

Ben Dicken

40,810 次观看 • 5 天前

TyperSafe Founder, Diogo Almeida just gave the best 2-hour breakdown on how to actually master Jev, from 0% to 100%: • 10% → 21:43 - building an eval for your own workflow with JEV • 30% → 55:49 - choice, score, noul - new types of code mapping with JEV • 55% → 1:12:36 - cascade: confident answers ship, uncertain ones go to a bigger model • 80% → 1:37:12 - JEV use cases: dark data, real-time calls, verifying every LLM in your stack • 100% → 2:11:50 - building coding agents with JEV this is worth more than another $500 course on building agents with Claude watch it today - then read the full Jev playbook below

TyperSafe Founder, Diogo Almeida just gave the best 2-hour breakdown on how to actually master Jev, from 0% to 100%: • 10% → 21:43 - building an eval for your own workflow with JEV • 30% → 55:49 - choice, score, noul - new types of code mapping with JEV • 55% → 1:12:36 - cascade: confident answers ship, uncertain ones go to a bigger model • 80% → 1:37:12 - JEV use cases: dark data, real-time calls, verifying every LLM in your stack • 100% → 2:11:50 - building coding agents with JEV this is worth more than another $500 course on building agents with Claude watch it today - then read the full Jev playbook below

Codez

74,324 次观看 • 2 天前

Jev is HERE and this is the CLEAREST explanation of what it is and what NEW businesses it unlocks. (and at the end I'll tell you how to get Jev even if you're on the waitlist) WHAT IT IS You know how you open your inbox and have to decide what's junk, what needs a reply, and what can wait? Jev does that part. It looks at each thing and says "this is junk, I'm 94% sure." It doesn't write anything back to you. It just sorts. 1,700 emails for 18 cents, instantly. That sounds kinda trivial but the important part WHAT IT UNLOCKS My explanation of Jev sounds small until you realize HOW MANY jobs are exactly this. Someone reading a stack of applications. Someone deciding which support ticket goes to which team. Someone looking at inbound and deciding who's worth calling back. A few ideas on what it unlocks: 1/ Instant quotes that are actually instant. Every quote form on the internet says "we'll email you by end of day." Build the version that answers in under a second, for roofers, movers, insurance, legal intake. 2/ Lead scoring as a product. Every agency and service business has a contact form full of junk. Score every submission and send the real ones straight to the owner's phone. 3/ Support triage for companies with no support team. The ticket gets classified and routed before anyone opens it. 4/ Clipping tools. Pass in a transcript, get the best moments scored in three seconds. Every clipping product just got a cheaper engine. 5/ Application piles. Grants, permits, insurance claims, job apps, loan docs. Someone reads that stack one item at a time today. 6/ Marketplace matching. Someone types what they need and gets matched to the right local business instantly instead of waiting for callbacks. 7/ Browser agents that actually move FAST. That makes bulk browser work practical: pulling quotes from five carriers, filing the same form for 200 clients, checking supplier inventory in real time etc. TLDR; find an expensive queue and put Jev at the front of it. HOW TO GET IT I didn't realize you can skip the waitlist because Jev is live on the Vercel AI Gateway right now, so you can start calling it today. In this episode, we share how. Episode now live on The Startup Ideas Podcast (SIP) 🧃 (thanks to vogel for coming on and spilling the sauce today) Watch: Jev is a big deal because this is a whole new way to do AI Really cool Happy Jev day.

Jev is HERE and this is the CLEAREST explanation of what it is and what NEW businesses it unlocks. (and at the end I'll tell you how to get Jev even if you're on the waitlist) WHAT IT IS You know how you open your inbox and have to decide what's junk, what needs a reply, and what can wait? Jev does that part. It looks at each thing and says "this is junk, I'm 94% sure." It doesn't write anything back to you. It just sorts. 1,700 emails for 18 cents, instantly. That sounds kinda trivial but the important part WHAT IT UNLOCKS My explanation of Jev sounds small until you realize HOW MANY jobs are exactly this. Someone reading a stack of applications. Someone deciding which support ticket goes to which team. Someone looking at inbound and deciding who's worth calling back. A few ideas on what it unlocks: 1/ Instant quotes that are actually instant. Every quote form on the internet says "we'll email you by end of day." Build the version that answers in under a second, for roofers, movers, insurance, legal intake. 2/ Lead scoring as a product. Every agency and service business has a contact form full of junk. Score every submission and send the real ones straight to the owner's phone. 3/ Support triage for companies with no support team. The ticket gets classified and routed before anyone opens it. 4/ Clipping tools. Pass in a transcript, get the best moments scored in three seconds. Every clipping product just got a cheaper engine. 5/ Application piles. Grants, permits, insurance claims, job apps, loan docs. Someone reads that stack one item at a time today. 6/ Marketplace matching. Someone types what they need and gets matched to the right local business instantly instead of waiting for callbacks. 7/ Browser agents that actually move FAST. That makes bulk browser work practical: pulling quotes from five carriers, filing the same form for 200 clients, checking supplier inventory in real time etc. TLDR; find an expensive queue and put Jev at the front of it. HOW TO GET IT I didn't realize you can skip the waitlist because Jev is live on the Vercel AI Gateway right now, so you can start calling it today. In this episode, we share how. Episode now live on The Startup Ideas Podcast (SIP) 🧃 (thanks to vogel for coming on and spilling the sauce today) Watch: Jev is a big deal because this is a whole new way to do AI Really cool Happy Jev day.

GREG ISENBERG

158,186 次观看 • 6 天前

Jev is WILD for SEO audit 🤯 in 45.1 seconds it read all 586 pages on my site and rebuilt the internal link map. 584 links placed, 139 pages it refused to link because nothing honestly fit. total cost $0.21. Claude Opus 5, same 586 pages, same clock, got through 21 of them and spent $1.43. per page that is ~190x cheaper. the full Opus pass would have run $43. internal linking is the perfect Jev job. it is not writing, it is 8,790 yes/no calls: does this page have a real reason to link to that one, and is there anchor text already sitting in the copy. that is a classification problem, and we have been paying frontier prices to do it one page at a time. what you are watching: left column is Jev, right is Opus, same queue, same rubric. the run stops the moment Jev finishes so Opus stops burning tokens. coming soon to Distribb + connector + gpt plugin

Jev is WILD for SEO audit 🤯 in 45.1 seconds it read all 586 pages on my site and rebuilt the internal link map. 584 links placed, 139 pages it refused to link because nothing honestly fit. total cost $0.21. Claude Opus 5, same 586 pages, same clock, got through 21 of them and spent $1.43. per page that is ~190x cheaper. the full Opus pass would have run $43. internal linking is the perfect Jev job. it is not writing, it is 8,790 yes/no calls: does this page have a real reason to link to that one, and is there anchor text already sitting in the copy. that is a classification problem, and we have been paying frontier prices to do it one page at a time. what you are watching: left column is Jev, right is Opus, same queue, same rubric. the run stops the moment Jev finishes so Opus stops burning tokens. coming soon to Distribb + connector + gpt plugin

borja

822,202 次观看 • 6 天前

I just built a Jev X Viral Post Analyser. 100,000 viral X posts. 20.4 seconds. $0.67. Claude Opus 5, same corpus, same clock, got through 214 posts and spent $0.98. per post that is ~680x cheaper the full Opus pass would have run $458. viral analysis is the perfect Jev job. • it is not writing, it is 14 yes/no calls per post: > does the hook open a loop, > is there a number in the first line, > is the proof real or claimed. classification, not prose. • what it found: 1,220 posts broke into the top 1%. baseline 1.22%. > superlative claim - 2.34% viral. 1.92x baseline > contrarian take - 1.59%. 1.31x > launch / tool drop - 1.46%. 1.19x and numbered lists, the thing everyone writes: 0.55%. below baseline. the most used hook is the least viral one. full stop. • what you are watching: left is the post under analysis, right is Jev answering 14 typed questions about it, each with a confidence score. the run stops at 20.4s because that is when Jev finished all 100k. pulled the corpus through a few X APIs, one parallel pass into Jev. should I drop it to public? Read my latest article on Jev Engineering below and turn your ideas into reality.

I just built a Jev X Viral Post Analyser. 100,000 viral X posts. 20.4 seconds. $0.67. Claude Opus 5, same corpus, same clock, got through 214 posts and spent $0.98. per post that is ~680x cheaper the full Opus pass would have run $458. viral analysis is the perfect Jev job. • it is not writing, it is 14 yes/no calls per post: > does the hook open a loop, > is there a number in the first line, > is the proof real or claimed. classification, not prose. • what it found: 1,220 posts broke into the top 1%. baseline 1.22%. > superlative claim - 2.34% viral. 1.92x baseline > contrarian take - 1.59%. 1.31x > launch / tool drop - 1.46%. 1.19x and numbered lists, the thing everyone writes: 0.55%. below baseline. the most used hook is the least viral one. full stop. • what you are watching: left is the post under analysis, right is Jev answering 14 typed questions about it, each with a confidence score. the run stops at 20.4s because that is when Jev finished all 100k. pulled the corpus through a few X APIs, one parallel pass into Jev. should I drop it to public? Read my latest article on Jev Engineering below and turn your ideas into reality.

Movez

78,582 次观看 • 5 天前

Jev has been exploding in popularity recently. If you already have access to the Jev API but aren’t sure how to start experimenting with it, just copy this checklist: 1. agent-desktop Desktop automation. Read the system's accessibility tree, judge which button, menu, or input field to click next. 2. typesafe-mario Have Jev play Super Mario. No screenshots—just read the structured state in the emulator's RAM, then decide to run, jump, or dodge. 3. jev-drone Use Jev to control a drone. The underlying flight control still handles stability and safety; Jev just does higher-level judgments like climbing, braking, and navigating obstacles. 4. OneVOneJev 1v1 FPS in the browser. Every decision tick, judge movement, view angle, aiming, firing, and jumping. 5. jev-trader High-frequency market making on Monad testnet. Jev judges the next buy or sell based on spreads and trade direction, with model latency around 81ms. 6. Prism Doesn't directly have Jev place orders. It judges states like toxic flow, market pressure, mean reversion, etc., then hands off to the original strategy. 7. neo4jev Stuff Jev into a knowledge graph. At each node, judge the most worthwhile edge to take next, then follow it all the way. 8. jev-curate Use Jev to screen training data. For JSONL / Parquet, first judge quality, relevance, and risk, then decide which ones go into the next training round. 9. Canny Prevents Coding Agents from stubbornly claiming they're done. Look at tool outputs, code diffs, and test results, then judge if the completion claim is reliable. 10. killmyidea Input a startup idea, and Jev scores it from multiple angles, finally giving you KILL, FIX, or SHIP. Copy these complete Jev blueprints - then read full Jev setup below ↓ ↓

Jev has been exploding in popularity recently. If you already have access to the Jev API but aren’t sure how to start experimenting with it, just copy this checklist: 1. agent-desktop Desktop automation. Read the system's accessibility tree, judge which button, menu, or input field to click next. 2. typesafe-mario Have Jev play Super Mario. No screenshots—just read the structured state in the emulator's RAM, then decide to run, jump, or dodge. 3. jev-drone Use Jev to control a drone. The underlying flight control still handles stability and safety; Jev just does higher-level judgments like climbing, braking, and navigating obstacles. 4. OneVOneJev 1v1 FPS in the browser. Every decision tick, judge movement, view angle, aiming, firing, and jumping. 5. jev-trader High-frequency market making on Monad testnet. Jev judges the next buy or sell based on spreads and trade direction, with model latency around 81ms. 6. Prism Doesn't directly have Jev place orders. It judges states like toxic flow, market pressure, mean reversion, etc., then hands off to the original strategy. 7. neo4jev Stuff Jev into a knowledge graph. At each node, judge the most worthwhile edge to take next, then follow it all the way. 8. jev-curate Use Jev to screen training data. For JSONL / Parquet, first judge quality, relevance, and risk, then decide which ones go into the next training round. 9. Canny Prevents Coding Agents from stubbornly claiming they're done. Look at tool outputs, code diffs, and test results, then judge if the completion claim is reliable. 10. killmyidea Input a startup idea, and Jev scores it from multiple angles, finally giving you KILL, FIX, or SHIP. Copy these complete Jev blueprints - then read full Jev setup below ↓ ↓

rody

314,779 次观看 • 2 天前

I gave JEV one prompt: "turn $24.80 into 1000x or I'm pulling the plug" it didn't ask questions. didn't negotiate. didn't say "that's unrealistic" it just started $24.80 to $31,847.52 overnight I woke up, opened Meridian Desk, and the number was already there. green, pulsing, real here's the part nobody talks about: I didn't mass-trade, didn't watch charts at 3am, didn't mass-subscribe to signal groups I built a terminal called Meridian Desk and let Jev run it while I slept Jev is the brain. it doesn't trade, it thinks it reads the entire market state every few seconds and outputs one structured decision: buy, copy, skip, or pass, each one tagged with a confidence score below Jev sit four agents that do the actual work: SCOUT finds fresh mints before anyone's even talking about them LEDGER tracks smart wallets and mirrors the ones with 90%+ win rates PULSE reads momentum and social sentiment in real time FLUX maps liquidity routes so every fill gets the best execution then there's WARDEN, the fifth agent, the last gate every decision Jev makes has to pass through WARDEN before a single dollar moves. it checks for honeypots, arms stop-losses, sizes the position, and vetoes anything that smells off if WARDEN says no, nothing happens. period at hour two the balance dropped to $7 Jev went quiet. stopped entering. WARDEN was blocking everything. confidence too low, liquidity too thin, signals disagreed it waited then around hour four something shifted. SCOUT flagged a mint nobody had seen yet, LEDGER confirmed three smart wallets were already in, PULSE showed social mentions climbing, FLUX found a clean route with under 2% slippage Jev lit up: BUY, conf 0.91 WARDEN cleared it. position filled in 1.6 milliseconds that was the first real trade. the balance went from $7 to $40 in minutes after that it just kept compounding. trade after trade, all night, no human input 96.4% copy accuracy. five agents running in sync. one decision engine calling the shots I got early access to JEV. that's it. manual research trying to do what Jev does in seconds? $5,000 a month minimum, and you'd still miss the window this isn't a bot that sprays trades and hopes. this is an architecture. intelligence layer on top, execution layer below, risk gate in between Jev analyzes. agents execute. WARDEN protects I haven't touched it since I hit start bookmark this. follow me if you want to see the terminal live

I gave JEV one prompt: "turn $24.80 into 1000x or I'm pulling the plug" it didn't ask questions. didn't negotiate. didn't say "that's unrealistic" it just started $24.80 to $31,847.52 overnight I woke up, opened Meridian Desk, and the number was already there. green, pulsing, real here's the part nobody talks about: I didn't mass-trade, didn't watch charts at 3am, didn't mass-subscribe to signal groups I built a terminal called Meridian Desk and let Jev run it while I slept Jev is the brain. it doesn't trade, it thinks it reads the entire market state every few seconds and outputs one structured decision: buy, copy, skip, or pass, each one tagged with a confidence score below Jev sit four agents that do the actual work: SCOUT finds fresh mints before anyone's even talking about them LEDGER tracks smart wallets and mirrors the ones with 90%+ win rates PULSE reads momentum and social sentiment in real time FLUX maps liquidity routes so every fill gets the best execution then there's WARDEN, the fifth agent, the last gate every decision Jev makes has to pass through WARDEN before a single dollar moves. it checks for honeypots, arms stop-losses, sizes the position, and vetoes anything that smells off if WARDEN says no, nothing happens. period at hour two the balance dropped to $7 Jev went quiet. stopped entering. WARDEN was blocking everything. confidence too low, liquidity too thin, signals disagreed it waited then around hour four something shifted. SCOUT flagged a mint nobody had seen yet, LEDGER confirmed three smart wallets were already in, PULSE showed social mentions climbing, FLUX found a clean route with under 2% slippage Jev lit up: BUY, conf 0.91 WARDEN cleared it. position filled in 1.6 milliseconds that was the first real trade. the balance went from $7 to $40 in minutes after that it just kept compounding. trade after trade, all night, no human input 96.4% copy accuracy. five agents running in sync. one decision engine calling the shots I got early access to JEV. that's it. manual research trying to do what Jev does in seconds? $5,000 a month minimum, and you'd still miss the window this isn't a bot that sprays trades and hopes. this is an architecture. intelligence layer on top, execution layer below, risk gate in between Jev analyzes. agents execute. WARDEN protects I haven't touched it since I hit start bookmark this. follow me if you want to see the terminal live

cristal💎

225,879 次观看 • 2 天前

Corent’s brain uses TypeSafe AI Jev now. Not to generate the output, to make the decision before the output gets generated. When a request comes into Corent, you don’t need to tell us which model to use. You send the prompt, the workload and the quality level. Then Jev helps us decide what that request actually needs, how confident we are in that decision, and whether we should take the route or fall back to something safer. That matters because every request has different economics. A 2¢ image can tolerate more uncertainty. A $2 video clip cannot. Across 1000+ models, this changes how we route. We can set different confidence requirements depending on the workload, the cost and the quality expected. If the confidence is too low, we stop guessing. Routing was never really a text problem. It was a decision problem. Diogo Almeida and the team did a wonderful job with JEV Get your key at

Corent’s brain uses TypeSafe AI Jev now. Not to generate the output, to make the decision before the output gets generated. When a request comes into Corent, you don’t need to tell us which model to use. You send the prompt, the workload and the quality level. Then Jev helps us decide what that request actually needs, how confident we are in that decision, and whether we should take the route or fall back to something safer. That matters because every request has different economics. A 2¢ image can tolerate more uncertainty. A $2 video clip cannot. Across 1000+ models, this changes how we route. We can set different confidence requirements depending on the workload, the cost and the quality expected. If the confidence is too low, we stop guessing. Routing was never really a text problem. It was a decision problem. Diogo Almeida and the team did a wonderful job with JEV Get your key at

corent

109,541 次观看 • 6 天前

I gave Jev 3,282 of my X posts across 100M views and asked it to find what actually works for growth. 4,252,330 tokens $0.1282 for the full 8m 34s run! Each post got 8 questions about the topic, hook, tone, whether it teaches something, etc. How-to posts got 150 median likes vs the average median of 44. AI and coding was a 1.9x multiplier topic compared and SEO, despite recent posts, was right at base median 1.0x - surprisingly. The recommended topic + angle + voice formula was: AI coding + teach something + provocative

I gave Jev 3,282 of my X posts across 100M views and asked it to find what actually works for growth. 4,252,330 tokens $0.1282 for the full 8m 34s run! Each post got 8 questions about the topic, hook, tone, whether it teaches something, etc. How-to posts got 150 median likes vs the average median of 44. AI and coding was a 1.9x multiplier topic compared and SEO, despite recent posts, was right at base median 1.0x - surprisingly. The recommended topic + angle + voice formula was: AI coding + teach something + provocative

Ian Nuttall

86,917 次观看 • 7 天前

If you are confused about why 𝗝𝗲𝘃 is being called the "Internet" moment for the AI industry. This is 100% worth your time. In fact, you should watch it: It tells LLMs what to do next, in milliseconds & at almost zero cost. If you set it up correctly, you will have the AI engineer’s setup for 2028. How to set up & use Jev (to actually get the 100x): 1. Join the waitlist; it's fairly quick: typesafe .ai. 2. Then go to Claude Code or Codex. 3. Choose Opus 5-Low or Sol-Low. 4. Copy and paste this prompt: "[claude or codex] plugin marketplace add typesafe-ai/skills [claude or codex] plugin install typesafe@typesafe-ai" 5. When you type /typesafe, the skill shows up. 6. Paste your API key once and click "Allow" 7. Start with $5 in free credit. It's hard to spend more. ----- Now, here are the 3 ways to actually use Jev: 1. Jev for Linkedin I have 38,000 connections & invitations on LinkedIn. I have a new company to launch. I need to find a couple of hundred people to message. to do while saving time: > Export your LinkedIn connections and invitations. > Connect Claude to GitHub, Vercel & Apify. > Create an Apify API key to enrich your data. > Go to LinkedIn Settings → Data privacy. > Get a copy. LinkedIn will email you a ZIP file. > Open the file & find the Connections CSVs. > Upload the files to Jev. > Use Jev to classify your contacts. > Review the shortlist. 2. Jev for Gmail To go through all of my Gmail contacts and email the right people. > Go to Google Contacts. Open Other contacts. > Select all contacts. Export them. > Upload the file to Claude Code or Codex. > Use Jev to sort them into: Keep, Review, Remove and Review everything before removing anything. 3. You got lost in Claude Code, GitHub, Vercel, Apify, Jev, Typesafe. I feel you. It is overwhelming. That’s why I included the entire copy-and-paste prompt for each use case in the newsletter: A 45-second TL;DR by Matija Sosic.

If you are confused about why 𝗝𝗲𝘃 is being called the "Internet" moment for the AI industry. This is 100% worth your time. In fact, you should watch it: It tells LLMs what to do next, in milliseconds & at almost zero cost. If you set it up correctly, you will have the AI engineer’s setup for 2028. How to set up & use Jev (to actually get the 100x): 1. Join the waitlist; it's fairly quick: typesafe .ai. 2. Then go to Claude Code or Codex. 3. Choose Opus 5-Low or Sol-Low. 4. Copy and paste this prompt: "[claude or codex] plugin marketplace add typesafe-ai/skills [claude or codex] plugin install typesafe@typesafe-ai" 5. When you type /typesafe, the skill shows up. 6. Paste your API key once and click "Allow" 7. Start with $5 in free credit. It's hard to spend more. ----- Now, here are the 3 ways to actually use Jev: 1. Jev for Linkedin I have 38,000 connections & invitations on LinkedIn. I have a new company to launch. I need to find a couple of hundred people to message. to do while saving time: > Export your LinkedIn connections and invitations. > Connect Claude to GitHub, Vercel & Apify. > Create an Apify API key to enrich your data. > Go to LinkedIn Settings → Data privacy. > Get a copy. LinkedIn will email you a ZIP file. > Open the file & find the Connections CSVs. > Upload the files to Jev. > Use Jev to classify your contacts. > Review the shortlist. 2. Jev for Gmail To go through all of my Gmail contacts and email the right people. > Go to Google Contacts. Open Other contacts. > Select all contacts. Export them. > Upload the file to Claude Code or Codex. > Use Jev to sort them into: Keep, Review, Remove and Review everything before removing anything. 3. You got lost in Claude Code, GitHub, Vercel, Apify, Jev, Typesafe. I feel you. It is overwhelming. That’s why I included the entire copy-and-paste prompt for each use case in the newsletter: A 45-second TL;DR by Matija Sosic.

Ruben Hassid

167,306 次观看 • 3 天前

you can make any open source model behave like jev with just a bit of inference engineering. it's shockingly easy. to prove it, we built a new endpoint we're calling deepseek-v4.1-flash-jev. see the demo below. here's how it's done: sglang (an inference engine) offers a scoring endpoint in addition to the normal generation one. in scoring mode, given an input & set of possible answers, it forces the model to produce probabilities for each one. example: > input: what is most common letter in abcccde? > possible answers: a, b, c > output: (c, 0.9), (b, 0.0.5), (a, 0.05) getting the above behavior instead of streamed output is as simple as using sglang's /v1/score endpoint instead of /generate. there's just one other trick required. for deepseek, you have to add a closing think tag before the response. this forces a direct answer instead of a reasoning trace. if you want reasoning, you can do that too, but imo that makes things too slow to be worth it. dsv4.1 flash is not as good as jev, but if we had enough spare compute to experiment with this same approach for a larger model then i think the decision quality would be at least as good, if not better. also, somewhat unrelated, i think decision-making models kill all prospecting & sourcing work. i would have absolutely killed to have jev or similar when i was recruiting Mintlify. absolutely incredible.

you can make any open source model behave like jev with just a bit of inference engineering. it's shockingly easy. to prove it, we built a new endpoint we're calling deepseek-v4.1-flash-jev. see the demo below. here's how it's done: sglang (an inference engine) offers a scoring endpoint in addition to the normal generation one. in scoring mode, given an input & set of possible answers, it forces the model to produce probabilities for each one. example: > input: what is most common letter in abcccde? > possible answers: a, b, c > output: (c, 0.9), (b, 0.0.5), (a, 0.05) getting the above behavior instead of streamed output is as simple as using sglang's /v1/score endpoint instead of /generate. there's just one other trick required. for deepseek, you have to add a closing think tag before the response. this forces a direct answer instead of a reasoning trace. if you want reasoning, you can do that too, but imo that makes things too slow to be worth it. dsv4.1 flash is not as good as jev, but if we had enough spare compute to experiment with this same approach for a larger model then i think the decision quality would be at least as good, if not better. also, somewhat unrelated, i think decision-making models kill all prospecting & sourcing work. i would have absolutely killed to have jev or similar when i was recruiting Mintlify. absolutely incredible.

Nick Khami

102,542 次观看 • 5 天前

Another insane Jev use case! Jev is making it dramatically cheaper to evaluate what actually happened inside an agent run. And finally, someone open-sourced a self-improving memory layer that can put that signal to work across agent harnesses: - Claude Code - Codex - Cursor - OpenCode, and 20+ more Beacon by Asymptote Labs continuously captures your agent history across harnesses and uses Jev to identify which runs are actually worth learning from. It then turns the highest-signal workflows, corrections, and debugging patterns into reusable skills. GitHub repo: (don’t forget to star it ⭐ ) Beacon preserves the complete session history. But preserving a run and learning from it are two different things. Most coding-agent sessions contain routine exploration, failed commands, and fixes that only apply to one task. The trace can remain available for inspection without turning every detail into guidance for future agents. Jev scores each run for evidence, reuse potential, and human correction signals. An application policy then decides whether to promote, review, or discard it. The recording shows this in action. Claude receives a coding task, modifies the implementation, and runs the tests. I then provide an edge-case correction, so Claude updates the code and adds regression coverage. Beacon automatically captures the complete session. Jev evaluates whether the correction contains a reusable engineering lesson. Once approved, that lesson becomes available to other coding agents working on the project. Since it works across harnesses: - Claude Code sessions can teach Codex. - Cursor debugging can improve OpenCode. So a problem solved by one agent should not need to be learned from scratch by another. If you want to dive deeper into Jev, I also wrote a hands-on guide to building this Jev-style decision path with open models, entirely locally. Read it below.

Another insane Jev use case! Jev is making it dramatically cheaper to evaluate what actually happened inside an agent run. And finally, someone open-sourced a self-improving memory layer that can put that signal to work across agent harnesses: - Claude Code - Codex - Cursor - OpenCode, and 20+ more Beacon by Asymptote Labs continuously captures your agent history across harnesses and uses Jev to identify which runs are actually worth learning from. It then turns the highest-signal workflows, corrections, and debugging patterns into reusable skills. GitHub repo: (don’t forget to star it ⭐ ) Beacon preserves the complete session history. But preserving a run and learning from it are two different things. Most coding-agent sessions contain routine exploration, failed commands, and fixes that only apply to one task. The trace can remain available for inspection without turning every detail into guidance for future agents. Jev scores each run for evidence, reuse potential, and human correction signals. An application policy then decides whether to promote, review, or discard it. The recording shows this in action. Claude receives a coding task, modifies the implementation, and runs the tests. I then provide an edge-case correction, so Claude updates the code and adds regression coverage. Beacon automatically captures the complete session. Jev evaluates whether the correction contains a reusable engineering lesson. Once approved, that lesson becomes available to other coding agents working on the project. Since it works across harnesses: - Claude Code sessions can teach Codex. - Cursor debugging can improve OpenCode. So a problem solved by one agent should not need to be learned from scratch by another. If you want to dive deeper into Jev, I also wrote a hands-on guide to building this Jev-style decision path with open models, entirely locally. Read it below.

Avi Chawla

279,042 次观看 • 3 天前

fun weekend project: AutoJev. i was curious to see if i could train a competitive Jev-like model completely autonomously with a swarm of agents using our internal system. turns out you can get quite far! some details: - gave the swarm a devbox with an h200 gpu - the swarm is a mix of astra and fable; used sol and luna for synthetic data and filtering; ran for 20 hours - spent $3.1k in total ($1.9k on agents, $1.2k on data) - used qwen3.8-27b as the backbone. it underperforms Jev initially, but after training it is competitive/better, and it also supports 260k context and multimodal input - the agents tried RL, but it hasn't worked out so far, so they fell back to SFT on high-quality synthetic data - both accuracy and calibration are better - jev-compatible api, playground, and inference. on an h200 it gets around 120ms p95. that will be higher under contention, but still quite fast for an unoptimized version code: model: going to let it run longer, and will also bring up inference so folks can try it out.

fun weekend project: AutoJev. i was curious to see if i could train a competitive Jev-like model completely autonomously with a swarm of agents using our internal system. turns out you can get quite far! some details: - gave the swarm a devbox with an h200 gpu - the swarm is a mix of astra and fable; used sol and luna for synthetic data and filtering; ran for 20 hours - spent $3.1k in total ($1.9k on agents, $1.2k on data) - used qwen3.8-27b as the backbone. it underperforms Jev initially, but after training it is competitive/better, and it also supports 260k context and multimodal input - the agents tried RL, but it hasn't worked out so far, so they fell back to SFT on high-quality synthetic data - both accuracy and calibration are better - jev-compatible api, playground, and inference. on an h200 it gets around 120ms p95. that will be higher under contention, but still quite fast for an unoptimized version code: model: going to let it run longer, and will also bring up inference so folks can try it out.

Denis Yarats

25,932 次观看 • 2 天前

I GAVE MY SIX GROK BOTS A NEW F*CKING BRAIN FOR $0.04 AND WENT TO SLEEP, $1,000 BECAME $3,833.92 day 1 of the new run. same bots, same bank, one thing changed i plugged in Jev Jev takes a pile and hands back a verdict. that is all it does, and it does it in 0.1 seconds the guys selling signals pay $200 a month for a model that chews on one question for six seconds Jev costs four cents per million words you feed it. the answer side is free so i stopped asking about a single coin. i handed it the whole market $1,000 → $1,153.54 → $1,028.02 → $1,611.60 → $3,386.65 → $3,833.92 → 14:01 Jev read 107 live tickers, killed 102, kept one → 15:35 opening buy on the survivor, +$153.54 → 18:12 got it wrong, sold while it was still falling, -$125.52 → 21:20 waited for the panic sell, bought into it, +$583.58 → 03:15 the big one, held it 2 hours 15 minutes, +$1,775.05 → 06:30 flat, and the coin itself only did +127% six checks on each ticker. liquidity, which means can i sell it back, plus holders, volume, rug risk, fresh wallets and entry window 102 of them failed at least one. that filter is the whole edge this holds far outside crypto a slow brain makes you choose what to open. a fast one lets you scan the pile that is your inbox. your job hunt. every tab you left open at 2am best setup i have run, and nowhere near its ceiling. day 2 starts tonight want to copy it? fund the balance before you start. an empty wallet means the bots just watch platform link below in the replies, no fee to join want the full guide, every prompt and each place it breaks? say so and i will write it you know one person still paying monthly for the slow version. send this before they renew bookmark this, the feed eats posts like mine by morning. what would you scan first if checking were free?

I GAVE MY SIX GROK BOTS A NEW F*CKING BRAIN FOR $0.04 AND WENT TO SLEEP, $1,000 BECAME $3,833.92 day 1 of the new run. same bots, same bank, one thing changed i plugged in Jev Jev takes a pile and hands back a verdict. that is all it does, and it does it in 0.1 seconds the guys selling signals pay $200 a month for a model that chews on one question for six seconds Jev costs four cents per million words you feed it. the answer side is free so i stopped asking about a single coin. i handed it the whole market $1,000 → $1,153.54 → $1,028.02 → $1,611.60 → $3,386.65 → $3,833.92 → 14:01 Jev read 107 live tickers, killed 102, kept one → 15:35 opening buy on the survivor, +$153.54 → 18:12 got it wrong, sold while it was still falling, -$125.52 → 21:20 waited for the panic sell, bought into it, +$583.58 → 03:15 the big one, held it 2 hours 15 minutes, +$1,775.05 → 06:30 flat, and the coin itself only did +127% six checks on each ticker. liquidity, which means can i sell it back, plus holders, volume, rug risk, fresh wallets and entry window 102 of them failed at least one. that filter is the whole edge this holds far outside crypto a slow brain makes you choose what to open. a fast one lets you scan the pile that is your inbox. your job hunt. every tab you left open at 2am best setup i have run, and nowhere near its ceiling. day 2 starts tonight want to copy it? fund the balance before you start. an empty wallet means the bots just watch platform link below in the replies, no fee to join want the full guide, every prompt and each place it breaks? say so and i will write it you know one person still paying monthly for the slow version. send this before they renew bookmark this, the feed eats posts like mine by morning. what would you scan first if checking were free?

savip.

21,055 次观看 • 2 天前

i gave five Grok Bots their own inboxes and told them to find businesses that need AI implemented 6 hours later they had emailed 140 companies, and 27 replied - into the bots' inboxes, not mine ( each business pays between $500 and $8,500. so far my agents have earned ~$27,410 ) not a scraper. not a mail blast. five agents on a cloud computer that never sleeps, each with one narrow job and its own address here is what happened while i slept > bot 1 pulled 468 local businesses and cut 69% on a single rule: is there a gap here i can actually close in a week > bot 2 went through the survivors and wrote down the evidence - the site from 2014, the unanswered reviews, the booking form that 404s > bot 3 built the artifact so the email would not be empty: a one-page audit with the screenshots inside > bot 4 wrote and sent from its own inbox, then ran the thread itself when the reply came back > bot 5 tried to kill every send the other four approved. its only job was to ask: would this email annoy me if i got it out of 468 businesses, 146 passed the filter and 140 went out 27 replied. 23 asked for a call. the whole run cost ~$12 of those 23 i have onboarded 11 so far. each business pays between $500 and $8,500, which is ~$27,410 to date the other 12 are still in progress. if they close the same way it lands around $52,000 - but that is a projection, not a fact the part that only works here: the reply drops into bot 4's inbox. i was not in the second email. or the third. in the morning i read the thread like a manager, not like the person who sent it what the bots never touched: > my own mailbox. they have theirs, i have mine > sending without the artifact. no audit, no email > anyone bot 5 flagged. it killed 6 drafts out of the 146 that passed, and i did not overrule it the honest part: this is the first run. one city, one niche, six hours. eleven clients out of twenty-three is not an average yet, it is a start setup took one evening: create the bots, connect AgentMail so each gets an inbox, write five charters, put the scan on a schedule no VPS. no scraper farm. no mail-merge what's left is finding the ceiling: 140 emails went out overnight. will 1,000?

i gave five Grok Bots their own inboxes and told them to find businesses that need AI implemented 6 hours later they had emailed 140 companies, and 27 replied - into the bots' inboxes, not mine ( each business pays between $500 and $8,500. so far my agents have earned ~$27,410 ) not a scraper. not a mail blast. five agents on a cloud computer that never sleeps, each with one narrow job and its own address here is what happened while i slept > bot 1 pulled 468 local businesses and cut 69% on a single rule: is there a gap here i can actually close in a week > bot 2 went through the survivors and wrote down the evidence - the site from 2014, the unanswered reviews, the booking form that 404s > bot 3 built the artifact so the email would not be empty: a one-page audit with the screenshots inside > bot 4 wrote and sent from its own inbox, then ran the thread itself when the reply came back > bot 5 tried to kill every send the other four approved. its only job was to ask: would this email annoy me if i got it out of 468 businesses, 146 passed the filter and 140 went out 27 replied. 23 asked for a call. the whole run cost ~$12 of those 23 i have onboarded 11 so far. each business pays between $500 and $8,500, which is ~$27,410 to date the other 12 are still in progress. if they close the same way it lands around $52,000 - but that is a projection, not a fact the part that only works here: the reply drops into bot 4's inbox. i was not in the second email. or the third. in the morning i read the thread like a manager, not like the person who sent it what the bots never touched: > my own mailbox. they have theirs, i have mine > sending without the artifact. no audit, no email > anyone bot 5 flagged. it killed 6 drafts out of the 146 that passed, and i did not overrule it the honest part: this is the first run. one city, one niche, six hours. eleven clients out of twenty-three is not an average yet, it is a start setup took one evening: create the bots, connect AgentMail so each gets an inbox, write five charters, put the scan on a schedule no VPS. no scraper farm. no mail-merge what's left is finding the ceiling: 140 emails went out overnight. will 1,000?

Archive

110,394 次观看 • 27 天前

Jev builds the MOST POWERFUL trading agents and someone JUST open sourced jev-trader, a fully working 24/7 trading bot with Jev along with COMPLETE low latency CODEBASE WHAT THIS MEANS FOR YOU - you no longer have to build a trading bot with Jev from scratch, you just clone this and make it yours here is how you make your own Jev trading bot with this repo: 1. clone it and run three commands, it boots straight into dry run mode with real book data, real decisions, and simulated fills so you can watch it think with zero capital 2. drop in your Jev API key and the model starts answering buy or sell on every block with calibrated probabilities in 81 milliseconds 3. swap the book reader for your own venue, the model interface is clean so any order book that returns bids and asks plugs straight in 4. tune the decision cadence and horizon, ask the model every N blocks about the move over the next M, so you control how aggressive the engine trades 5. the hot loop already fits one block with exactly two round trips, one to read the book, one to send the order, nothing else on the path, this is the institutional latency discipline most retail bots never reach 6. plug in the live server and every block, every decision, every fill streams to a public dashboard so you watch your engine run the whole point is this repo hands you HARDEST part for FREE - > the low latency engine the COMPLETE breakdown of how i turned this into hedge fund grade HFT trading system is in my article below:

Jev builds the MOST POWERFUL trading agents and someone JUST open sourced jev-trader, a fully working 24/7 trading bot with Jev along with COMPLETE low latency CODEBASE WHAT THIS MEANS FOR YOU - you no longer have to build a trading bot with Jev from scratch, you just clone this and make it yours here is how you make your own Jev trading bot with this repo: 1. clone it and run three commands, it boots straight into dry run mode with real book data, real decisions, and simulated fills so you can watch it think with zero capital 2. drop in your Jev API key and the model starts answering buy or sell on every block with calibrated probabilities in 81 milliseconds 3. swap the book reader for your own venue, the model interface is clean so any order book that returns bids and asks plugs straight in 4. tune the decision cadence and horizon, ask the model every N blocks about the move over the next M, so you control how aggressive the engine trades 5. the hot loop already fits one block with exactly two round trips, one to read the book, one to send the order, nothing else on the path, this is the institutional latency discipline most retail bots never reach 6. plug in the live server and every block, every decision, every fill streams to a public dashboard so you watch your engine run the whole point is this repo hands you HARDEST part for FREE - > the low latency engine the COMPLETE breakdown of how i turned this into hedge fund grade HFT trading system is in my article below:

Roan

119,605 次观看 • 4 天前

How Health New Zealand (Te Whatu Ora) Buried Whistleblower Barry Young's Protected Disclosure. Barry Young details how he made a protected disclosure to Health New Zealand’s executive leadership team with statistical evidence suggesting serious vaccine safety issues. After extensive review with epidemiologists, doctors, and statisticians, he calculated odds of 100 billion to one against the vaccine not causing the observed signals. The handling of his Protected Disclosure reveals suppression of evidence, which would be potentially serious illegality, at the highest levels of the Ministry of Health. Barry had to raise several OIA (Official Information Act) requests to obtain the evidence that Health New Zealand had indeed received his original Protected Disclosure email, despite the evidence being "buried away in an Accenture Report, which was a Forensics Report." This is essential viewing for anyone who has concerns about government transparency, public health accountability, and Whistleblower Protections in New Zealand and beyond. Transcript: "I gave it to Health New Zealand, that was my protected disclosure... And only after doing a lot of due diligence with a lot of experts and statisticians and doctors who looked at it and I found out in hindsight I'm perfectly allowed to do that under the act to see how and whether that's important, whether to make a protected disclosure. It was all... red flag, red flag, red flag. So yes, I did put all that together, I did some crude analysis back then, getting a lot better at it now. And I just came up with some numbers that was 100 billion to one against the vaccine not causing this. I can't say for sure, I can never say that. And I sent that in an email to the executive leadership team at Health New Zealand. So of course, yeah, yeah, to make them aware of what I was saying and that formed the protected disclosure which was the whole purpose of the act, which is why we're here. Of course, they just ignored that and retaliated. In the police disclosures, I didn't even see a sign of that original email that I sent, they tried to bury it, they tried to withhold it from evidence because it was a protected disclosure. The original ELT email, the only one they did provide as evidence was the email I sent to the MPs, not knowing that that wasn't a protected disclosure. I didn't know the act at the time, but they withheld the one I sent to the executive leadership team. And the only reason that I can think of they did that was to try and avoid saying that it was a protected disclosure. They tried to bury it. I... emailed them, the Crown, the police, where's the email that I sent to the executive team? Oh no, we've sent you everything that we have. So I thought, that's a bit strange. I did send an email. ... I had to resort to writing OIA's to Health New Zealand, which they denied. They said, oh no, we didn't, there's no email sent from you at that time to these people. Your request is denied because it doesn't exist. And I wrote back to them. I said, check again, please. These are the times. These are the dates. And they said, we've gone back and we've done a thorough check and we stand by original decision. The email doesn't exist. So Health New Zealand said twice that email doesn't exist. I found it. The evidence buried away in an Accenture report, which was a forensics report. I said, hang on a minute. There's the email there in that report. Only after that did the police and the Crown reply to me. And lo and behold, there it was. The protected disclosure email... produced nearly a year after I was charged. It should have been the very first thing that they sent and [that] they dealt with. ...Looking at a protected disclosure, the way it's meant to be, they're meant to receive it and acknowledge it and reply to it. They tried to bury it."

How Health New Zealand (Te Whatu Ora) Buried Whistleblower Barry Young's Protected Disclosure. Barry Young details how he made a protected disclosure to Health New Zealand’s executive leadership team with statistical evidence suggesting serious vaccine safety issues. After extensive review with epidemiologists, doctors, and statisticians, he calculated odds of 100 billion to one against the vaccine not causing the observed signals. The handling of his Protected Disclosure reveals suppression of evidence, which would be potentially serious illegality, at the highest levels of the Ministry of Health. Barry had to raise several OIA (Official Information Act) requests to obtain the evidence that Health New Zealand had indeed received his original Protected Disclosure email, despite the evidence being "buried away in an Accenture Report, which was a Forensics Report." This is essential viewing for anyone who has concerns about government transparency, public health accountability, and Whistleblower Protections in New Zealand and beyond. Transcript: "I gave it to Health New Zealand, that was my protected disclosure... And only after doing a lot of due diligence with a lot of experts and statisticians and doctors who looked at it and I found out in hindsight I'm perfectly allowed to do that under the act to see how and whether that's important, whether to make a protected disclosure. It was all... red flag, red flag, red flag. So yes, I did put all that together, I did some crude analysis back then, getting a lot better at it now. And I just came up with some numbers that was 100 billion to one against the vaccine not causing this. I can't say for sure, I can never say that. And I sent that in an email to the executive leadership team at Health New Zealand. So of course, yeah, yeah, to make them aware of what I was saying and that formed the protected disclosure which was the whole purpose of the act, which is why we're here. Of course, they just ignored that and retaliated. In the police disclosures, I didn't even see a sign of that original email that I sent, they tried to bury it, they tried to withhold it from evidence because it was a protected disclosure. The original ELT email, the only one they did provide as evidence was the email I sent to the MPs, not knowing that that wasn't a protected disclosure. I didn't know the act at the time, but they withheld the one I sent to the executive leadership team. And the only reason that I can think of they did that was to try and avoid saying that it was a protected disclosure. They tried to bury it. I... emailed them, the Crown, the police, where's the email that I sent to the executive team? Oh no, we've sent you everything that we have. So I thought, that's a bit strange. I did send an email. ... I had to resort to writing OIA's to Health New Zealand, which they denied. They said, oh no, we didn't, there's no email sent from you at that time to these people. Your request is denied because it doesn't exist. And I wrote back to them. I said, check again, please. These are the times. These are the dates. And they said, we've gone back and we've done a thorough check and we stand by original decision. The email doesn't exist. So Health New Zealand said twice that email doesn't exist. I found it. The evidence buried away in an Accenture report, which was a forensics report. I said, hang on a minute. There's the email there in that report. Only after that did the police and the Crown reply to me. And lo and behold, there it was. The protected disclosure email... produced nearly a year after I was charged. It should have been the very first thing that they sent and [that] they dealt with. ...Looking at a protected disclosure, the way it's meant to be, they're meant to receive it and acknowledge it and reply to it. They tried to bury it."

Liz Gunn

12,711 次观看 • 2 个月前