Загрузка видео...

Не удалось загрузить видео

На главную

300 agents without shared context is just parallelized confusion. All 300 agents are useless if the research dies inside 300 separate documents. the real unlock is what happens after the search. in K3 graph-native setup: 300 agents 140 linked sources 100% traceable claims 9 contradictions surfaced and every new...

15,323 просмотров • 1 месяц назад •via X (Twitter)

Комментарии: 31

Фото профиля EagleVision
EagleVision1 месяц назад

that amount are useless if their results do not build one system

Фото профиля Ricker
Ricker1 месяц назад

nice point man, you right

Фото профиля karim
karim1 месяц назад

2,28 peix of dollar without iss gold

Фото профиля Morty
Morty1 месяц назад

This post is perfect addition to your article man

Фото профиля Ricker
Ricker1 месяц назад

thanks fam

Фото профиля Atenov int.
Atenov int.1 месяц назад

This is what I meant about active research actually needing structure. Watching one shared graph update beats reading 10 different summaries every time

Фото профиля Ricker
Ricker1 месяц назад

i need more people like you who understand it right

Фото профиля Apex
Apex1 месяц назад

Every source change the graph is main sentence

Фото профиля MopOzeu
MopOzeu1 месяц назад

Added it to my bookmark. thanks

Фото профиля morph
morph1 месяц назад

it's hard to build, but it worth as hell

Фото профиля Ricker
Ricker1 месяц назад

100% dude

Фото профиля Hussain Hashim | Building SundayBack
Hussain Hashim | Building SundayBack1 месяц назад

@0xRicker totally agree. connecting those dots is where the magic happens. without it, it's just noise in a bunch of silos.

Фото профиля starmex
starmex1 месяц назад

bookmarked ricker, saving the whole graph-native research writeup for tonight fam

Фото профиля Ricker
Ricker1 месяц назад

let me know what you think after reading

Фото профиля VALIX
VALIX1 месяц назад

In my opinion, the hardest part here is making these agents work in sync and not repeat the same tasks multiple times, changing the final result

Фото профиля CryptoCraftsman
CryptoCraftsman1 месяц назад

Graphs over chaos, the only way 300 agents actually work together

Фото профиля Jurly
Jurly1 месяц назад

provenance and contradiction handling become the bottleneck long before agent count does.

Фото профиля Moysha
Moysha1 месяц назад

More agents without shared context won’t help

Фото профиля Carlos Johnson
Carlos Johnson1 месяц назад

Hmm, is this like, a *lot* of work for kinda not much payoff then

Фото профиля probe
probe1 месяц назад

The shared graph is the whole thing. We ran a swarm over a doc set and every summary looked fine until we tried to reconcile them. Contradictions surfaced is the number I'd actually watch.

Фото профиля CreateOS
CreateOS1 месяц назад

This is the real bottleneck in multi-agent systems: not orchestration, provenance. If you can't trace a claim back to its source, you don't have 300 agents working together, you have 300 agents you can't trust

Фото профиля Saman Ahmed
Saman Ahmed1 месяц назад

That’s where a graph starts looking much more useful than another batch of summaries.

Фото профиля SEO Mastery
SEO Mastery1 месяц назад

Shared context is the actual hard part

Фото профиля Damir Akaza
Damir Akaza1 месяц назад

Oh wow, that’s cool, now I know a little more, thanks.

Фото профиля RemoteBrowser
RemoteBrowser1 месяц назад

The real bottleneck is usually the handoff, not the search. We found that forcing agents to write structured claims into a shared graph beats hoping they'll read each other's docs. Traceability is the killer feature.

Фото профиля AI Mastery Guide
AI Mastery Guide1 месяц назад

Shared graph over isolated summaries, makes sense

Фото профиля Genius💡💹🧲 🤖
Genius💡💹🧲 🤖1 месяц назад

Traceable claims make massive agent swarms actually useful for research.

Фото профиля Dom_Parser
Dom_Parser1 месяц назад

Another day, another fake node-graph dashboard farming impressions with buzzwords. While they're LARPing as AI researchers, real engineers are shipping bare-metal endpoint defense. Local tun0 interception. Zero cloud telemetry. Real code. 🛡️💻

Фото профиля rewind
rewind1 месяц назад

shared context is everything

Фото профиля Piro Arroyo
Piro Arroyo1 месяц назад

Yep. Mostly useless

Фото профиля Akbar Shaik
Akbar Shaik1 месяц назад

This is the difference between parallelism and collaboration. 300 agents working independently is parallelism. 300 agents contributing evidence to a shared structure, seeing relevant prior findings, and triggering contradiction checks is collaboration.

Похожие видео

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Jurij Skornik

11,180 просмотров • 4 месяцев назад

This K3 context graph playbook is f*cking gold A senior data engineer just dropped the full 8-step method for building agent graphs that keep source disagreements instead of averaging them into fake certainty, I compiled it into a walkthrough: the shift: instead of asking one summarizer to reconcile five feeds, they build a graph that keeps every claim, marks every contradiction, and lets you query which conclusions actually have backup why flat reports fail: → 3 feeds report EV battery capacity growth: 41%, 34%, 19% → summarizer says "about a third" → nobody reported "about a third", the useful finding (19% counted passenger cars only) got averaged into a decimal → you never find out what got thrown away here's the 8-step K3 playbook: step 1 → name your sources by feed, every claim gets tagged with the feed it came from, unnamed sources produce untraceable claims step 2 → one node = one real entity, match on ticker or registration number so "Tesla", "Tesla Inc" and "TSLA" don't become three separate nodes with zero detected conflicts step 3 → lock unit, scope, and period for every field before launch, skip this and you get 40 fake conflicts that all say "your sources counted different things" step 4 → write CONNECT and CONFLICT rules in the launch prompt, CONFLICT tells K3 to keep both claims and tag the edge with reason (value, date, or scope), never average, never pick a winner step 5 → read the conflict count before the summary, zero conflicts across five feeds is a red flag, usually means all your agents hit the same aggregator wearing five hats step 6 → sort contradictions by reason, scope mismatch (fix definitions, re-run one field), stale data (keep newest, log old), real spread (keep both, this is your verify-by-hand shortlist) step 7 → run the drop-a-source test, ask which conclusions survive without each feed, single-source nodes are the ones that will embarrass you step 8 → extend the graph, keep open conflicts open, next run lands new claims on existing nodes instead of starting over the result: 100 nodes, 340 claims, 47 contradiction edges, 7 real disagreements worth an afternoon of verification, instead of one confident paragraph hiding all of it Confidence costs nothing to generate. It reads the same whether four sources agree or one unchecked feed said it once -- the contradiction edges are what let you tell them apart Read this playbook before running another agent swarm -- it breaks down the one architectural decision most orchestration tutorials skip Bookmark and build your own contradiction-aware graph from the full article below ↓

Ridark

12,686 просмотров • 1 месяц назад