Loading video...

Video Failed to Load

Go Home

🚨THE DEBRIEFING: FORENSIC VS. EVENT ANALYSIS You get events. Isolated moments. A treaty here. A law there. Each one handed to you in its own box, with its own explanation. That's event analysis. And when everything's isolated, nothing connects. No pattern. No plan. Just a pile of disconnected facts....

11,422 views • 3 months ago •via X (Twitter)

6 Comments

Brian Cates - Political Columnist & Pundit's profile picture
Brian Cates - Political Columnist & Pundit3 months ago

Pay attention. People are always telling me how smart they think I am. I'm not some kind of genius. I'm trained to see patterns, to analyze things forensically instead of in isolation. It's not hard to learn to think this way, like a forensic analyst. It just takes some training. Watch this pretty good explanation in the video above. Fake News is designed to KEEP YOU CONFUSED AND LOOKING IN THE WRONG DIRECTIONS by showing you everything in ISOLATION. To understand what's going on, to be able to 'pull back' and see the '40,000 foot view', you MUST learn to analyze forensically. There's a reason the Fake News Media and the Hollywood crowd want you to think people that can do that are CARAAAAAYZEEEEEEE. So you won't listen to them and you certainly won't learn anything from them.

Teddy Love's profile picture
Teddy Love3 months ago

Love it… Kinda like 3:22 length of clip. “322”. 🤣 See Blacklist Series for actionable examples.

RedAtlantis's profile picture
RedAtlantis3 months ago

❤️🙏🐸

trading fool's profile picture
trading fool9 days ago

I miss your ai vids and hope you start making them again... your posts/analysis are always great but rendering them into ai vids gives extra punch and relatability to the complex topics you discuss. either way though, you're great and ty

Doright's profile picture
Doright3 months ago

I'm assuming the guy on the couch is AI. Any contrary thinking?

TheDebriefing17's profile picture
TheDebriefing173 months ago

Unfortunately most people are programmed to only trust the news if it comes from the man behind the desk behind the microphone. I do not have the luxury of a newsroom so I created my own however it's my face it is my voice and it is my thoughts

Related Videos

Elon Musk, absolute leader of the AI race with Grok Bot, and it's not a joke anymore. Ultimate guide on god-mode setup of Grok Bot, the org chart that runs while you sleep, step by step: A Chief of Staff sits in the middle with no tools of its own, BUT it reads the outcome you gave it, picks who does what, and never does the work itself. That one rule is why it never turns into the bottleneck you hired it to remove. → Researcher pulls real sources and tracks what's actually moving, not what sounds true → Writer turns that into finished copy while the research is still in the room → Visualiser gets three reference visuals once, then ships everything in that style forever → Analyst reads what performed and tells the rest of the team what to stop doing → Scheduler owns timing and holds the queue → Publisher actually ships What makes it different from every AI tool you've used: each bot gets its own computer in the cloud, its own browser, its own files, and they all share one memory. So the research is already sitting inside the draft before the draft starts. Nothing gets copy-pasted between tabs, nothing waits on you to approve step four of nine. And you never write a workflow for it. You hit record, do the job once the way you actually do it, stop. It pulls out the steps, saves them as a skill, and puts it on a schedule. The shape you're aiming for on every bot: everything reversible finished, nothing sent. 36 drafts queued, 0 published. It does all the work and stops dead at the one line only you can cross. You stop prompting. You start assigning. Full charter blocks, the approval line and the routines are in the article below ↓

Miraqle

87,098 views • 1 month ago

elon musk started with 7 grok agents. by morning each had spawned somewhere between 80 and 900 more on its own, and no one had told them to multiply. openai and anthropic each sell you one agent that sits still for $400. this whole self-building swarm runs for $5 the swarm above is that overnight run, seven seeds that turned into thousands, every one of them working a slice of the same job with nobody at the keyboard here is the exact setup, and it costs nothing on top of a $5 key: -> spin up one grok agent and give it a standing order instead of a prompt: own a boring niche people search every day -> it reads x and reddit complaints in real time and picks the one nobody wants but everybody googles, because it is grok and it sees the whole app -> when the work outgrows it, it spawns its own helpers, 80 to 900 of them, and splits the site between them -> they build it on their own machines and ship 3 to 6 useful pages a night, on a routine you set once -> the swarm writes, negotiates and closes its own affiliate and referral deals by email, in your name, at 3am -> telegram sends you the money report and you never open the site -> month one is traffic, month three the first $237 lands, and it does not stop after that the whole time, opus 5 and gpt-5.6 are still sitting frozen, waiting for you to type the next message. one is a swarm that builds its own workforce and its own income while you sleep, the other is a $200 chat you have to drive by hand drop your $400/mo stack to $5, and bookmark this before someone's swarm spawns another 600 pages into the niche you would have owned. the full playbook is in the article below

starmex

97,805 views • 22 days ago

context engineering vs graph engineering. every few months the list gets a new word and everyone treats it as a replacement for the last one. these two are not on the same list. one decides what the model sees this turn, the other decides what exists at all. the cleanest way to tell them apart is to ask what a single unit of work looks like. > context engineering is the window the window opens empty, every single time. you assemble what goes in it. the prompt, the docs, the history, the tool results. the assembling is the work. the window only grows. it never shrinks on its own, so eventually something gets dropped. usually from the middle. usually without telling you. then the turn ends and the window is thrown away. not archived, thrown away. the next turn opens empty again and you re-explain what you already explained. good context engineering is knowing what to leave out, not what to pack in. the unit of work is one window. > graph engineering is the structure the same material arrives from the same sources. instead of packing it into a window, you pull entities out of it, resolve the duplicates into one node, and write typed edges between them. nothing here is stored as text you hope to find again. it is stored as a thing with a name and its connections to other things. when the turn ends, the graph is still there. the next turn does not start from zero. it starts by querying what already exists, and the query walks edges instead of guessing at similarity. good graph engineering is deciding what counts as the same thing twice. the unit of work is one relationship. > they are not alternatives the graph is what refills the window. context engineering decides what fits. graph engineering decides what there is to choose from. remove the graph and every session starts blind. remove the context work and the best structure in the world arrives as an unreadable dump. that also tells you which one broke. the answer drifted from what you actually said, or forgot something from this same session. that is the window. the answer is coherent but invents a connection that does not exist, or cannot join two facts it has clearly seen. that is the structure. people debug the prompt because the prompt is the easiest thing to edit. it keeps taking the blame for failures that live a layer down. save this - then read the full breakdown below

Hanako

19,160 views • 1 month ago

Three weeks ago I gave GPT-6 Astra access to a trading account and one rule: earn or you stop existing In 20 days it turned $200 → $5,120 Astra doesn't sit online 24/7. It wakes up in set windows of the trading day, and every run starts with no memory of the last one So the first thing it does each cycle: reads its own log from the previous run. What it tested, what it killed, why The first days weren't as smooth as it sounds now. On day two it bled $80 on a trade that passed the backtest clean. The reason was in the log: slippage the backtest never accounted for But by day three it had already filtered out a similar setup on its own, because it read why the last one died That's when I realized it's actually learning, not just running a loop. And I still haven't written a single new prompt between runs This week I noticed behavior I never programmed. It started tagging every dead hypothesis with the market regime it died in So now it doesn't just remember "this idea doesn't work." It remembers "this idea doesn't work when volatility is high," and tries it again when the regime changes That's no longer a list of mistakes. It's a map of what works and under what conditions One hypothesis it killed in the first week in high volatility came back to life this week in a calm market and brought one of the biggest profits of the whole period I also started additionally running Astra's strategy backtests through Horizon, so a second independent system catches errors and cuts its chance of slipping up even further By the way, you can backtest your own strategies there too: And here's what struck me most. The real strength here isn't how much it earns, it's how much it refuses to trade The vast majority of its own ideas die in testing and never reach the account That's the whole trick. Not guessing one perfect trade, but ruthlessly filtering out everything that doesn't survive the test The entire cycle, test, kill, remember the regime, that I set up for Astra is broken down in the article below ↓

qwinsi

72,619 views • 2 days ago

Mark Cuban just compared the most powerful AI on earth to a two-year-old in a high chair. The toddler won. Cuban: “A two-year-old on a high chair with a sippy cup knows that when she pushes that cup off, Mom’s going to come running and the baby’s going to be laughing its ass off. It knows the consequences of its actions.” Then he named the thing no one building AI wants to say out loud. Cuban: “If you ask ChatGPT or any of them something and it gives you bad advice, it has no idea what’s going to happen because you took that bad advice.” A system that passed the bar exam. Aced medical boards. Still can’t grasp what a child who can’t tie her own shoes already knows. The child understands cause and effect. AI understands pattern and prediction. They sound similar. They are not even close. A pattern tells you what comes next in a sequence. Consequence tells you what happens to the person standing at the end of it. One is math. The other is meaning. Cuban went further. Cuban: “If you were blind at an intersection and had the choice between your seeing-eye dog or holding up a phone with AI, I’m taking the seeing-eye dog every time.” Because the dog understands something no language model on earth understands. Stakes. The dog knows a wrong step means its owner gets hurt. The app knows a wrong step means a revised output. Hundreds of billions spent building systems that can write, reason, and diagnose. Not one of them loses sleep when the answer is wrong. A toddler pushing a cup off a tray runs a tighter feedback loop than every foundation model combined. The child doesn’t just predict the outcome. The child wants the reaction. Pushes the cup off the edge, watches it fall, watches Mom come running. Laughs. Because the child knew what would happen before the cup ever hit the floor. That gap between prediction and consequence isn’t a bug. It’s not getting patched in the next update. It is the unsolved problem of artificial intelligence. We didn’t build minds. We built mirrors. Mirrors don’t flinch when you walk into traffic.

Dustin

47,919 views • 4 months ago