<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: anurag asawa</title>
    <description>The latest articles on DEV Community by anurag asawa (@anurag_asawa_12d5f5be39cf).</description>
    <link>https://dev.to/anurag_asawa_12d5f5be39cf</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4237436%2F8cf28a55-4e1f-4ad4-9911-542b17286642.png</url>
      <title>DEV Community: anurag asawa</title>
      <link>https://dev.to/anurag_asawa_12d5f5be39cf</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/anurag_asawa_12d5f5be39cf"/>
    <language>en</language>
    <item>
      <title>Total Recall for Sales - Building DealOS with Walrus Memory and Tatum</title>
      <dc:creator>anurag asawa</dc:creator>
      <pubDate>Tue, 10 Nov 2026 16:15:18 +0000</pubDate>
      <link>https://dev.to/anurag_asawa_12d5f5be39cf/total-recall-for-sales-building-dealos-with-walrus-memory-and-tatum-4do</link>
      <guid>https://dev.to/anurag_asawa_12d5f5be39cf/total-recall-for-sales-building-dealos-with-walrus-memory-and-tatum-4do</guid>
      <description>&lt;h1&gt;
  
  
  Total Recall for Sales: Building DealOS with Walrus Memory and Tatum
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Most sales tools summarize a call and forget it. DealOS remembers the deal, learns from the rep, and compounds what works across the organization.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Sales is an experience business, but the software is usually stateless. A discovery call becomes a summary. The summary becomes a CRM note. A quarter later, the next rep repeats the same discovery, hits the same objection, and learns the same lesson from scratch.&lt;/p&gt;

&lt;p&gt;We built &lt;strong&gt;DealOS&lt;/strong&gt; for the Tatum × Walrus Memory &lt;strong&gt;Total Recall&lt;/strong&gt; hackathon to close that loop. It is an experience-driven sales intelligence agent with three connected memory layers, persisted on &lt;strong&gt;Walrus Memory Mainnet&lt;/strong&gt; and verified through &lt;strong&gt;Tatum Sui Mainnet RPC&lt;/strong&gt;.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Demo disclaimer:&lt;/strong&gt; All customer transcripts and the multi-rep organizational dataset in this build are synthetic. They are clearly labeled in the product and must not be read as actual customer performance.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  The problem: sales intelligence resets
&lt;/h2&gt;

&lt;p&gt;A sales conversation contains more than a summary. It contains:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;the customer's real pain point and the words they used,&lt;/li&gt;
&lt;li&gt;the objection that stalled progress,&lt;/li&gt;
&lt;li&gt;the stakeholder who controls the budget,&lt;/li&gt;
&lt;li&gt;the buying signal that changed the deal,&lt;/li&gt;
&lt;li&gt;the approach the rep actually used,&lt;/li&gt;
&lt;li&gt;and what happened afterward.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Most systems keep fragments of that. Few keep the relationship between the situation, the strategy, and the outcome. That is why teams repeat themselves.&lt;/p&gt;

&lt;p&gt;DealOS treats sales as a learning system, not a transcription pipeline.&lt;/p&gt;




&lt;h2&gt;
  
  
  Three memory layers
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Deal memory
&lt;/h3&gt;

&lt;p&gt;For each deal, DealOS remembers calls, facts, evidence, stakeholders, objections, buying signals, requirements, commitments, budget, timeline, and decision criteria.&lt;/p&gt;

&lt;p&gt;A memory is not simply a row of extracted text. When a new call arrives, DealOS compares new facts with existing deal memories and reconciles them as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;CREATE&lt;/strong&gt; — new knowledge,&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CONFIRM&lt;/strong&gt; — new evidence for existing knowledge,&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;REFINE&lt;/strong&gt; — improved understanding,&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CONTRADICT&lt;/strong&gt; — a conflict that must be surfaced.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Previous versions are preserved. The Memory Explorer makes this visible as an interactive graph and a lifecycle timeline.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Personal learning
&lt;/h3&gt;

&lt;p&gt;Salespeople capture techniques from books, videos, training, and experience. Those techniques are stored separately in the &lt;strong&gt;&lt;code&gt;dealos_demo_learning&lt;/code&gt;&lt;/strong&gt; namespace, synced to Walrus, and recalled semantically when relevant.&lt;/p&gt;

&lt;p&gt;Personal learning is not mixed into deal memory or shared organizational guidance.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Organizational intelligence
&lt;/h3&gt;

&lt;p&gt;Across deals and reps, DealOS identifies recurring sales situations, records what each rep actually did, tracks observable outcomes, and aggregates the evidence.&lt;/p&gt;

&lt;p&gt;The result is an evolving organizational playbook:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;standardized case taxonomy,&lt;/li&gt;
&lt;li&gt;case instances with transcript evidence,&lt;/li&gt;
&lt;li&gt;strategy executions,&lt;/li&gt;
&lt;li&gt;observed outcomes,&lt;/li&gt;
&lt;li&gt;conditional guidance,&lt;/li&gt;
&lt;li&gt;evidence-backed playbook versions,&lt;/li&gt;
&lt;li&gt;approval and versioning.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The organization does not learn by counting which strategy has the most wins. It learns &lt;strong&gt;under which conditions&lt;/strong&gt; a strategy was used and what evidence exists.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why Walrus Memory
&lt;/h2&gt;

&lt;p&gt;Sales memory has to outlive a single app session, a single model, and a single rep. Walrus Memory gives us a durable, portable semantic layer on Mainnet with three capabilities that matter here:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Durable writes&lt;/strong&gt; — case memories, personal techniques, and approved playbooks are persisted to Walrus.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Semantic recall&lt;/strong&gt; — the agent can retrieve similar situations, not just exact keyword matches.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Independent provenance&lt;/strong&gt; — PostgreSQL remains the structured application source of truth, while Walrus is the semantic memory layer. A PostgreSQL write never pretends a Walrus write succeeded.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;DealOS uses three Walrus namespaces:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Namespace&lt;/th&gt;
&lt;th&gt;Purpose&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;dealos_demo_deals&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Deal-specific call experiences&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;dealos_demo_learning&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Personal sales techniques&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;dealos_demo_organization&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Organizational case memories and approved playbooks&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The application uses:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;rememberAndWait()&lt;/code&gt; for organizational case memories and personal techniques,&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;analyzeAndWait()&lt;/code&gt; for approved playbook versions, letting Walrus extract durable guidance,&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;recall()&lt;/code&gt; for semantic retrieval in the UI and in recommendation generation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Walrus writes are tracked independently in &lt;code&gt;OrganizationMemorySync&lt;/code&gt; and &lt;code&gt;MemorySync&lt;/code&gt;, with status, attempts, errors, blob/job references, and retry actions.&lt;/p&gt;




&lt;h2&gt;
  
  
  Architecture
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Sales call transcript
        │
        ▼
Nemotron analysis (Zod-validated)
        │
        ├── PostgreSQL: call summary + extracted facts
        │
        ▼
Memory reconciliation against existing deal memories
        │
        ├── CREATE / CONFIRM / REFINE / CONTRADICT
        └── memory versions + provenance
        │
        ▼
Case identification (standardized taxonomy)
        │
        ├── case instance
        ├── observed salesperson strategy
        └── strategy execution
        │
        ▼
Walrus Memory Mainnet
        ├── case memory (rememberAndWait)
        ├── personal technique (rememberAndWait)
        └── approved playbook (analyzeAndWait)
        │
        ▼
Outcome tracking on later calls
        │
        ▼
Organization learning engine
        │
        ├── strategy evidence aggregation
        ├── conditional learning insights
        ├── playbook draft
        └── human approval
        │
        ▼
Recommendation generation
        ├── deal memory
        ├── personal learning
        ├── approved playbook
        └── Walrus semantic recall
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Structured records stay in PostgreSQL. Semantic memory stays in Walrus. The frontend never calls Walrus directly; the server mediates every write and recall.&lt;/p&gt;




&lt;h2&gt;
  
  
  How it learned over time
&lt;/h2&gt;

&lt;p&gt;Here is the loop we verified with real services.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 1 — A call creates a case
&lt;/h3&gt;

&lt;p&gt;A synthetic discovery call about manual renewal follow-ups produced:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;PRICE_OBJECTION / ROI_UNCLEAR&lt;/code&gt;,&lt;/li&gt;
&lt;li&gt;a pain point about 15–18 hours per week of manual work,&lt;/li&gt;
&lt;li&gt;an objection about proving ROI to the CFO,&lt;/li&gt;
&lt;li&gt;a buying signal for a demo,&lt;/li&gt;
&lt;li&gt;and an observed ROI-justification strategy execution.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The case was written to Walrus with provenance and no raw transcript.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 2 — The organization approves a playbook
&lt;/h3&gt;

&lt;p&gt;The ROI evidence was aggregated across comparable synthetic cases. The learning engine produced a draft playbook:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;ROI Justification for Unclear Value Objections&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The draft included conditional guidance, when to use it, when not to use it, suggested questions, exceptions, evidence counts, and a confidence score. A human approved it before it became active.&lt;/p&gt;

&lt;p&gt;The approved version was published to Walrus with &lt;code&gt;analyzeAndWait()&lt;/code&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 3 — A recommendation uses the playbook
&lt;/h3&gt;

&lt;p&gt;A new call was analyzed and matched to the same case subtype. The recommendation cited:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;the deal's ROI requirement and commitment,&lt;/li&gt;
&lt;li&gt;the customer's 15-hours-per-week pain point,&lt;/li&gt;
&lt;li&gt;the personal ROI-first discovery technique,&lt;/li&gt;
&lt;li&gt;the approved organizational playbook,&lt;/li&gt;
&lt;li&gt;and related Walrus organizational memories.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The recommendation was stored as &lt;strong&gt;SUGGESTED&lt;/strong&gt;, not executed.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 4 — Acceptance is not execution
&lt;/h3&gt;

&lt;p&gt;When the recommendation was accepted, it stayed accepted. Only when it was explicitly marked &lt;strong&gt;executed&lt;/strong&gt; did DealOS create a real &lt;code&gt;StrategyExecution&lt;/code&gt; with status &lt;code&gt;OUTCOME_PENDING&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;That distinction matters. An accepted suggestion is not evidence that anything happened.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 5 — A follow-up call records an outcome
&lt;/h3&gt;

&lt;p&gt;A follow-up transcript said finance had approved the business case and the customer wanted to move to the proposal.&lt;/p&gt;

&lt;p&gt;DealOS recorded:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;outcome &lt;code&gt;OBJECTION_RESOLVED&lt;/code&gt;,&lt;/li&gt;
&lt;li&gt;direct transcript evidence,&lt;/li&gt;
&lt;li&gt;source call,&lt;/li&gt;
&lt;li&gt;execution status &lt;code&gt;OUTCOME_RECORDED&lt;/code&gt;,&lt;/li&gt;
&lt;li&gt;recommendation status &lt;code&gt;OUTCOME_RECORDED&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The case memory was resynced to Walrus with the new outcome, and the follow-up call created a new &lt;code&gt;BUYING_SIGNAL / NEXT_STEPS&lt;/code&gt; case plus a new recommendation.&lt;/p&gt;

&lt;p&gt;That is the loop: &lt;strong&gt;individual experience → deal memory → case → strategy → outcome → organizational learning → shared playbook → better recommendation → new experience.&lt;/strong&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Tatum onchain proof
&lt;/h2&gt;

&lt;p&gt;DealOS uses &lt;strong&gt;Tatum Sui Mainnet RPC&lt;/strong&gt; for the onchain side of the memory story.&lt;/p&gt;

&lt;p&gt;The Tatum service calls:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;sui_getChainIdentifier&lt;/code&gt;,&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;sui_getLatestCheckpointSequenceNumber&lt;/code&gt;,&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;sui_getObject&lt;/code&gt; for the configured Walrus Memory account object.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The result is visible in two places:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;/infrastructure&lt;/code&gt; — live Tatum Sui Mainnet status.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;/intelligence?tab=walrus&lt;/code&gt; — a &lt;strong&gt;Tatum mainnet proof&lt;/strong&gt; card that reads chain identifier, latest checkpoint, and the Walrus Memory account object, with a link to Suiscan.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The Walrus Memory page also links every write to &lt;strong&gt;Walruscan&lt;/strong&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;https://walruscan.com/mainnet/blob/&amp;lt;blobId&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;and the memory account object to Suiscan.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Configuration note:&lt;/strong&gt; Tatum proof requires &lt;code&gt;TATUM_API_KEY&lt;/code&gt; in &lt;code&gt;.env&lt;/code&gt;. Without it, the UI reports &lt;code&gt;configuration missing&lt;/code&gt; rather than faking a successful call.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  What shipped
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Surface&lt;/th&gt;
&lt;th&gt;What it demonstrates&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;/deals&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Deal creation, stages, call counts, synthetic badges&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;/deals/[dealId]&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Transcript submission, call timeline, facts, evidence, Walrus status, deal recall&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;/deals/[dealId]/memory&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Interactive graph, memory versions, lifecycle timeline, recommendations, techniques&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;/learning&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Personal technique library, Walrus learning namespace, semantic recall&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;/intelligence&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Case Library, Strategy Explorer, Playbooks, Learning Insights&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;/intelligence?tab=walrus&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Walrus sync status, semantic recall, mainnet blob links, Tatum proof&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;/infrastructure&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Live PostgreSQL, Nemotron, Walrus, and Tatum checks&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The Memory Explorer uses React Flow and a wrapped per-call layout, so a deal with dozens of memories stays readable. Selecting a graph node highlights the corresponding lifecycle events; selecting a timeline event focuses the graph.&lt;/p&gt;




&lt;h2&gt;
  
  
  Evidence
&lt;/h2&gt;

&lt;p&gt;The current build has:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;20 completed Walrus Memory syncs&lt;/strong&gt; (16 organizational cases, 3 personal techniques, 1 approved playbook),&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;three active Walrus namespaces&lt;/strong&gt;,&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;real blob IDs&lt;/strong&gt;, visible in the UI and on Walruscan,&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;case-level provenance&lt;/strong&gt; (organization, case category, subtype, source call, strategy, outcome),&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;an approved playbook&lt;/strong&gt; with versioned evidence,&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;a verified outcome loop&lt;/strong&gt; that updated a strategy execution and recommendation and resynced the case memory.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Example mainnet blobs from the current demo:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Case memory: &lt;a href="https://walruscan.com/mainnet/blob/zy89k5okV8Mr7_eBACrZ8T6L_5lxeaPB5h-y9cFoZaI" rel="noopener noreferrer"&gt;&lt;code&gt;zy89k5okV8Mr7_eBACrZ8T6L_5lxeaPB5h-y9cFoZaI&lt;/code&gt;&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;ROI case memory: &lt;a href="https://walruscan.com/mainnet/blob/xRbgBI8_YmG0VRYBTSzT3PxeJ4gKICphyOGV6tOq5ys" rel="noopener noreferrer"&gt;&lt;code&gt;xRbgBI8_YmG0VRYBTSzT3PxeJ4gKICphyOGV6tOq5ys&lt;/code&gt;&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Personal technique: &lt;a href="https://walruscan.com/mainnet/blob/rKfW6CPMRJvrCqcR9WGgWA1vtgvltyGXNzME4FE-wNg" rel="noopener noreferrer"&gt;&lt;code&gt;rKfW6CPMRJvrCqcR9WGgWA1vtgvltyGXNzME4FE-wNg&lt;/code&gt;&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Approved playbook blob: &lt;a href="https://walruscan.com/mainnet/blob/BSeCwPqQJHWZTTn18HC5MgeCwxbo0ZmMbuzv22Qlq8c" rel="noopener noreferrer"&gt;&lt;code&gt;BSeCwPqQJHWZTTn18HC5MgeCwxbo0ZmMbuzv22Qlq8c&lt;/code&gt;&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Walrus Memory account object: &lt;a href="https://suiscan.xyz/mainnet/object/0x6b7b706987c258370007e040fe4f9e3a8540a15027292f13fc2e42fdf54bbf41" rel="noopener noreferrer"&gt;&lt;code&gt;0x6b7b706987c258370007e040fe4f9e3a8540a15027292f13fc2e42fdf54bbf41&lt;/code&gt;&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  What we learned
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Memory is not a summary.&lt;/strong&gt; The useful unit is a case with evidence, a strategy, and an outcome. A summary can tell you what happened; memory has to tell you what to do next.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Confirmation and contradiction matter.&lt;/strong&gt; A CRUD list of facts is not learning. DealOS preserves versions and explicitly represents when new evidence confirms, refines, or contradicts existing understanding.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Context beats a universal winner.&lt;/strong&gt; ROI justification looked strong in some contexts and failed in others. The playbook is conditional and evidence-scoped, not a leaderboard of “best strategies.”&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Execution and outcome are separate.&lt;/strong&gt; A recommendation being accepted is not execution. Execution is not success. Outcomes must be observed and attributed carefully.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Persistence needs honesty.&lt;/strong&gt; Walrus and PostgreSQL can fail independently. The UI shows each status, attempts, errors, and retry actions instead of collapsing them into one “saved” badge.&lt;/p&gt;




&lt;h2&gt;
  
  
  Limitations and next steps
&lt;/h2&gt;

&lt;p&gt;This is a hackathon build. The organizational dataset is synthetic and labeled. There is no authentication or per-user ownership boundary yet; organization scoping is enforced in the data layer, but production multi-tenant authorization is the next step.&lt;/p&gt;

&lt;p&gt;Other next steps:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;add real rep identities and access control,&lt;/li&gt;
&lt;li&gt;add retraction/correction workflows for organizational knowledge,&lt;/li&gt;
&lt;li&gt;expand outcome attribution beyond a single deal,&lt;/li&gt;
&lt;li&gt;add more Tatum reads for onchain memory proof and audit trails,&lt;/li&gt;
&lt;li&gt;add approval history and reviewer roles,&lt;/li&gt;
&lt;li&gt;and tighten confidence calibration as real evidence accumulates.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;nvm use
npm install
docker compose up -d
cp .env.example .env
&lt;span class="c"&gt;# Fill in OPENROUTER_API_KEY, MEMWAL_PRIVATE_KEY, MEMWAL_ACCOUNT_ID, TATUM_API_KEY&lt;/span&gt;
npx prisma migrate deploy
npm run dev
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Open:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code&gt;http://localhost:3000/deals&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;http://localhost:3000/deals/&amp;lt;dealId&amp;gt;/memory&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;http://localhost:3000/learning&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;http://localhost:3000/intelligence&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;http://localhost:3000/intelligence?tab=walrus&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;http://localhost:3000/infrastructure&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Load the synthetic organizational demo from &lt;code&gt;/intelligence&lt;/code&gt;, then search Walrus Memory with:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;ROI unclear CFO business case
migration risk phased rollout
ROI-first discovery technique
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;p&gt;&lt;strong&gt;DealOS is a proof that sales experience can compound.&lt;/strong&gt; Not as a chat history. Not as a CRM note. As evidence-backed memory that changes the next recommendation.&lt;/p&gt;

&lt;p&gt;Built for the Tatum × Walrus Memory &lt;strong&gt;Total Recall&lt;/strong&gt; hackathon.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>memory</category>
      <category>tatum</category>
      <category>web3</category>
    </item>
  </channel>
</rss>
