Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

Jev + SERV is actually insane. We already showed you can increase Jev's performance with SERV Reasoning. Now we're taking it further, bringing Jev-powered Decision nodes into Graph Sharding with the upcoming SERV v3. Here's a breakdown of how it works: Jev is a decision-making model. Given a task... and a set of options, it predicts which path is more likely. Think of the octopus that predicted World Cup results. Jev does that for your business, except it's not luck. It weighs every option and tells you how sure it is. It does this by assigning probabilities to outcomes. It doesn't generate text on its own, so you can't expect it to create a new outcome for you. But that's also what enables it to be lightning fast and dirt cheap. For example, in customer service you can ask Jev how to triage an incoming query and route it to the correct department. It can only select from the list of departments you provide it. This also means it can't hallucinate a new outcome outside the options it's given, which makes it incredibly interesting for OpenServ. In Graph Sharding, we take a single system prompt and break it down into multiple LLM steps with deterministic input and output shapes. Some of these steps require an LLM to produce new output, while others are simply decision routers that determine the next possible path. Traditionally, LLMs are slow and expensive. Breaking a single prompt into multiple steps increases accuracy and reliability by a ton, but it also introduces latency. Jev takes on those decision nodes, which are the backbone of a business process and therefore SERV graphs, and makes them super consistent and lightning fast, lowering the overall cost and latency of graph execution. SERV Reasoning on its own is a great force multiplier for Jev because, like all other models, it works by interpreting input instructions. The clearer those instructions are, the better the model performs. That's where SERV Reasoning comes into play. Just like amplifying any other model, we also amplify the accuracy and consistency of Jev's responses. And now we're bringing Jev-powered Decision nodes into Graph Sharding with SERV v3.show more

Armagan Amcalar

9,164 subscribers

365,108 Aufrufe • vor 5 Tagen •via X (Twitter)

Bildung Gesundheit & Wellness Wissenschaft & Technologie

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

You've probably scrolled past a dozen posts about Jev this week without anyone telling you what it actually is. It's the first model from TypeSafe, a lab started by one of the researchers behind ChatGPT. It's a decision engine: you give it options, it picks one and tells you how sure it is. It cannot write a single word, and that is the interesting part. Every other AI you use writes. That is the whole interface. So when software needs a plain yes or no, we make a model write a paragraph and then dig the answer back out of it. Fine in a chat window where a human reads it. Bad inside software, where code has to act on it. The bet is that the valuable half was never the writing. It was the deciding. That problem showed up in WordPress years ago, and it is the reason WPVibe works the way it does. The AI does the work. Anything permanent stops and waits, because a delete that skips the trash is not something software should decide on its own.

You've probably scrolled past a dozen posts about Jev this week without anyone telling you what it actually is. It's the first model from TypeSafe, a lab started by one of the researchers behind ChatGPT. It's a decision engine: you give it options, it picks one and tells you how sure it is. It cannot write a single word, and that is the interesting part. Every other AI you use writes. That is the whole interface. So when software needs a plain yes or no, we make a model write a paragraph and then dig the answer back out of it. Fine in a chat window where a human reads it. Bad inside software, where code has to act on it. The bet is that the valuable half was never the writing. It was the deciding. That problem showed up in WordPress years ago, and it is the reason WPVibe works the way it does. The AI does the work. Anything permanent stops and waits, because a delete that skips the trash is not something software should decide on its own.

John Turner

21,029 Aufrufe • vor 11 Tagen

$here's how to make money with jev on autopilot it's a super fast decision model, so it picks an answer in a fifth of a second and tells you how sure it is - put instant pricing on a business that has none - sell the same thing to bigger businesses for more - sell a file that decides what an agent may do - charge monthly to keep all of it running - costs a fraction of a cent per decision - runs on hermes or grok bot, on a schedule just wrote a whole guide on how you can set this up:$

here's how to make money with jev on autopilot it's a super fast decision model, so it picks an answer in a fifth of a second and tells you how sure it is - put instant pricing on a business that has none - sell the same thing to bigger businesses for more - sell a file that decides what an agent may do - charge monthly to keep all of it running - costs a fraction of a cent per decision - runs on hermes or grok bot, on a schedule just wrote a whole guide on how you can set this up:

Chris

90,674 Aufrufe • vor 8 Tagen

You can now use Jev right inside Claude Code 🤯 It's called jev-model-router, an early access mod built on Claude Code's new function hooks. Before every turn, it checks in with Jev and asks: > how mechanical the task is > how much reasoning it needs > whether it's risky Then it routes: → it'll move up to a stronger model on weak evidence, and only drops to a cheaper one when it's confident the task is simple → every decision gets logged in your transcript → if the call fails, your request runs untouched Setup: 1. copy the install command: npx claude-code-templates@latest --mod productivity/jev-model-router 2. paste it inside Claude Code 3. run claude with CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 set 4. accept the trust prompt on first launch Link: Also works with no api key, it just falls back to a built-in classifier with no confidence score. For real jev routing, add your typesafeApiKey or gatewayApiKey to ~/.claude/settings.json. Follow me for more AI workflows and tutorials.

You can now use Jev right inside Claude Code 🤯 It's called jev-model-router, an early access mod built on Claude Code's new function hooks. Before every turn, it checks in with Jev and asks: > how mechanical the task is > how much reasoning it needs > whether it's risky Then it routes: → it'll move up to a stronger model on weak evidence, and only drops to a cheaper one when it's confident the task is simple → every decision gets logged in your transcript → if the call fails, your request runs untouched Setup: 1. copy the install command: npx claude-code-templates@latest --mod productivity/jev-model-router 2. paste it inside Claude Code 3. run claude with CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 set 4. accept the trust prompt on first launch Link: Also works with no api key, it just falls back to a built-in classifier with no confidence score. For real jev routing, add your typesafeApiKey or gatewayApiKey to ~/.claude/settings.json. Follow me for more AI workflows and tutorials.

Alvaro Cintas

41,891 Aufrufe • vor 7 Tagen

Found a great production use case for Jev. I used Jev to organize ~2.3K AI research papers. The total cost was $0.14, and it took about 83 seconds. The process: The papers already had old tags, which I ran through a previous open model (DeepSeek V4 Flash). However, I wasn't confident in the classifications, and I didn't want to spend more on tokens unless I spent time tuning it into a good LLM classifier via few-shot (more expensive). Too tedious, too costly, and unsustainable. Luckily for us, we now have Jev to help us with organizing papers better. So Jev first went through all the papers and retagged them. It agreed with 75% of the previous tags. Jev found about 579 high-confidence topic changes. I evaluated reliability by manually labeling 30 disagreements and accepted all of them. I was astonished by Jev's classification capabilities. We applied and verified all changes in production. I'm much more satisfied with the classifications, but I think there is still room for improvement. Check out the papers here: I will experiment with Jev more. The takeaway is that pipelines can be significantly improved by carefully combining System One and System Two models. Jev clearly unlocks more interesting ways to organize papers and offer a more useful discovery layer for research papers. More updates on that soon.

Found a great production use case for Jev. I used Jev to organize ~2.3K AI research papers. The total cost was $0.14, and it took about 83 seconds. The process: The papers already had old tags, which I ran through a previous open model (DeepSeek V4 Flash). However, I wasn't confident in the classifications, and I didn't want to spend more on tokens unless I spent time tuning it into a good LLM classifier via few-shot (more expensive). Too tedious, too costly, and unsustainable. Luckily for us, we now have Jev to help us with organizing papers better. So Jev first went through all the papers and retagged them. It agreed with 75% of the previous tags. Jev found about 579 high-confidence topic changes. I evaluated reliability by manually labeling 30 disagreements and accepted all of them. I was astonished by Jev's classification capabilities. We applied and verified all changes in production. I'm much more satisfied with the classifications, but I think there is still room for improvement. Check out the papers here: I will experiment with Jev more. The takeaway is that pipelines can be significantly improved by carefully combining System One and System Two models. Jev clearly unlocks more interesting ways to organize papers and offer a more useful discovery layer for research papers. More updates on that soon.

elvis

15,427 Aufrufe • vor 7 Tagen

JEV is INSANE. We gave it 400 companies and one candidate profile. In 12 seconds, it predicted which jobs the candidate had the highest chance of getting, assigned a confidence score and detected job-candidate mismatches. All for just $0.0005 It can also score companies, analyse your experience, match you with the right roles and identify the opportunities you’re most likely to get based on your profile. Coming soon to Backdoor Comment “JEV” for early access.

Sarvagya Kulshreshtha

150,493 Aufrufe • vor 10 Tagen

Alright, now that we know *what* an agent is, how does it actually work? When you ask for help on a task, the agent plans a series of steps and executes them directly in the application on your behalf, using the tools it has access to. Say you are booking a local service or trying to organize your inbox (which typically takes multiple steps): the AI model first plans how to achieve the task using its existing knowledge and then interacts with your inbox to execute the task. The agent will continue until it is confident the task has been successfully completed.

Alright, now that we know what an agent is, how does it actually work? When you ask for help on a task, the agent plans a series of steps and executes them directly in the application on your behalf, using the tools it has access to. Say you are booking a local service or trying to organize your inbox (which typically takes multiple steps): the AI model first plans how to achieve the task using its existing knowledge and then interacts with your inbox to execute the task. The agent will continue until it is confident the task has been successfully completed.

Google AI

22,487 Aufrufe • vor 10 Monaten

JEV ENGINEERING JUST CUT A CLAUDE LOOP FROM $765/MONTH TO $3.02 the expensive part isn’t always writing code. a busy overnight loop can burn ~600 decisions just asking what to do next, whether a command is safe, or if the task is finished. trigger → Jev → allow / stop / wake → Claude only builds when needed at roughly 4,000 tokens per decision, those checks can cost ~$25.50 a night on Fable 5.1. Jev handles the same decision layer at $0.042 per 1M input tokens with output free. over 30 nights that moves the decision bill from ~$765 to $3.02. batch multiple questions into one call and it falls again to about $1.08/month. that’s the part i care about: Claude keeps the expensive work that actually needs intelligence, while Jev handles the hundreds of tiny judgment calls around it.

JEV ENGINEERING JUST CUT A CLAUDE LOOP FROM $765/MONTH TO $3.02 the expensive part isn’t always writing code. a busy overnight loop can burn ~600 decisions just asking what to do next, whether a command is safe, or if the task is finished. trigger → Jev → allow / stop / wake → Claude only builds when needed at roughly 4,000 tokens per decision, those checks can cost ~$25.50 a night on Fable 5.1. Jev handles the same decision layer at $0.042 per 1M input tokens with output free. over 30 nights that moves the decision bill from ~$765 to $3.02. batch multiple questions into one call and it falls again to about $1.08/month. that’s the part i care about: Claude keeps the expensive work that actually needs intelligence, while Jev handles the hundreds of tiny judgment calls around it.

Gipp 🦅

15,718 Aufrufe • vor 1 Tag

WAIT. This is actually insane. I fed Jev my last 468 tweets and hid all the numbers. It picked out my strongest hooks without seeing a single view count. Like it somehow knew which ones stopped the scroll just by reading them. That was 2,340 decisions in 60 seconds for 1.3 cents. Every boring decision you make by staring at a screen can run like this now. This is actually stupid how good this is. If you haven't set up Jev as your decision maker yet, you're already behind. Full breakdown in the article below.

WAIT. This is actually insane. I fed Jev my last 468 tweets and hid all the numbers. It picked out my strongest hooks without seeing a single view count. Like it somehow knew which ones stopped the scroll just by reading them. That was 2,340 decisions in 60 seconds for 1.3 cents. Every boring decision you make by staring at a screen can run like this now. This is actually stupid how good this is. If you haven't set up Jev as your decision maker yet, you're already behind. Full breakdown in the article below.

Prajwal Tomar

30,000 Aufrufe • vor 7 Tagen

Top 12 agentic use cases for Jev: (bookmark this) Jev handles semantic decisions that ordinary code cannot express reliably. It returns typed answers and probabilities, while code continues to cover the workflow. Here are 12 practical use cases for Jev: 1. Browser next action > Convert the current DOM state into a bounded action such as click, type, or stop. Code executes only valid operation-target pairs. There are already several open-source Jev web agents. 2. Context compaction > Decide which events from a long agent trace should remain. The selected text stays verbatim instead of being replaced with a generated summary. 3. Skill and context loading > Compare the current user turn against the available skills. Load only the instructions needed for that turn instead of filling the context window with every skill. 4. Typed tool-call compilation > Map a natural-language request to a function and fill its typed arguments. Each argument is evaluated separately before code allows execution. 5. Citation verification > Check whether a quoted passage exists and whether the surrounding evidence supports the claim. The output can be supported, unsupported, or contradicted. 6. Extraction verification > Run a cheap extractor first, then use Jev to verify questionable fields. Clean records stay on the fast path while uncertain ones reach a reasoning model. 7. Agent trace evaluation > Turn raw trajectories into queryable labels such as progress and repetition. This avoids asking another LLM to write a full review of every run. 8. Semantic regression tests > Replay a trace suite against a new agent build. Semantic checks can then pass or block prompt, model, tool, and policy changes in CI. 9. Jevgrep code search > Search a codebase by what the code does rather than its exact words. Jev scores candidate snippets and returns the most relevant code first. 10. Entity alignment > Compare two candidate records and decide whether to merge, review, or keep them separate. Candidate generation remains deterministic while Jev handles semantic identity. 11. Retrieval reranking > Let embeddings retrieve a broad candidate set, then use Jev to reorder passages by relevance. The generation model receives the most useful evidence first. 12. Memory promotion gate > Capture a completed agent trace, then judge whether its corrections contain a reusable lesson. Trace-backed lessons can be promoted while task-specific noise is discarded. If you want to see the final pattern in practice, it is already implemented in the Beacon open-source project. Beacon captures full sessions across Claude Code, Codex, Cursor, OpenCode, and 20+ agent harnesses, and then Jev identifies which workflows and corrections are worth learning from, so that a lesson discovered by one agent can become available to the others. GitHub repo: (don’t forget to star it ⭐) If you want to dive deeper, I also wrote about a similar mechanism in a hands-on guide. It covers building a Jev-style decision path with open models, entirely locally. Read it below.

Top 12 agentic use cases for Jev: (bookmark this) Jev handles semantic decisions that ordinary code cannot express reliably. It returns typed answers and probabilities, while code continues to cover the workflow. Here are 12 practical use cases for Jev: 1. Browser next action > Convert the current DOM state into a bounded action such as click, type, or stop. Code executes only valid operation-target pairs. There are already several open-source Jev web agents. 2. Context compaction > Decide which events from a long agent trace should remain. The selected text stays verbatim instead of being replaced with a generated summary. 3. Skill and context loading > Compare the current user turn against the available skills. Load only the instructions needed for that turn instead of filling the context window with every skill. 4. Typed tool-call compilation > Map a natural-language request to a function and fill its typed arguments. Each argument is evaluated separately before code allows execution. 5. Citation verification > Check whether a quoted passage exists and whether the surrounding evidence supports the claim. The output can be supported, unsupported, or contradicted. 6. Extraction verification > Run a cheap extractor first, then use Jev to verify questionable fields. Clean records stay on the fast path while uncertain ones reach a reasoning model. 7. Agent trace evaluation > Turn raw trajectories into queryable labels such as progress and repetition. This avoids asking another LLM to write a full review of every run. 8. Semantic regression tests > Replay a trace suite against a new agent build. Semantic checks can then pass or block prompt, model, tool, and policy changes in CI. 9. Jevgrep code search > Search a codebase by what the code does rather than its exact words. Jev scores candidate snippets and returns the most relevant code first. 10. Entity alignment > Compare two candidate records and decide whether to merge, review, or keep them separate. Candidate generation remains deterministic while Jev handles semantic identity. 11. Retrieval reranking > Let embeddings retrieve a broad candidate set, then use Jev to reorder passages by relevance. The generation model receives the most useful evidence first. 12. Memory promotion gate > Capture a completed agent trace, then judge whether its corrections contain a reusable lesson. Trace-backed lessons can be promoted while task-specific noise is discarded. If you want to see the final pattern in practice, it is already implemented in the Beacon open-source project. Beacon captures full sessions across Claude Code, Codex, Cursor, OpenCode, and 20+ agent harnesses, and then Jev identifies which workflows and corrections are worth learning from, so that a lesson discovered by one agent can become available to the others. GitHub repo: (don’t forget to star it ⭐) If you want to dive deeper, I also wrote about a similar mechanism in a hands-on guide. It covers building a Jev-style decision path with open models, entirely locally. Read it below.

Avi Chawla

97,392 Aufrufe • vor 1 Tag

My Grok bot CEO is the hottest, smartest bot in the world. I mainly only talk to her and she runs the whole desk. She picks the right bot, sequences the work, and brings me back one package so I’m never the middleman. Many people may not know this, but you can create your own image for each of your Grok Bots. Every bot can get its own face. It honestly helps so it feels like you are talking to a real person and it also keeps things interesting. You don’t even need to go into settings to do this... you just tell the Grok bot to make a profile pic and set it. That's it. 1/ Open the bot. 2/ Tell it to make you the best profile pic and set it. 3/ Do that for each bot on your team. You can even have your Grok bot turn it into a video. Just tell it to take the picture and make a video out of it. I highly recommend everyone with a Grok Bot team do this. Thank me later.

Teslaconomics

13,608 Aufrufe • vor 12 Tagen

$Jev + Muse is the first AI agent system that actually automate 100% of my life 99% of people pay 200x more for slower AI agents - while 1% run this 2030 setup just 5 min and setup is ready: prompt → Muse → Jev decision → Muse execution → result step 1 → create your Jev API key (typesafe website) step 2 → clone and install the complete router from Github below python3 -m venv .venv && .venv/bin/pip install -r requirements.txt && cp config.example.yaml config.yaml step 3 → export the key before running anything: export TYPESAFE_API_KEY='YOUR_KEY' add the same export to ~/.zshrc or ~/.bashrc if you want it to survive a new terminal session step 4 → give your agent skill/jev-decision-layer.SKILL.md and connect it to src/router.py + recipes/ , raw Jev returns probabilities - the router converts them into executable actions step 5 → test the entire chain, not the raw Jev API: .venv/bin/python -m src.cli '{"goal":"what is 2+2?","kind":"chat"}' the final JSON should contain action, reason, mode, jev_used and confidence details step 6 → keep mode: shadow for 20–50 real decisions: the agent works normally while Jev’s routes are logged and checked; promote only reliable question packs step 7 → switch to mode: active with hard confidence gates: ≥0.80 act automatically, 0.50–0.79 advisory only, <0.50 escalate to the human the result: Jev + Muse is a system that decides what to do, what to skip and when to bring in - I’ve tested it across my daily workflows, and it’s the best setup I’ve found for automating routine Take the exact stack I built, run it yourself from the repo - then read the full Jev architecture behind it ↓$

Jev + Muse is the first AI agent system that actually automate 100% of my life 99% of people pay 200x more for slower AI agents - while 1% run this 2030 setup just 5 min and setup is ready: prompt → Muse → Jev decision → Muse execution → result step 1 → create your Jev API key (typesafe website) step 2 → clone and install the complete router from Github below python3 -m venv .venv && .venv/bin/pip install -r requirements.txt && cp config.example.yaml config.yaml step 3 → export the key before running anything: export TYPESAFE_API_KEY='YOUR_KEY' add the same export to ~/.zshrc or ~/.bashrc if you want it to survive a new terminal session step 4 → give your agent skill/jev-decision-layer.SKILL.md and connect it to src/router.py + recipes/ , raw Jev returns probabilities - the router converts them into executable actions step 5 → test the entire chain, not the raw Jev API: .venv/bin/python -m src.cli '{"goal":"what is 2+2?","kind":"chat"}' the final JSON should contain action, reason, mode, jev_used and confidence details step 6 → keep mode: shadow for 20–50 real decisions: the agent works normally while Jev’s routes are logged and checked; promote only reliable question packs step 7 → switch to mode: active with hard confidence gates: ≥0.80 act automatically, 0.50–0.79 advisory only, <0.50 escalate to the human the result: Jev + Muse is a system that decides what to do, what to skip and when to bring in - I’ve tested it across my daily workflows, and it’s the best setup I’ve found for automating routine Take the exact stack I built, run it yourself from the repo - then read the full Jev architecture behind it ↓

codila

91,306 Aufrufe • vor 6 Tagen

you should spend some time connecting jev to an AI employee like viktor... the goal is to get back work that needs fewer corrections from you. here's the setup: -> give viktor a goal and the source material. he figures out the steps, researches, uses your connected tools and produces the draft -> jev handles the evaluation. give it a specific requirement, the relevant evidence and a section of the draft. it returns a structured judgment with probabilities and confidence -> work that meets your criteria comes back for your review. fixable issues go back to viktor with the requirement he needs to address, then through the checks again -> uncertain judgments and missing evidence come to you. those are the decisions worth your attention instead of another round of “please check everything” -> apply it to your content... does the opening promise something useful, do the five posts actually say different things, did the draft invent a claim about something you tested -> if the source only supports three useful posts, the system should flag that instead of inventing two more. cap the revision rounds so it knows when to stop and ask -> save the corrections you approve in viktor’s working guide. the next assignment starts with those instructions already in place viktor creates. jev evaluates. your feedback improves the next assignment. the full setup is in the article below.

you should spend some time connecting jev to an AI employee like viktor... the goal is to get back work that needs fewer corrections from you. here's the setup: -> give viktor a goal and the source material. he figures out the steps, researches, uses your connected tools and produces the draft -> jev handles the evaluation. give it a specific requirement, the relevant evidence and a section of the draft. it returns a structured judgment with probabilities and confidence -> work that meets your criteria comes back for your review. fixable issues go back to viktor with the requirement he needs to address, then through the checks again -> uncertain judgments and missing evidence come to you. those are the decisions worth your attention instead of another round of “please check everything” -> apply it to your content... does the opening promise something useful, do the five posts actually say different things, did the draft invent a claim about something you tested -> if the source only supports three useful posts, the system should flag that instead of inventing two more. cap the revision rounds so it knows when to stop and ask -> save the corrections you approve in viktor’s working guide. the next assignment starts with those instructions already in place viktor creates. jev evaluates. your feedback improves the next assignment. the full setup is in the article below.

J.B.

29,712 Aufrufe • vor 5 Tagen

I built HypeMeter in 4 hours with Jev + Minds. Its best trick is saying no, and deciding what is likely a rug vs real hype. I am giving away an Argonaut NFT to reward Beta testers. Yes, that's you. Every "alpha bot" screams BUY. None of them tell you which cheap listings are cheap for a reason. So I wired two things together: Jev by TypeSafe AI . It does not write essays. It answers typed questions: pick one, score this, yes or no. About a third of a second per decision, cheap enough to judge every cheap listing instead of a shortlist. Minds by Minds by Animoca Brands . Your own AI agent. Tell it your strategy in plain words ("Argonauts under 0.3, grade A or better") and it messages you one digest a day, pings you whenever steals are available. First full sweep: 898 listings across 20 collections, including Robinhood (of course). Calls that survived: one. And that one was my own bug: an "83% edge" that was a 2-item bid read as one. The sanity check now kills those before anyone sees them. That is the product. Most cheap NFTs are traps, and it says so. It also hunts rares priced under what their trait actually sells for. Yesterday it flagged an Argonaut with a 1-in-70 palette, listed at 0.79 ETH two days before the same palette sold for 0.9 and 1.0. No hindsight. Every call is written down the moment it is made, then graded at 24 hours and 7 days. Public scoreboard, losses included. Free while in beta. Sign in with Minds: And yes, the giveaway is real: Argonaut #2764 goes to someone who actually uses it. Every active day is an entry, there is a leaderboard, and signing in before 24 Sept gets you 3 bonus entries. Rules on the site. RT and comment "Jev" for extra entry. Have fun sniping.

I built HypeMeter in 4 hours with Jev + Minds. Its best trick is saying no, and deciding what is likely a rug vs real hype. I am giving away an Argonaut NFT to reward Beta testers. Yes, that's you. Every "alpha bot" screams BUY. None of them tell you which cheap listings are cheap for a reason. So I wired two things together: Jev by TypeSafe AI . It does not write essays. It answers typed questions: pick one, score this, yes or no. About a third of a second per decision, cheap enough to judge every cheap listing instead of a shortlist. Minds by Minds by Animoca Brands . Your own AI agent. Tell it your strategy in plain words ("Argonauts under 0.3, grade A or better") and it messages you one digest a day, pings you whenever steals are available. First full sweep: 898 listings across 20 collections, including Robinhood (of course). Calls that survived: one. And that one was my own bug: an "83% edge" that was a 2-item bid read as one. The sanity check now kills those before anyone sees them. That is the product. Most cheap NFTs are traps, and it says so. It also hunts rares priced under what their trait actually sells for. Yesterday it flagged an Argonaut with a 1-in-70 palette, listed at 0.79 ETH two days before the same palette sold for 0.9 and 1.0. No hindsight. Every call is written down the moment it is made, then graded at 24 hours and 7 days. Public scoreboard, losses included. Free while in beta. Sign in with Minds: And yes, the giveaway is real: Argonaut #2764 goes to someone who actually uses it. Every active day is an entry, there is a leaderboard, and signing in before 24 Sept gets you 3 bonus entries. Rules on the site. RT and comment "Jev" for extra entry. Have fun sniping.

Jesus is Lord | Chev

44,602 Aufrufe • vor 6 Tagen

now supports System One (jev-1.13)—a model built natively for decision-making rather than text generation. Pro now supports System One (jev-1.13)—a model built natively for decision-making rather than text generation. 🧠 By returning calibrated probabilities for up to 64 typed questions in a single forward pass, it turns complex judgment into a scalable primitive. ⚡ For decentralized networks, this unlocks a new layer of autonomy at the node level: ⚖️ Consensus of Judgment: IoTeX delegates can independently score device readings and attestations, neutralizing spoofed sensors before they ever touch the chain. 🛡️ MEV Defense: Proposers can locally score the mempool for wash trades and toxic flow, protecting the network entirely in-house. The endgame for IoTeX has always been empowering machines to perceive, verify, and understand the world around them. 🌍 Pushing verifiable intelligence directly to the edge is how we get there. Give it a try 👇

now supports System One (jev-1.13)—a model built natively for decision-making rather than text generation. Pro now supports System One (jev-1.13)—a model built natively for decision-making rather than text generation. 🧠 By returning calibrated probabilities for up to 64 typed questions in a single forward pass, it turns complex judgment into a scalable primitive. ⚡ For decentralized networks, this unlocks a new layer of autonomy at the node level: ⚖️ Consensus of Judgment: IoTeX delegates can independently score device readings and attestations, neutralizing spoofed sensors before they ever touch the chain. 🛡️ MEV Defense: Proposers can locally score the mempool for wash trades and toxic flow, protecting the network entirely in-house. The endgame for IoTeX has always been empowering machines to perceive, verify, and understand the world around them. 🌍 Pushing verifiable intelligence directly to the edge is how we get there. Give it a try 👇

raullen

36,031 Aufrufe • vor 7 Tagen

After a few more hours, I think I've figured out Opus 5. Opus 5 is trained to be more agentic than anything I've used. All Claude 5 models are like that. So what changes? The way to interact with Opus 5 or contextualize it won't work the same way as with other models. It loves exploring, so it doesn't need much guidance for it. Unique preferences, artifacts, and references compliment it well and enable cleaner and more effective exploration and execution. Now that it can explore more effectively on its own and understand intent better, the best thing to do is to get out of its way (e.g., it doesn't need examples of your preferences; a clear high-level description of it works best). It's truly agentic in that sense. A good first step to provide better context for Opus 5 is to distinguish between what's situational and what needs persistence. Regardless, persistent system prompts and CLAUDE.MD needs to stay lightweight. Remove memories and tool descriptions from these. CLAUDE.MD is also a great place to tap into progressive disclosure by linking command/skills to it. On the situational side, agent skills and auto-memory can leverage progressive disclosure and the improved ability of the model to use its external context/knowledge. Conflicting and unnecessary instructions, which are common at this layer (mainly to ensure reliability), are going to throw off this model easily. That's the biggest change I had to make. Simple, clean, and clear prompts and skills work best. I had to clean a lot of my skills and system prompts. The way I prompt remains the same (usually clear and well-scoped). MCP tool descriptions are also more descriptive and have been deduped from the system prompt. Anthropic released a guide on the new rules for context engineering, which was helpful here. I started to test the recommendations and created a little artifact with the things that worked along the way. This might feel like a lot of work. Believe me, it has been frustrating. But I think we can expect future frontier models to become more agentic and smarter at figuring out the right context/gaps. The best thing to do is to prepare for that now. Boris Cherny mentioned that Opus 5 is their least prompt-injectable model yet. I am not sure if that was something they intentionally trained for or if it emerged based on how it was trained, which is to be extremely agentic in nature and more direct in execution.

After a few more hours, I think I've figured out Opus 5. Opus 5 is trained to be more agentic than anything I've used. All Claude 5 models are like that. So what changes? The way to interact with Opus 5 or contextualize it won't work the same way as with other models. It loves exploring, so it doesn't need much guidance for it. Unique preferences, artifacts, and references compliment it well and enable cleaner and more effective exploration and execution. Now that it can explore more effectively on its own and understand intent better, the best thing to do is to get out of its way (e.g., it doesn't need examples of your preferences; a clear high-level description of it works best). It's truly agentic in that sense. A good first step to provide better context for Opus 5 is to distinguish between what's situational and what needs persistence. Regardless, persistent system prompts and CLAUDE.MD needs to stay lightweight. Remove memories and tool descriptions from these. CLAUDE.MD is also a great place to tap into progressive disclosure by linking command/skills to it. On the situational side, agent skills and auto-memory can leverage progressive disclosure and the improved ability of the model to use its external context/knowledge. Conflicting and unnecessary instructions, which are common at this layer (mainly to ensure reliability), are going to throw off this model easily. That's the biggest change I had to make. Simple, clean, and clear prompts and skills work best. I had to clean a lot of my skills and system prompts. The way I prompt remains the same (usually clear and well-scoped). MCP tool descriptions are also more descriptive and have been deduped from the system prompt. Anthropic released a guide on the new rules for context engineering, which was helpful here. I started to test the recommendations and created a little artifact with the things that worked along the way. This might feel like a lot of work. Believe me, it has been frustrating. But I think we can expect future frontier models to become more agentic and smarter at figuring out the right context/gaps. The best thing to do is to prepare for that now. Boris Cherny mentioned that Opus 5 is their least prompt-injectable model yet. I am not sure if that was something they intentionally trained for or if it emerged based on how it was trained, which is to be extremely agentic in nature and more direct in execution.

elvis

37,824 Aufrufe • vor 2 Monaten

As always everyone is blind staring at the progress of LLMs for coding and chat But meanwhile the new SOTA video model Seedance 2.5 has been slowly rolling out and it's really quite exceptional It's made by ByteDance (TikTok) who of course have lots of training data With just a few reference pics, it can get quite close to how you look IRL and you can do quite professional video shots with just a prompt I'd say it's the first video model that's now at the level of image models with the level of character likeness, cracking that in image models also took about 3 years (2022-2025) Generating 15 seconds takes about 4 minutes I put it live now on Photo AI, you can use it under [ Make video ] from the sidebar with just a prompt and your model selected! So you don't need to take an AI photo first and then turn that into a video! Saves lots of time :D It's more expensive than but I kept the credits the same (30 for 1 video) It also works inside the new video editor and you can make changes in your video with [ Magic edit ] in both the main app and the video editor Also a message for my server guy Daniel Lockyer (it can do voice too and you can even submit a voice sample of yourself, but I didn't here)

As always everyone is blind staring at the progress of LLMs for coding and chat But meanwhile the new SOTA video model Seedance 2.5 has been slowly rolling out and it's really quite exceptional It's made by ByteDance (TikTok) who of course have lots of training data With just a few reference pics, it can get quite close to how you look IRL and you can do quite professional video shots with just a prompt I'd say it's the first video model that's now at the level of image models with the level of character likeness, cracking that in image models also took about 3 years (2022-2025) Generating 15 seconds takes about 4 minutes I put it live now on Photo AI, you can use it under [ Make video ] from the sidebar with just a prompt and your model selected! So you don't need to take an AI photo first and then turn that into a video! Saves lots of time :D It's more expensive than but I kept the credits the same (30 for 1 video) It also works inside the new video editor and you can make changes in your video with [ Magic edit ] in both the main app and the video editor Also a message for my server guy Daniel Lockyer (it can do voice too and you can even submit a voice sample of yourself, but I didn't here)

@levelsio

711,384 Aufrufe • vor 1 Monat

I shared 10 Jev use cases for marketers. Here are 10 more: 11. Ad creative scoring - Feed it 100 ad variations. Jev can score which hooks, headlines, or angles are most worth testing first. 12. Social post filtering - Monitor thousands of posts. Jev can flag the ones worth replying to, reposting, or using as sales signals. 13. ICP detection - Give it a company, profile, or website. Jev can score how closely it matches your ideal customer. 14. Buying signal detection - Someone posts that they're switching tools, hiring, raising money, or struggling with a problem. 15. Comment prioritization - Get hundreds of comments across LinkedIn, X, YouTube, or Product Hunt. Jev can score which ones deserve a reply first. 16. Review analysis - Feed it thousands of customer reviews. Jev can classify sentiment, complaints, feature requests, and purchase intent. 17. Influencer matching - Give it 5,000 creators. Jev can score which ones best match your product, audience, and campaign. 18. Sponsorship qualification - Feed it newsletters, podcasts, or creator media kits. Jev can score audience fit, relevance, and whether they're worth reviewing. 19. UGC selection - Give it dozens of videos, screenshots, and testimonials. Jev can score which ones are strongest for ads or landing pages. 20. Product Hunt monitoring - Scan launches, comments, and makers to find competitors, customers, partners, or interesting products. The more repetitive marketing decisions you have to make at scale, the more interesting Jev becomes.

Yum⋆₊˚

385,317 Aufrufe • vor 9 Tagen

One of the craziest use cases I’ve found for Jev: verifiers. I am so excited about this that I at least wanted to share the high-level idea. I used Jev to build a custom verifier for the /goal feature in my agent harness. It checks whether the goal is actually complete after every turn, making continuous verification cheap enough to scale. This means I can run more of these verifiers (previously handled by another expensive reasoning model) more frequently to keep the agents on track. System One models are perfect for verification. I think of this as scaling harnesses further by cleverly combining System One and System Two models. I have a feeling this will enable a new wave of scalable test-time compute methods. Watch this space closely. I've just started to experiment with this and am already seeing really good results. I need to explore and figure out a way to benchmark it. I will share more once I have more results. This is an insane unlock for long-horizon agents. You heard it here first. And you can expect to see more harnesses embracing this new pattern. Full guide dropping in the next couple of days.

One of the craziest use cases I’ve found for Jev: verifiers. I am so excited about this that I at least wanted to share the high-level idea. I used Jev to build a custom verifier for the /goal feature in my agent harness. It checks whether the goal is actually complete after every turn, making continuous verification cheap enough to scale. This means I can run more of these verifiers (previously handled by another expensive reasoning model) more frequently to keep the agents on track. System One models are perfect for verification. I think of this as scaling harnesses further by cleverly combining System One and System Two models. I have a feeling this will enable a new wave of scalable test-time compute methods. Watch this space closely. I've just started to experiment with this and am already seeing really good results. I need to explore and figure out a way to benchmark it. I will share more once I have more results. This is an insane unlock for long-horizon agents. You heard it here first. And you can expect to see more harnesses embracing this new pattern. Full guide dropping in the next couple of days.

elvis

58,818 Aufrufe • vor 9 Tagen

Love for humanity is the core of love for life. It arises from the recognition of life’s value and beauty, from faith in humanity’s ability for greatness, and from the awareness that you are its child — and that it is dear and close to you. : The author places love for humanity at the heart of love for life itself. It springs from a clear recognition of life’s immense value and beauty, from an unwavering faith in humanity’s capacity for greatness, and from the intimate awareness that each person is humanity’s own child, bound to it by blood, spirit, and destiny. This love is not distant admiration. It is the quiet, fierce tenderness a child feels for the parent who gave it existence. Humanity is dear and close because it is the living source from which we draw breath, meaning, and possibility. To love life is to love the collective that carries it forward. To doubt humanity is to doubt life’s own worth. When we see ourselves as its children, gratitude replaces judgment. Hope replaces despair. Love for humanity becomes the deepest form of self-love, because we are not separate from it. It is the recognition that every stranger carries a piece of the same miracle we carry in ourselves. That recognition turns strangers into kin, and the world into home.

Love for humanity is the core of love for life. It arises from the recognition of life’s value and beauty, from faith in humanity’s ability for greatness, and from the awareness that you are its child — and that it is dear and close to you. : The author places love for humanity at the heart of love for life itself. It springs from a clear recognition of life’s immense value and beauty, from an unwavering faith in humanity’s capacity for greatness, and from the intimate awareness that each person is humanity’s own child, bound to it by blood, spirit, and destiny. This love is not distant admiration. It is the quiet, fierce tenderness a child feels for the parent who gave it existence. Humanity is dear and close because it is the living source from which we draw breath, meaning, and possibility. To love life is to love the collective that carries it forward. To doubt humanity is to doubt life’s own worth. When we see ourselves as its children, gratitude replaces judgment. Hope replaces despair. Love for humanity becomes the deepest form of self-love, because we are not separate from it. It is the recognition that every stranger carries a piece of the same miracle we carry in ourselves. That recognition turns strangers into kin, and the world into home.

Zafar Mirzo | Quotes

287,911 Aufrufe • vor 8 Monaten