Contextually Aware

Luis Calderon

What product managers can actually build with AI today—and where it still breaks.

  1. 1d ago

    Memory that learns from memory

    Memory that learns from memory Contextually Aware · Luis and Carina An assistant remembers a temporary demo instruction and accidentally replaces the production decision. What would help its next version handle a different exception correctly? Luis and Carina examine a proposed learning loop built around stored decisions, verified corrections, and later outcomes. The episode starts with Luis's documented rule that project facts belong in memory and reusable lessons belong in versioned skills. It then explores a small learned decision layer for deciding whether instructions apply permanently, temporarily, or need clarification. The database scenario is hypothetical. The combined system is a proposed design: no model training, benchmark reproduction, or deployment result is claimed. In this conversation Diagnose retrieval and extraction failures before treating them as model judgment failures. Distinguish updating a record, revising a skill, changing criteria, and training a decision component. Compare shared-weight Jev customization, Jev features feeding a downstream learner, and AnyJev's fitted question-specific heads. Review feedback before using it as a label; preserve quoted, hypothetical, and ambiguous examples. Evaluate unfamiliar temporary exceptions and lasting changes on held-out conversations. Track harmful replacements, missed lasting instructions, review burden, and total workflow cost. Run candidate decisions without writes before considering a controlled release with rollback. Listener question: Which mistake have you corrected twice, and what evidence would distinguish a retrieval failure from a judgment failure? Sources These sources were checked in the accompanying research through September 26, 2026. This adaptation does not add a new research pass or claim independent reproduction. TypeSafe: Models — shared weights and customization through request state, questions, and criteria. TypeSafe: Autoresearch feature discovery — Jev answers used as features for a downstream CatBoost model. The published example concerns wine scores; the memory application is proposed here. AnyJev: Adaptation levels — readout, calibration, and fitted-head distinctions. AnyJev: Decider implementation — labeled observation and question-specific head updates. Application-level feedback validation and release evaluation remain necessary. Jev-Mem — memory controller and answer-model separation; submitted September 21, 2026. Not evidence of continual retraining from user corrections. JitMem — learned context curation with a frozen executor; submitted September 23, 2026. Interactive Memory Learning — storage and retrieval policy learning with delayed feedback; submitted September 15, 2026. Model-judge rewards are a relevant evidence limitation. Production disclosure Scripted with AI assistance and performed using Luis’s approved synthetic voice and the Carina synthetic co-host voice. This is not a recording of a live conversation.

    Memory that learns from memory
  2. Sep 14

    One of the Hardest Problems in Mathematics. AI Says It Solved It in 88 Hours.

    # One of mathematics’ hardest problems. AI says 88 hours. OpenAI reports a proposed Navier–Stokes resolution. Luis and Maya examine what the claim means, where the METR task-horizon chart gets misread, and why the Hugging Face incident deserves scrutiny without invented claims of consciousness. ## In this episode - Fluid motion, singularities, and why this problem matters.- 88 hours of search plus 17 hours of formalization and checking.- Human guidance and independent mathematical scrutiny.- Task difficulty at 50% versus 80% success.- Capability, reliability, and business value.- The real security failure behind the Hugging Face headlines. ## Sources - OpenAI Navier–Stokes announcement: https://openai.com/index/navier-stokes-solution/- Clay problem status: https://www.claymath.org/millennium/navier-stokes-equation/- METR methodology: https://metr.org/time-horizons/- METR raw data: https://metr.org/assets/benchmark_results_1_1.yaml- Matthew Berman source video: https://www.youtube.com/watch?v=jQIeVznGG3k- METR/Redwood investigation: https://metr.org/blog/2026-08-26-openai-hugging-face-incident-investigation/- OpenAI incident report: https://openai.com/index/hugging-face-incident-and-the-road-ahead/ ## About the show https://contextuallyaware.comhttps://growthalchemylab.com ## Timed chapters 00:00 Contextually Aware intro00:28 Meet your host01:01 The setup02:13 What the article says02:46 The killer line03:14 The new way to think04:24 Concrete moves05:33 One thing to remember06:18 Where to find us06:42 Sign-off Article: https://growthalchemylab.com/blog/navier-stokes-88-hours Voice stack: Luisv3 saved clone and MiniMax socialmedia_female_1_v1; speech-2.6-hd.

    One of the Hardest Problems in Mathematics. AI Says It Solved It in 88 Hours.

Ratings & Reviews

5
out of 5
2 Ratings

About

What product managers can actually build with AI today—and where it still breaks.