正在加载视频...

视频加载失败

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

ANTHROPIC LEAKED A GRAPH WHERE ONE FILE WITH 7 ITEMS CUTS YOUR WORK FROM 8 HOURS TO 40 MINUTES AND TAKES 40 DECISIONS A DAY OFF YOU autonomy isn't a slider you drag to the right - it's a graph with 7 steps, and exactly one edge leads into... each one. your approve is worth nothing until there's a description of what the output should be - otherwise you're approving something nobody defined. you can't run a batch without checkpoints, because one crash in the middle rolls back all 40 tasks at once. the agent already works without you, and until it writes down what it did there's nothing to check the report against. this is where the point of no return sits: past it the loop runs while you sleep. the approval didn't disappear - you moved it onto an evaluator that never gets tired and never lets one through. silence is only allowed when there's a list of what breaks it: money, deletion, anything leaving the system. the last one is the brake - a turn limit and a budget cap, whichever runs out first kills the run. you build the brake before the engine - an agent you can't stop isn't autonomous, it's just unattended. skip one edge and nothing crashes and nobody warns you - the system quietly settles two steps lower and keeps running. save this - 7 steps, 7 artefacts, zero ways to jump one ↓show more

Sprytix

6,271 subscribers

41,920 次观看 • 1 个月前 •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Loops vs. Graphs, clearly explained! loops are great, but they have a ceiling: a loop makes one unit of work better. it cannot decide which units exist. so you end up with a very good agent running the wrong three steps, in the wrong order, one at a time. Graph engineering fixes this by moving the decision up a layer: what runs, what runs at the same time, and what never runs at all. you need both. here's how it works: a graph splits your system into two kinds of decision. ↳ inside a unit: the loop. produce, check, correct, repeat until green ↳ between units: the graph. split, fan out, merge, gate, send back Prompts → Context → Harness → Loops → Graphs you get parallel work, isolated contexts, and steps that stop running when nothing needs them. the trick is being selective about what becomes a node. only spend a model where judgment lives. merging, ranking, deduping and schema checks are edges, and edges are code. free, instant, and they cannot be argued out of a verdict. a graph where every edge is an agent pays rent on its own wiring. one thing to know before you scale it. a graph has two return paths, and almost everyone builds one. ↳ the correction edge is short. a gate rejects one unit back to the step that produced it, and it fixes the run you are in ↳ the learning edge is long. an accepted result goes back to the splitter as a constraint, and it fixes every run after skip the second and you get a graph that is fast and never gets smarter. next week it starts from the same place with the same blind spots. and a smaller one that eats whole nights: when a unit fails, return that unit, not the batch. send back four slices because one failed and you have just rewritten three correct ones. do it twice in a run and the run never converges. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this and read it below ↓

Loops vs. Graphs, clearly explained! loops are great, but they have a ceiling: a loop makes one unit of work better. it cannot decide which units exist. so you end up with a very good agent running the wrong three steps, in the wrong order, one at a time. Graph engineering fixes this by moving the decision up a layer: what runs, what runs at the same time, and what never runs at all. you need both. here's how it works: a graph splits your system into two kinds of decision. ↳ inside a unit: the loop. produce, check, correct, repeat until green ↳ between units: the graph. split, fan out, merge, gate, send back Prompts → Context → Harness → Loops → Graphs you get parallel work, isolated contexts, and steps that stop running when nothing needs them. the trick is being selective about what becomes a node. only spend a model where judgment lives. merging, ranking, deduping and schema checks are edges, and edges are code. free, instant, and they cannot be argued out of a verdict. a graph where every edge is an agent pays rent on its own wiring. one thing to know before you scale it. a graph has two return paths, and almost everyone builds one. ↳ the correction edge is short. a gate rejects one unit back to the step that produced it, and it fixes the run you are in ↳ the learning edge is long. an accepted result goes back to the splitter as a constraint, and it fixes every run after skip the second and you get a graph that is fast and never gets smarter. next week it starts from the same place with the same blind spots. and a smaller one that eats whole nights: when a unit fails, return that unit, not the batch. send back four slices because one failed and you have just rewritten three correct ones. do it twice in a run and the run never converges. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this and read it below ↓

Hanako

73,867 次观看 • 1 个月前

ANTHROPIC LEAKED A SETUP WHERE ONE FILE STARTS 7 LOOPS THAT TURN A PROMPT INTO A WORKING BUSINESS AI engineer drops in 1 file - the other 95% of the work closes automatically without them. spec → tasks → code → tests → docs → release → monitoring → back into the spec you don't write tickets anymore - you write the thing tickets get derived from, and Opus 5 cuts the spec into 6 tasks by itself. a task that fails its test comes back to itself, not to you - and runs a second lap without a single notification. 6 lanes of code run in parallel and none of them wait on you - the critic filters the diff before you ever open it. every new production bug becomes a permanent line in the eval set - the system never steps on it twice. monitoring isn't the end of the line, it's the start of the next spec - those back edges are what make it a graph instead of a conveyor. and one place is left where you say yes - release, 5 minutes instead of 5 hours. save this and paste it into Claude Code - and you get 7 loops that run without you ↓

ANTHROPIC LEAKED A SETUP WHERE ONE FILE STARTS 7 LOOPS THAT TURN A PROMPT INTO A WORKING BUSINESS AI engineer drops in 1 file - the other 95% of the work closes automatically without them. spec → tasks → code → tests → docs → release → monitoring → back into the spec you don't write tickets anymore - you write the thing tickets get derived from, and Opus 5 cuts the spec into 6 tasks by itself. a task that fails its test comes back to itself, not to you - and runs a second lap without a single notification. 6 lanes of code run in parallel and none of them wait on you - the critic filters the diff before you ever open it. every new production bug becomes a permanent line in the eval set - the system never steps on it twice. monitoring isn't the end of the line, it's the start of the next spec - those back edges are what make it a graph instead of a conveyor. and one place is left where you say yes - release, 5 minutes instead of 5 hours. save this and paste it into Claude Code - and you get 7 loops that run without you ↓

Sprytix

66,333 次观看 • 1 个月前

ANTHROPIC LEAKED A FILE THEIR LEAD ENGINEER SPENT 4 YEARS BUILDING AT A COST OF $3.2M - ONE SUPER AGENT WITH JEV HOLDS A BUSINESS DOING $2.4M A YEAR the agent costs $0, and in month one it's already pulling $100K+ read → decide → build → ship → watch → back to reading 24 cycles a day, and each one starts exactly where the last one stopped it doesn't sleep, doesn't forget and never asks what to do next in one night it runs more cycles than a team closes in a quarter JEV holds the context, the budget and the stop condition between hours - without it every cycle would start from zero it picks one change an hour, not twenty - which is exactly why nothing breaks if things get worse it rolls back on its own, no meeting and no explanation the price of the loop doesn't grow with the revenue: it's the same at $0 and at $200,000 a month $2.4M a year is 669 customers, and that's only true while all 669 keep paying every month one agent is one point of failure: the night the loop stopped, nobody noticed until morning it ships the changes, it doesn't find the customers - that part is still yours save this and paste it into Claude Code - let it build you this loop ↓

ANTHROPIC LEAKED A FILE THEIR LEAD ENGINEER SPENT 4 YEARS BUILDING AT A COST OF $3.2M - ONE SUPER AGENT WITH JEV HOLDS A BUSINESS DOING $2.4M A YEAR the agent costs $0, and in month one it's already pulling $100K+ read → decide → build → ship → watch → back to reading 24 cycles a day, and each one starts exactly where the last one stopped it doesn't sleep, doesn't forget and never asks what to do next in one night it runs more cycles than a team closes in a quarter JEV holds the context, the budget and the stop condition between hours - without it every cycle would start from zero it picks one change an hour, not twenty - which is exactly why nothing breaks if things get worse it rolls back on its own, no meeting and no explanation the price of the loop doesn't grow with the revenue: it's the same at $0 and at $200,000 a month $2.4M a year is 669 customers, and that's only true while all 669 keep paying every month one agent is one point of failure: the night the loop stopped, nobody noticed until morning it ships the changes, it doesn't find the customers - that part is still yours save this and paste it into Claude Code - let it build you this loop ↓

Sprytix

10,325 次观看 • 12 天前

ANTHROPIC LEAKED A SETUP WHERE A $1.2M A-YEAR TEAM FITS INTO ONE FILE FOR $4 A DAY you hire nobody - you write one file, and $106,500 of salaries in it turn into $4 of tokens. architect → 4 builders → tests → critic → docs → scout → chief → back into the file the architect runs twice a day and decides everything - the priciest model on the sheet is the smallest line on the bill at $1.05. four builders cost $1.20 a day - and a fifth builder is one more number in the file, not one more quarter of recruiting. the tester asks does it run, the critic asks should it exist at all - $1.22 together for two roles a solo dev never fills. nothing reaches you that hasn't been rejected at least once. the scout and the scribe cost 40 cents - the exact two roles that get cut from every real budget. nobody hires a documentation engineer, and everybody wishes they had one. the chief at 14 cents is the only one who writes back into the file - without it this is a list, with it the list edits itself. hiring the eleventh is a paragraph: no req, no interviews, no ramp - and firing is one command. save this and paste it into Claude Code - and you get 10 roles for the price of one coffee ↓

ANTHROPIC LEAKED A SETUP WHERE A $1.2M A-YEAR TEAM FITS INTO ONE FILE FOR $4 A DAY you hire nobody - you write one file, and $106,500 of salaries in it turn into $4 of tokens. architect → 4 builders → tests → critic → docs → scout → chief → back into the file the architect runs twice a day and decides everything - the priciest model on the sheet is the smallest line on the bill at $1.05. four builders cost $1.20 a day - and a fifth builder is one more number in the file, not one more quarter of recruiting. the tester asks does it run, the critic asks should it exist at all - $1.22 together for two roles a solo dev never fills. nothing reaches you that hasn't been rejected at least once. the scout and the scribe cost 40 cents - the exact two roles that get cut from every real budget. nobody hires a documentation engineer, and everybody wishes they had one. the chief at 14 cents is the only one who writes back into the file - without it this is a list, with it the list edits itself. hiring the eleventh is a paragraph: no req, no interviews, no ramp - and firing is one command. save this and paste it into Claude Code - and you get 10 roles for the price of one coffee ↓

Sprytix

47,679 次观看 • 1 个月前

ANTHROPIC LEAKED 6 RULES THAT RUN 8 LOOPS AT ONCE - AND ONE ENGINEER DOES THE WORK OF A TEAM one engineer with this system replaces an entire team - and costs the company 8 times less You → Opus 5 plan → Fable 5 ×8 execute → Fable 5 review → you: 5 min Opus 5 takes your intent and breaks it into subtasks - a bad plan multiplied across every loop gives the same number of disasters - the plan is the only thing you read carefully one repo - isolated worktrees for each loop - nobody stands on anyone's file - parallel PRs ship while you do nothing the agent runs the tests and fixes until green PR - a red build never reaches your eyes one CLAUDE.md for the whole fleet - without it you get different opinions from every loop and one merge hell the average engineer closes 3-4 tasks a day - this system closes a full sprint overnight with zero working hours Fable 5 pre-reviews every PR before it reaches you - you spend 5 minutes - your throughput is now measured in diffs read per hour bookmark and paste into Claude Code - your first fleet can start tonight

ANTHROPIC LEAKED 6 RULES THAT RUN 8 LOOPS AT ONCE - AND ONE ENGINEER DOES THE WORK OF A TEAM one engineer with this system replaces an entire team - and costs the company 8 times less You → Opus 5 plan → Fable 5 ×8 execute → Fable 5 review → you: 5 min Opus 5 takes your intent and breaks it into subtasks - a bad plan multiplied across every loop gives the same number of disasters - the plan is the only thing you read carefully one repo - isolated worktrees for each loop - nobody stands on anyone's file - parallel PRs ship while you do nothing the agent runs the tests and fixes until green PR - a red build never reaches your eyes one CLAUDE.md for the whole fleet - without it you get different opinions from every loop and one merge hell the average engineer closes 3-4 tasks a day - this system closes a full sprint overnight with zero working hours Fable 5 pre-reviews every PR before it reaches you - you spend 5 minutes - your throughput is now measured in diffs read per hour bookmark and paste into Claude Code - your first fleet can start tonight

Sprytix

37,904 次观看 • 2 个月前

THE HEAD ENGINEER AT ANTHROPIC LEAKED THE PATH FROM ZERO TO AN ENGINEER ON $1.4M A YEAR WITH A FULLY AUTOMATED TEAM in 12 days you reach the point where your job is deciding - one file carries the rest, and that's $120K a month. chat → terminal → skills → patterns → gates → fleet while you're copying answers into the editor, you are the wire between the model and the code - all 4 hops are yours. in the terminal copy-paste ends for good - the model sees the whole repo and git, not the snippet you pasted. skills is the last point where you're still tuning wording - 7 procedures sit on disk, exactly 1 enters the window. after that runs the real border: before it you improve prompts, past it you build something that doesn't depend on them. quality stops being how you phrased it - it becomes a contract and an evaluator that never gets tired. gates replace review: the cheap model triages the findings, the expensive one decides on the real ones - rejection happens before you open anything. a gate that never rejects anything is a status badge, not a gate. at the end it's 8 workers, cron and a file that edits itself - you read the morning report and you started nothing. skip a link and nothing throws an error, the reports keep arriving - they just stop being true. save this and paste it into Claude Code - one file, 12 days, zero ways to jump a step ↓

THE HEAD ENGINEER AT ANTHROPIC LEAKED THE PATH FROM ZERO TO AN ENGINEER ON $1.4M A YEAR WITH A FULLY AUTOMATED TEAM in 12 days you reach the point where your job is deciding - one file carries the rest, and that's $120K a month. chat → terminal → skills → patterns → gates → fleet while you're copying answers into the editor, you are the wire between the model and the code - all 4 hops are yours. in the terminal copy-paste ends for good - the model sees the whole repo and git, not the snippet you pasted. skills is the last point where you're still tuning wording - 7 procedures sit on disk, exactly 1 enters the window. after that runs the real border: before it you improve prompts, past it you build something that doesn't depend on them. quality stops being how you phrased it - it becomes a contract and an evaluator that never gets tired. gates replace review: the cheap model triages the findings, the expensive one decides on the real ones - rejection happens before you open anything. a gate that never rejects anything is a status badge, not a gate. at the end it's 8 workers, cron and a file that edits itself - you read the morning report and you started nothing. skip a link and nothing throws an error, the reports keep arriving - they just stop being true. save this and paste it into Claude Code - one file, 12 days, zero ways to jump a step ↓

Sprytix

10,836 次观看 • 1 个月前

ANTHROPIC LEAKED A FILE WHERE 8 ENGINEERS COST $2.40 A DAY INSTEAD OF $120,000 A MONTH Microsoft and Google already run this - the same 8 seats cost them $73 a month. the ring turns once a day, 3 shifts hand off the work, zero meetings. the scout has tomorrow's agenda ready before you sit down. the architect splits the work, 2 builders run parallel branches. contracts get written before the workers - skip that and every worker guesses what the last one meant. with contracts all three read one shape: what goes in, what comes out. 3 branches at once means you pay the slowest lane, not the sum of three. nothing reaches you unrejected: the cheap model asks does it run, the expensive one asks should it merge. a gate that never rejects anything is a status badge, not a gate. the night crew takes the long jobs that never fit a working day. 1 role out of 8 writes back into the file - cut that edge and the rest repeat monday for a year. save this and paste it into Claude Code - you write the file, the file runs the company ↓

ANTHROPIC LEAKED A FILE WHERE 8 ENGINEERS COST $2.40 A DAY INSTEAD OF $120,000 A MONTH Microsoft and Google already run this - the same 8 seats cost them $73 a month. the ring turns once a day, 3 shifts hand off the work, zero meetings. the scout has tomorrow's agenda ready before you sit down. the architect splits the work, 2 builders run parallel branches. contracts get written before the workers - skip that and every worker guesses what the last one meant. with contracts all three read one shape: what goes in, what comes out. 3 branches at once means you pay the slowest lane, not the sum of three. nothing reaches you unrejected: the cheap model asks does it run, the expensive one asks should it merge. a gate that never rejects anything is a status badge, not a gate. the night crew takes the long jobs that never fit a working day. 1 role out of 8 writes back into the file - cut that edge and the rest repeat monday for a year. save this and paste it into Claude Code - you write the file, the file runs the company ↓

Sprytix

699,444 次观看 • 1 个月前

one agent → a loop → a graph → a system that throttles itself Google just put the whole ladder in one free course. most people never leave the first rung. 2 hours 4 minutes, taught by two Google Cloud engineers. no signup, no paywall. 17:55 - build your first agent 39:55 - loop engineering: iterate, check, break 1:13:25 - graph engineering 1:35:27 - agents that throttle themselves 1:56:19 - the full graph for multi-agent systems the fourth one is the step nobody talks about. an agent that cannot throttle itself is not autonomous, it is just unattended. everyone builds one agent and calls it done. this is the version where the agents wire themselves into a graph and decide their own rate. and the thing that decides when one of them is allowed to stop is not in the course. that part you build yourself. bookmark and watch it today, then read the eval setup below

one agent → a loop → a graph → a system that throttles itself Google just put the whole ladder in one free course. most people never leave the first rung. 2 hours 4 minutes, taught by two Google Cloud engineers. no signup, no paywall. 17:55 - build your first agent 39:55 - loop engineering: iterate, check, break 1:13:25 - graph engineering 1:35:27 - agents that throttle themselves 1:56:19 - the full graph for multi-agent systems the fourth one is the step nobody talks about. an agent that cannot throttle itself is not autonomous, it is just unattended. everyone builds one agent and calls it done. this is the version where the agents wire themselves into a graph and decide their own rate. and the thing that decides when one of them is allowed to stop is not in the course. that part you build yourself. bookmark and watch it today, then read the eval setup below

Hanako

53,692 次观看 • 2 个月前

ANTHROPIC LEAKED A 5-AGENT SETUP THAT TURNS ONE QUESTION INTO A SOURCED REPORT you write one line and never open a tab - the fleet reads 40 sources and only the answer comes back. question → scope → 5 searchers → dedupe → writer → fact-check → report the scope agent turns a vague question into 5 angles that do not overlap - skip this and five agents fetch the same three articles. 5 searchers run in parallel with separate contexts - none of them sees what the others found, which is exactly why they do not converge on the same source. dedupe is code, not an agent - flatten, drop repeats, normalize URLs, zero tokens, instant. the writer only sees structured findings, never raw pages - it cannot cite something that was never verified because it never had access to it. the fact-checker reads the draft against the sources, not against itself - every claim without a matching source goes back, and only that section is rewritten. nothing reaches you until a second agent, with clean context, has tried to kill it. 12 minutes, 40 sources, one report where every line traces back to something real. save this and read the full graph engineering course below ↓

ANTHROPIC LEAKED A 5-AGENT SETUP THAT TURNS ONE QUESTION INTO A SOURCED REPORT you write one line and never open a tab - the fleet reads 40 sources and only the answer comes back. question → scope → 5 searchers → dedupe → writer → fact-check → report the scope agent turns a vague question into 5 angles that do not overlap - skip this and five agents fetch the same three articles. 5 searchers run in parallel with separate contexts - none of them sees what the others found, which is exactly why they do not converge on the same source. dedupe is code, not an agent - flatten, drop repeats, normalize URLs, zero tokens, instant. the writer only sees structured findings, never raw pages - it cannot cite something that was never verified because it never had access to it. the fact-checker reads the draft against the sources, not against itself - every claim without a matching source goes back, and only that section is rewritten. nothing reaches you until a second agent, with clean context, has tried to kill it. 12 minutes, 40 sources, one report where every line traces back to something real. save this and read the full graph engineering course below ↓

Hanako

59,030 次观看 • 1 个月前

ANTHROPIC LEAKED A $3.4M FILE THAT GIVES YOU A $120K/MONTH ENGINEERING TEAM IN 10 MINUTES AND BUILDS ANY SYSTEM Microsoft and Google have been using this file for a while - 5 roles, zero hires, and it costs $0. in 10 minutes the whole system is up: core, skills, contracts, tests, cron and a team already working. all of it rests on the root you write: who buys, what it costs, what the team never does, and one metric. Sonnet 5 brings up the core and wires the skills, Opus 5 splits the task and judges the result, Haiku 4.5 assembles the report on the batch queue. contracts get written before the workers - without them every hop re-guesses what the last one meant. with contracts the same object travels between all 5 roles: SETUP.md → skeleton → task graph → gate → report. the critic is the gate - nothing ships past it, which is why you never get a green build with dead logic. the auditor writes one line back into the root - tomorrow's team is better than today's, and you opened nothing. without that edge you don't have a loop, you have 5 scripts repeating monday for a year. 4 typed handoffs and 1 return - the whole system rests on those five arrows. save this and paste it into Claude Code - 10 minutes, 5 roles, zero hires ↓

ANTHROPIC LEAKED A $3.4M FILE THAT GIVES YOU A $120K/MONTH ENGINEERING TEAM IN 10 MINUTES AND BUILDS ANY SYSTEM Microsoft and Google have been using this file for a while - 5 roles, zero hires, and it costs $0. in 10 minutes the whole system is up: core, skills, contracts, tests, cron and a team already working. all of it rests on the root you write: who buys, what it costs, what the team never does, and one metric. Sonnet 5 brings up the core and wires the skills, Opus 5 splits the task and judges the result, Haiku 4.5 assembles the report on the batch queue. contracts get written before the workers - without them every hop re-guesses what the last one meant. with contracts the same object travels between all 5 roles: SETUP.md → skeleton → task graph → gate → report. the critic is the gate - nothing ships past it, which is why you never get a green build with dead logic. the auditor writes one line back into the root - tomorrow's team is better than today's, and you opened nothing. without that edge you don't have a loop, you have 5 scripts repeating monday for a year. 4 typed handoffs and 1 return - the whole system rests on those five arrows. save this and paste it into Claude Code - 10 minutes, 5 roles, zero hires ↓

Noisy

19,483 次观看 • 1 个月前

THE HEAD ENGINEER AT ANTHROPIC LEAKED A SETUP WHERE ONE FILE TURNS INTO A FINISHED PRODUCT IN 24 HOURS you hire nobody - you paste a $3.2M file into Fable 5, and the system unrolls itself from there. root → wiring → 4 branches → tests → release → back into the root in the first hour you write 4 things: boundaries, stack, roles, escalation - everything downstream is a consequence of that file. the first 5 hours the system wires itself into tools and only then decides what to build - a team would spread that across two weeks. 8 straight hours run 4 parallel branches with zero meetings - the same block a team fills with standups. by the time you finally open the diff, tests and the critic have already rejected it twice. the changelog is written by the run, not by a human from memory - so it never falls behind the code. your total involvement across the day is exactly 2 hours: the first one, and the one where you say ship it. the 9 hours you were asleep weren't downtime, they were capacity - a queue you have to launch by hand becomes your monday. and the key part: at 05:00 the report rewrites that same root - what shipped, what got rejected, what it cost. without that last line this is just a schedule - with it, the schedule improves itself. save this and paste it into Claude Code - and tomorrow starts from a better file than today did ↓

THE HEAD ENGINEER AT ANTHROPIC LEAKED A SETUP WHERE ONE FILE TURNS INTO A FINISHED PRODUCT IN 24 HOURS you hire nobody - you paste a $3.2M file into Fable 5, and the system unrolls itself from there. root → wiring → 4 branches → tests → release → back into the root in the first hour you write 4 things: boundaries, stack, roles, escalation - everything downstream is a consequence of that file. the first 5 hours the system wires itself into tools and only then decides what to build - a team would spread that across two weeks. 8 straight hours run 4 parallel branches with zero meetings - the same block a team fills with standups. by the time you finally open the diff, tests and the critic have already rejected it twice. the changelog is written by the run, not by a human from memory - so it never falls behind the code. your total involvement across the day is exactly 2 hours: the first one, and the one where you say ship it. the 9 hours you were asleep weren't downtime, they were capacity - a queue you have to launch by hand becomes your monday. and the key part: at 05:00 the report rewrites that same root - what shipped, what got rejected, what it cost. without that last line this is just a schedule - with it, the schedule improves itself. save this and paste it into Claude Code - and tomorrow starts from a better file than today did ↓

Sprytix

20,755 次观看 • 1 个月前

Orchestrators vs. Graphs, clearly explained! orchestrators are great, and everyone builds one first. here is the ceiling: an orchestrator sits above the work and routes every message. five agents report to it. it reads all five. it decides what each one does next, and reads all five replies. that is ten trips through one context, and by the fifth agent that context has read four reports, five instructions and its own reasoning about all of them. Graph engineering fixes this by removing the seat: not a better router, but no router at all. you need both, and here is the sentence that resolves the whole confusion: an orchestrator sits above the work and holds all of it. a graph is the shape of the work, and holds none of it. ↳ above the work: one context that has to see everything before anything ships ↳ inside the work: a splitter that hands out and lets go, and a merge that reads nothing Prompts → Context → Harness → Loops → Graphs the coordination did not disappear. it moved into the edges, where it costs nothing and cannot get tired. the trick is noticing what you actually built. if one node has to see every result before the run can finish, you did not remove the bottleneck. you hired it, gave it the longest context in the system, and made it the thing you were counting on to stay sharp. one thing to know before you scale it. an orchestrator degrades in the one way nothing catches. ↳ it does not crash, time out or return an error. it stays up and keeps routing ↳ it just starts routing worse, somewhere around the fifth report, and every downstream agent does exactly what it was told that last one catches careful people. you can have perfect isolation on every worker and still have one window quietly drifting at the top, and the traces will all look clean because each worker did its job. and the one that eats whole nights: the merge is where this shows up first. ranking five findings is not judgment, it is a sort. if a model is doing it, you are paying a model to read five reports so it can put them in an order that three lines of code would have got right, and now that model has read everything too. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this and read it below ↓

Orchestrators vs. Graphs, clearly explained! orchestrators are great, and everyone builds one first. here is the ceiling: an orchestrator sits above the work and routes every message. five agents report to it. it reads all five. it decides what each one does next, and reads all five replies. that is ten trips through one context, and by the fifth agent that context has read four reports, five instructions and its own reasoning about all of them. Graph engineering fixes this by removing the seat: not a better router, but no router at all. you need both, and here is the sentence that resolves the whole confusion: an orchestrator sits above the work and holds all of it. a graph is the shape of the work, and holds none of it. ↳ above the work: one context that has to see everything before anything ships ↳ inside the work: a splitter that hands out and lets go, and a merge that reads nothing Prompts → Context → Harness → Loops → Graphs the coordination did not disappear. it moved into the edges, where it costs nothing and cannot get tired. the trick is noticing what you actually built. if one node has to see every result before the run can finish, you did not remove the bottleneck. you hired it, gave it the longest context in the system, and made it the thing you were counting on to stay sharp. one thing to know before you scale it. an orchestrator degrades in the one way nothing catches. ↳ it does not crash, time out or return an error. it stays up and keeps routing ↳ it just starts routing worse, somewhere around the fifth report, and every downstream agent does exactly what it was told that last one catches careful people. you can have perfect isolation on every worker and still have one window quietly drifting at the top, and the traces will all look clean because each worker did its job. and the one that eats whole nights: the merge is where this shows up first. ranking five findings is not judgment, it is a sort. if a model is doing it, you are paying a model to read five reports so it can put them in an order that three lines of code would have got right, and now that model has read everything too. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this and read it below ↓

Hanako

44,226 次观看 • 21 天前

ANTHROPIC LEAKED 8 RULES THAT GIVE ONE ENGINEER 8X FROM A SINGLE CHANGE the engineers built it so nothing adds up - it multiplies, and that's the 8x task → split → verify → score → write back one queue means you wait for every step in turn - three workers together cost you the slowest one, not the sum of all. as long as you're the one reading the diff, the bottleneck is you, not the model. state is written at every step - a crash mid-run costs you one step, not the whole session. history gets compressed 25 times over - the next pass starts at 8k instead of 200k. nothing moves forward without a number - "it got better" isn't a result, and the breakage comes back when you're no longer watching. the eighth rule is the only one that writes back into CLAUDE.md - the agent records what it learned, and the next run doesn't start from zero. copy this into Claude Code today - and tomorrow you work like an engineer on $1.5M a year ↓

ANTHROPIC LEAKED 8 RULES THAT GIVE ONE ENGINEER 8X FROM A SINGLE CHANGE the engineers built it so nothing adds up - it multiplies, and that's the 8x task → split → verify → score → write back one queue means you wait for every step in turn - three workers together cost you the slowest one, not the sum of all. as long as you're the one reading the diff, the bottleneck is you, not the model. state is written at every step - a crash mid-run costs you one step, not the whole session. history gets compressed 25 times over - the next pass starts at 8k instead of 200k. nothing moves forward without a number - "it got better" isn't a result, and the breakage comes back when you're no longer watching. the eighth rule is the only one that writes back into CLAUDE.md - the agent records what it learned, and the next run doesn't start from zero. copy this into Claude Code today - and tomorrow you work like an engineer on $1.5M a year ↓

Noisy

37,450 次观看 • 1 个月前

You can spin up an AI workforce with one prompt. Here's why it works: it pulls the context the AI needs to lay the foundation. Give it: - your role - team size - the goals you want to hit. Then say "interview me." After that, build it out in four steps: 1) Start with 1 agent. - What does it feel like to work with one? 2) Make that agent proactive. - Now it's doing things on your behalf before you ask. 3) Expand to 2 agents. - One directs the other, or routes to it. - This is where you learn how context gets passed. 4) Scale the workforce. - A mission control where you watch it all move around. - Now you see what has to run in parallel, which agent never needed that tool, which one runs fine on a smaller model. - Not everything needs Opus. Sub-agents are haiku and sonnet. The catch: the prompt gets you agents with markdown files doing some stuff. Getting to the 90% plus level is iteration, and that part is specific to each person. Nobody can hand it to you. Start with one agent. Spin up one agent this week. The rest is discovery.

You can spin up an AI workforce with one prompt. Here's why it works: it pulls the context the AI needs to lay the foundation. Give it: - your role - team size - the goals you want to hit. Then say "interview me." After that, build it out in four steps: 1) Start with 1 agent. - What does it feel like to work with one? 2) Make that agent proactive. - Now it's doing things on your behalf before you ask. 3) Expand to 2 agents. - One directs the other, or routes to it. - This is where you learn how context gets passed. 4) Scale the workforce. - A mission control where you watch it all move around. - Now you see what has to run in parallel, which agent never needed that tool, which one runs fine on a smaller model. - Not everything needs Opus. Sub-agents are haiku and sonnet. The catch: the prompt gets you agents with markdown files doing some stuff. Getting to the 90% plus level is iteration, and that part is specific to each person. Nobody can hand it to you. Start with one agent. Spin up one agent this week. The rest is discovery.

The Startup Ideas Podcast (SIP) 🧃

18,006 次观看 • 1 个月前

I BUILT GROK BOT SECOND BRAIN 26 agents, one core, running off a single rule my own memory never followed: capture everything, forget nothing, connect it before you even ask. A voice note on a coffee walk gets split into a task and an idea in under 6 seconds - the core already knows the difference between something you have to do and something you just thought of. An idea from three weeks ago gets linked to the one you just had, automatically, before you remember you'd had it the first time. That visual -the rotating profile, the 26 glowing lines firing out through the skull, each one labeled with the agent running it - isn't a rendered mockup. It's the actual runtime. Every line is a live agent doing its job in real time, right now, in your browser. This isn't a note app. Note apps hold what you give them. This is a nervous system for everything your brain was never built to hold onto in the first place. Full build - the 26 agents, how memory actually persists, what it costs to set one up for real - is in the article.

Aleiah

257,595 次观看 • 1 个月前

Workflows vs. Graphs, clearly explained! workflows are great, and almost everyone has one. here is the ceiling: a workflow decides every step before it runs. you drew eight boxes in March. six months later the same three fire, every single time, and the other five have never once been reached. then a case arrives that nobody drew, and it goes to the closest wrong box. quietly, with a green status, because from the inside that looks exactly like success. Graph engineering fixes this by moving the decision: not what the steps do, but when the steps get chosen. you need both, and here is the sentence that resolves the whole confusion: a workflow decides the steps before it runs. a graph decides them while it runs. ↳ drawn in advance: the boxes, the branches, the order, the error path ↳ decided at runtime: how many units exist, what each one is allowed to see, which ones get created at all Prompts → Context → Harness → Loops → Graphs branches do not make it a graph. the branches were drawn in advance too, which means every one of them is a case you already thought of. the trick is knowing which part is allowed to be fixed. the node kinds are fixed. a splitter is a splitter, a gate is a gate, a merge is code. what is not fixed is how many of them exist this run, and that is decided after something has been read. one thing to know before you scale it. a workflow fails in a way that never pages anyone. ↳ the wrong branch ran, every check inside it passed, and the output is well formed ↳ nothing errored, because routing to the wrong box is not an error, it is a route that last one catches careful people. you cannot test your way out of it either, because the test suite was written from the same diagram that has the gap in it. and the one that eats whole nights: a workflow that has never surprised you is not stable, it is narrow. if it has run four hundred times and produced the same three shapes, it is not handling your work. it is handling the part of your work that fits it, and you have quietly stopped sending it the rest. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this and read it below ↓

Workflows vs. Graphs, clearly explained! workflows are great, and almost everyone has one. here is the ceiling: a workflow decides every step before it runs. you drew eight boxes in March. six months later the same three fire, every single time, and the other five have never once been reached. then a case arrives that nobody drew, and it goes to the closest wrong box. quietly, with a green status, because from the inside that looks exactly like success. Graph engineering fixes this by moving the decision: not what the steps do, but when the steps get chosen. you need both, and here is the sentence that resolves the whole confusion: a workflow decides the steps before it runs. a graph decides them while it runs. ↳ drawn in advance: the boxes, the branches, the order, the error path ↳ decided at runtime: how many units exist, what each one is allowed to see, which ones get created at all Prompts → Context → Harness → Loops → Graphs branches do not make it a graph. the branches were drawn in advance too, which means every one of them is a case you already thought of. the trick is knowing which part is allowed to be fixed. the node kinds are fixed. a splitter is a splitter, a gate is a gate, a merge is code. what is not fixed is how many of them exist this run, and that is decided after something has been read. one thing to know before you scale it. a workflow fails in a way that never pages anyone. ↳ the wrong branch ran, every check inside it passed, and the output is well formed ↳ nothing errored, because routing to the wrong box is not an error, it is a route that last one catches careful people. you cannot test your way out of it either, because the test suite was written from the same diagram that has the gap in it. and the one that eats whole nights: a workflow that has never surprised you is not stable, it is narrow. if it has run four hundred times and produced the same three shapes, it is not handling your work. it is handling the part of your work that fits it, and you have quietly stopped sending it the rest. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this and read it below ↓

Hanako

16,810 次观看 • 21 天前

your agent doesn't need a graph. it needs a verifier that isn't doing five jobs at once. a loop is already a graph - one node, one edge back to itself. you add a node when you'd hire a specialist. not before. here is the list of all 5 signals. read it before you draw another node.

your agent doesn't need a graph. it needs a verifier that isn't doing five jobs at once. a loop is already a graph - one node, one edge back to itself. you add a node when you'd hire a specialist. not before. here is the list of all 5 signals. read it before you draw another node.

Rohit

16,004 次观看 • 2 个月前

Boris Cherny, the engineer who built Claude Code: "I don't talk to an agent anymore. I talk to a loop" a prompt is one instruction you babysit. a loop is a goal the AI works toward on its own: > it plans > does the work > checks itself > fixes what's weak > and repeats until it's done you step out, the work keeps going that's the shift the best engineers quietly moved to. most people hear a line like that and have no idea what it means in practice this breaks it down without the hype: what a loop actually is, when it's worth building, when it's a money trap, and how to run one yourself today watch his clip, then read the article below

Boris Cherny, the engineer who built Claude Code: "I don't talk to an agent anymore. I talk to a loop" a prompt is one instruction you babysit. a loop is a goal the AI works toward on its own: > it plans > does the work > checks itself > fixes what's weak > and repeats until it's done you step out, the work keeps going that's the shift the best engineers quietly moved to. most people hear a line like that and have no idea what it means in practice this breaks it down without the hype: what a loop actually is, when it's worth building, when it's a money trap, and how to run one yourself today watch his clip, then read the article below

Dep

20,991 次观看 • 3 个月前

A DEVELOPER PROVED YOU CAN FIND THE EXACT COMMIT THAT BROKE YOUR CODE IN A HISTORY OF 10,000 -- IN ABOUT 13 STEPS, AUTOMATICALLY.. 33 minutes from a Google engineer on git bisect: the built-in command that binary-searches your entire history to hunt down the one commit that introduced a bug. -> The moment it lands, "When did this break?" stops being an afternoon of guessing. You hand git a good commit, a bad one, and a test and it finds the culprit while you watch. Most people debug a regression by reading diffs by hand, blaming the obvious file, and hoping. Bisect doesn't hope. It cuts the search in half, then in half again, until only the guilty commit is left standing. Reading history by hand was never the skill -> letting git do the binary search for you is. And when an AI agent dumps hundreds of commits into your repo and one quietly breaks production, bisect is what finds the needle without you reading a single line. The bug isn't hiding. It's sitting in one exact commit. Most people just never learned to make git point at it. Bookmark & Watch it today ↓

A DEVELOPER PROVED YOU CAN FIND THE EXACT COMMIT THAT BROKE YOUR CODE IN A HISTORY OF 10,000 -- IN ABOUT 13 STEPS, AUTOMATICALLY.. 33 minutes from a Google engineer on git bisect: the built-in command that binary-searches your entire history to hunt down the one commit that introduced a bug. -> The moment it lands, "When did this break?" stops being an afternoon of guessing. You hand git a good commit, a bad one, and a test and it finds the culprit while you watch. Most people debug a regression by reading diffs by hand, blaming the obvious file, and hoping. Bisect doesn't hope. It cuts the search in half, then in half again, until only the guilty commit is left standing. Reading history by hand was never the skill -> letting git do the binary search for you is. And when an AI agent dumps hundreds of commits into your repo and one quietly breaks production, bisect is what finds the needle without you reading a single line. The bug isn't hiding. It's sitting in one exact commit. Most people just never learned to make git point at it. Bookmark & Watch it today ↓

slash1s

37,857 次观看 • 3 个月前

ANTHROPIC MAPPED OUT 8 LEVELS OF AI AGENTS - AND ANYONE CAN REACH LEVEL 8 WHERE THE SYSTEM EARNS $70K WITHOUT YOU anyone can reach level 8 - one solo developer with the right architecture gets there in a few weeks level 1 - the agent can do one action - and 80% of developers call this a product level 3 - 50 tools in context at once - the model gets confused - most teams get stuck here and lose $30K/month level 4 - Opus 5 grades its own output and rejects before you see it - the first level where quality stops depending on luck level 5 - Opus 5 plans, Fable 5 executes in parallel - one brain, many hands level 7 - while you slept the agent did $3,000 worth of work and sent the report before you woke up level 8 - the fleet finds its own mistakes, patches the graph and tomorrow it is smarter than today bookmark and read below - 8 steps from level 1 to $70K/month without you

ANTHROPIC MAPPED OUT 8 LEVELS OF AI AGENTS - AND ANYONE CAN REACH LEVEL 8 WHERE THE SYSTEM EARNS $70K WITHOUT YOU anyone can reach level 8 - one solo developer with the right architecture gets there in a few weeks level 1 - the agent can do one action - and 80% of developers call this a product level 3 - 50 tools in context at once - the model gets confused - most teams get stuck here and lose $30K/month level 4 - Opus 5 grades its own output and rejects before you see it - the first level where quality stops depending on luck level 5 - Opus 5 plans, Fable 5 executes in parallel - one brain, many hands level 7 - while you slept the agent did $3,000 worth of work and sent the report before you woke up level 8 - the fleet finds its own mistakes, patches the graph and tomorrow it is smarter than today bookmark and read below - 8 steps from level 1 to $70K/month without you

Noisy

12,499 次观看 • 2 个月前