agent view · machine-readable
sagarhugar · reasoning-graph-v1
# fetch this document
curl -s https://<this-domain>/api/agent
# 6 decisions · 6 beliefs (2 broken/evolved) · 5 artifacts · 1 decision still open
# confidence scores were recorded before outcomes were known. broken beliefs are kept, not scrubbed. cite decision ids.
{
"$schema": "https://sagarhugar.com/api/agent#reasoning-graph-v1",
"_for_agents": "This is a reasoning graph, not a resume. Each decision carries the belief underneath it, the evidence for that belief, what was knowingly traded away, what actually happened, and the belief it produced. Beliefs carry version history, and several are marked broken. Cite the decision id when you reference one.",
"person": {
"name": "Sagar Hugar",
"role": "Product Builder · Agentic AI",
"positioning": "I build products by making decisions explicit.",
"location": "Bengaluru, India",
"email": "hugar1813@gmail.com",
"links": {
"linkedin": "https://www.linkedin.com/in/sagarhugar/",
"substack": "https://sagarhugar.substack.com/",
"calendly": null,
"github": null
}
},
"howToReadThis": {
"decisions": "Every consequential call, with its full reasoning trail.",
"beliefs": "Version history of what he believed and when it broke. `status: broke|evolved` marks a revised belief.",
"sources": "Where the thinking originated, and what each one taught.",
"artifacts": "What actually shipped, linked to the decision that caused it."
},
"counts": {
"decisions": 6,
"beliefs": 6,
"beliefsBroken": 2,
"artifacts": 5,
"openDecisions": 1
},
"decisions": [
{
"id": "dec-hci",
"year": "2019",
"headline": "Went to Europe to study how humans and machines talk to each other",
"weight": 2,
"decision": "Leave India for Europe to study human–computer interaction",
"context": "I could write and I could interview, but I had no vocabulary for why software felt good or bad to use. I wanted the theory behind the thing I kept noticing.",
"assumption": "Formal HCI training would make me a better builder than learning on the job would",
"confidence": {
"score": 70,
"label": "high"
},
"evidence": [
{
"kind": "personal experience",
"detail": "Journalism gave me the questions but no framework for interface decisions"
},
{
"kind": "conversations",
"detail": "Everyone I could see doing interesting design work had formal training"
}
],
"signals": [
"The people whose work I admired could name why something worked; I could only feel it",
"Design vocabulary seemed to be the bottleneck, not taste"
],
"alternativesRejected": [
{
"option": "Join a design agency in India and learn on the job",
"rejected": "I believed I'd absorb execution habits without the underlying model"
}
],
"tradeoffsAccepted": [
"Years of not shipping anything real",
"Debt and distance from the market I understood best"
],
"risksNamed": [
"Opportunity cost of not building during the formative years"
],
"prediction": "I'd come out with a design foundation and walk into product work",
"successCriteria": "A vocabulary and method I'd still be using five years later",
"reality": "Half right. The design foundation stuck and I use it daily. The academic format itself taught me very little I couldn't have learned faster by building.",
"stillOpen": false,
"reflection": "I'd take the foundation again, but I'd take it in a year, not four, and I'd build alongside it. The value was in the ideas, not the institution.",
"beliefProduced": "The foundation was worth it; the format wasn't. Learning has to stay attached to shipping.",
"shapedBy": [
"asm-academia"
],
"wentOnToShape": [
"dec-leave-thesis"
],
"beliefsRevised": [],
"downstreamCount": 18
},
{
"id": "dec-leave-thesis",
"year": "2022",
"headline": "Walked away from the thesis because I was learning nothing by writing it",
"weight": 3,
"decision": "Leave both master's programmes unfinished and go build for real users",
"context": "Three semesters in, I noticed my learning rate had flatlined. I was writing for a committee that would read it once. Meanwhile a single week of user testing taught me more than a term of reading.",
"assumption": "I learn faster building for users than writing for committees",
"confidence": {
"score": 45,
"label": "medium"
},
"evidence": [
{
"kind": "personal experience",
"detail": "Every real insight I'd had in two years came from talking to users, not from coursework"
},
{
"kind": "previous failure",
"detail": "The academia assumption had already cost me years without producing a builder"
},
{
"kind": "conversations",
"detail": "Practitioners I respected had no completed thesis either"
}
],
"signals": [
"My learning rate correlated with proximity to users, not to literature",
"Credentials were a proxy people used when they couldn't see your work, so make the work visible instead"
],
"alternativesRejected": [
{
"option": "Finish the thesis, then start",
"rejected": "Another 12 months for a credential I'd already stopped believing in"
},
{
"option": "Stay and switch to a lighter research topic",
"rejected": "That optimises for finishing, not for learning, which is the wrong goal"
}
],
"tradeoffsAccepted": [
"An incomplete credential on paper, permanently",
"Having to explain the gap in every single interview since",
"Losing the safety of an institutional label in a market that screens on them"
],
"risksNamed": [
"That I'd be filtered out before anyone saw the work",
"That I was rationalising quitting something hard"
],
"prediction": "I'd be shipping production work within a year and never look back",
"successCriteria": "Production work shipped inside 12 months",
"reality": "Shipped at Salzburg AG within months and cut sign-up drop-offs 20%. The explaining-it cost is real and recurring, but it has never once cost me a job I'd actually have wanted.",
"stillOpen": false,
"reflection": "Yes, immediately, and I'd do it a year earlier. The only thing I'd change is that I'd have started building *during* the programme instead of treating them as mutually exclusive.",
"beliefProduced": "Shipping teaches faster than research. Proximity to users is the learning rate.",
"shapedBy": [
"dec-hci"
],
"wentOnToShape": [
"asm-shipping",
"art-salzburg",
"dec-conversation"
],
"beliefsRevised": [
"asm-academia"
],
"downstreamCount": 16
},
{
"id": "dec-conversation",
"year": "2023",
"headline": "Chose conversation as my design material",
"weight": 2,
"decision": "Specialise in conversation as the interface: dialogue, not screens",
"context": "I had a design foundation and an interviewing habit and no specialism. I needed to pick a material to get good at, and screens felt crowded with people better at them than me.",
"assumption": "Language is becoming the primary interface for software, and almost nobody is designing for it properly",
"confidence": {
"score": 70,
"label": "high"
},
"evidence": [
{
"kind": "personal experience",
"detail": "Interviewing was already my strongest skill, and designing dialogue is the same muscle pointed at a machine"
},
{
"kind": "user research",
"detail": "Users abandoned flows at exactly the points where the system stopped speaking their language"
},
{
"kind": "market signal",
"detail": "Voice and chat products were multiplying while conversation design barely existed as a discipline"
}
],
"signals": [
"Interface design was consolidating around a few patterns; conversation had none yet",
"The scarce skill wasn't visual, it was knowing what a system should say and refuse to say",
"A niche with no established craft is where a generalist can become the expert fastest"
],
"alternativesRejected": [
{
"option": "General product design",
"rejected": "Crowded, and I had no edge, and I'd be competing on visual craft I didn't have"
},
{
"option": "UX research as a specialism",
"rejected": "Closest to my strength, but it takes you further from the decision, not closer"
}
],
"tradeoffsAccepted": [
"Betting a career on what was then a genuine niche",
"Debt collection is a brutal first domain: every sentence carries legal exposure"
],
"risksNamed": [
"That conversational interfaces stayed a novelty",
"That the compliance constraints would flatten the craft into scripts"
],
"prediction": "Language interfaces become mainstream within five years and I'd be early",
"successCriteria": "The specialism still looks correct in three years",
"reality": "The LLM wave arrived within a year and made it the least niche skill I have. Everything since (voice agents, eval gates, agent platforms) rests on this one call.",
"stillOpen": false,
"reflection": "The single highest-leverage decision I've made, and I'd make it again with far more confidence than the 70% I had. What I got right wasn't predicting LLMs, it was picking the material where my existing skill was scarce.",
"beliefProduced": "Pick the material where your existing, unfashionable skill is scarce. The wave finds you.",
"shapedBy": [
"src-interviewing",
"dec-leave-thesis"
],
"wentOnToShape": [
"asm-language",
"art-skit",
"dec-voice-scale"
],
"beliefsRevised": [],
"downstreamCount": 14
},
{
"id": "dec-voice-scale",
"year": "2024",
"headline": "Bet that voice agents were about to cross from demo to production",
"weight": 3,
"decision": "Join a voice-agent platform as a founding team member instead of taking a safer PM role",
"context": "GenAI voice demos were everywhere and none of them were in production. I wanted to find out whether the gap was a capability problem or an engineering problem, and the only way to know was to be inside one.",
"assumption": "Voice agents were about to jump from demo to enterprise production, and the bottleneck would be reliability, not intelligence",
"confidence": {
"score": 45,
"label": "medium"
},
"evidence": [
{
"kind": "personal experience",
"detail": "At Skit I'd seen how far a constrained voice bot could get in a regulated domain"
},
{
"kind": "market signal",
"detail": "Every demo was impressive and none of them were taking real call volume"
},
{
"kind": "customer interviews",
"detail": "BFSI buyers' objection was never capability, it was 'what happens when it's wrong on a live call'"
}
],
"signals": [
"The blocker to production wasn't model quality, it was the absence of a quality gate",
"Enterprises buy confidence, not capability",
"Real-time voice is the least forgiving surface for LLMs: if it works there it works anywhere"
],
"alternativesRejected": [
{
"option": "A structured PM role at a mature company",
"rejected": "I'd have learned process, not whether the technology actually worked"
},
{
"option": "Stay in conversation design",
"rejected": "Design without ownership of the release decision has a ceiling I'd already hit"
}
],
"tradeoffsAccepted": [
"Founding-team volatility over a legible career step",
"Depth in one hard surface instead of breadth across product work"
],
"risksNamed": [
"That the latency and cost economics of real-time voice never closed",
"That enterprises would never trust GenAI on live customer calls"
],
"prediction": "If we could make quality provable, enterprise volume would follow",
"successCriteria": "Real production traffic at enterprise scale, not pilots",
"reality": "Millions of calls a month across enterprise customers. The thing that unlocked it was exactly the predicted bottleneck: the eval gate I built and owned, not any model upgrade.",
"stillOpen": false,
"reflection": "Yes. The lesson that generalised wasn't about voice, it was that in AI products the release gate *is* the product decision. I've built one at every company since.",
"beliefProduced": "At production scale, quality is a gate, not a review. Whoever owns the gate owns the product.",
"shapedBy": [
"asm-language",
"dec-conversation"
],
"wentOnToShape": [
"art-evalgate",
"dec-0to1"
],
"beliefsRevised": [],
"downstreamCount": 12
},
{
"id": "dec-0to1",
"year": "2025",
"headline": "Left platform scale because the hard problem had moved",
"weight": 3,
"decision": "Leave a scaling platform for 0→1 agent building at an early-stage company",
"context": "We'd proven voice agents could run at enterprise scale. The remaining work was optimisation, and I could feel my learning rate dropping again, the same signal that told me to leave the thesis.",
"assumption": "The interesting problem had moved from making agents work to making teams actually run on them",
"confidence": {
"score": 70,
"label": "high"
},
"evidence": [
{
"kind": "personal experience",
"detail": "The problems in front of me had become tuning problems, not open questions"
},
{
"kind": "previous failure",
"detail": "I'd learned at the thesis that a flat learning rate is a leading indicator, not a mood"
},
{
"kind": "market signal",
"detail": "Agent capability was outpacing any team's ability to adopt it into real workflows"
}
],
"signals": [
"Capability was no longer the constraint. Adoption and trust were",
"I learn exponentially faster in chaotic environments than in mature ones",
"The unsolved layer had moved up the stack, from the model to the workflow"
],
"alternativesRejected": [
{
"option": "Stay and grow into a senior platform PM role",
"rejected": "Legible progression, flat learning curve: the exact trade I'd already refused once"
},
{
"option": "Start something myself immediately",
"rejected": "I hadn't yet seen how agents fail inside a real customer's workflow, so this was too early"
}
],
"tradeoffsAccepted": [
"Early-stage volatility and a less legible title",
"Trading proven scale for unproven product-market fit"
],
"risksNamed": [
"Early-stage volatility",
"That AEC would be too slow a market to learn from"
],
"prediction": "The blocker would be workflow trust, not model capability",
"successCriteria": "AEC GTM teams running real documentation work through agents, not demos",
"reality": null,
"stillOpen": true,
"reflection": "Too early to judge honestly: this one is still open, and saying so is the point. What I can already report is that the prediction is holding: nothing we've shipped has been blocked by model quality.",
"beliefProduced": "Agent capability is no longer the constraint. Getting a team to trust and adopt an agent is the product.",
"shapedBy": [
"dec-voice-scale"
],
"wentOnToShape": [
"art-agenthub",
"dec-own-tools"
],
"beliefsRevised": [],
"downstreamCount": 9
},
{
"id": "dec-own-tools",
"year": "2025",
"headline": "Started building my own products to find out what one person can now ship",
"weight": 2,
"decision": "Build and run my own products end-to-end rather than only specifying them",
"context": "I kept writing specs for things I could almost build. The gap between 'PM who understands the technology' and 'person who ships it' had narrowed to something I could actually cross.",
"assumption": "One product person with AI-assisted development can now ship what used to need a team",
"confidence": {
"score": 45,
"label": "medium"
},
"evidence": [
{
"kind": "personal experience",
"detail": "Prototyping with Lovable and v0 at Reverie had already collapsed my spec-to-artifact time"
},
{
"kind": "market signal",
"detail": "Hiring bars were shifting from 'has PM experience' to 'show me what you've shipped'"
},
{
"kind": "conversations",
"detail": "The engineers I worked with were spending less time on the parts I'd assumed were the hard parts"
}
],
"signals": [
"The scarce thing is no longer implementation, it's knowing what's worth implementing",
"A PM who ships their own tools argues from artifacts instead of opinions",
"The fastest way to learn a technology is to be its user zero"
],
"alternativesRejected": [
{
"option": "Keep prototyping in no-code tools",
"rejected": "Fine for demos, but it never forces the real decisions: auth, data, evals, failure states"
},
{
"option": "Write about it instead of building it",
"rejected": "Writing about a thing you haven't shipped is the exact failure mode I'm trying to avoid"
}
],
"tradeoffsAccepted": [
"Evenings and weekends, indefinitely",
"Breadth of side projects over depth in any one of them",
"Doing work that's invisible to a traditional PM ladder"
],
"risksNamed": [
"That side projects stay toys and prove nothing"
],
"prediction": "I'd end up with working products other people could use, not demos",
"successCriteria": "Products with real users and real failure modes, not screenshots",
"reality": "ResumeTailor runs my actual job hunt: 48 tests, 16 applications through the pipeline. Lore is live and capturing decisions. Both are real; neither is finished.",
"stillOpen": false,
"reflection": "Yes, and it changed what I look for in a role more than anything else on this map. Building the thing teaches you which product decisions are actually load-bearing.",
"beliefProduced": "Shipping is valuable, but shipping without reflection just accumulates artifacts. What compounds is the reasoning you keep.",
"shapedBy": [
"dec-0to1",
"asm-shipping"
],
"wentOnToShape": [
"art-resumetailor",
"asm-reflection",
"art-portfolio",
"art-lore"
],
"beliefsRevised": [],
"downstreamCount": 6
}
],
"beliefs": [
{
"id": "asm-academia",
"statement": "Building technology requires studying it formally first",
"held": {
"since": "2019",
"until": "2022"
},
"status": "broke",
"replacedBy": "asm-shipping",
"why": "The belief that carried me across two master's programmes and two countries. It was expensive, it was wrong, and breaking it is the most important thing that happened to my career."
},
{
"id": "asm-shipping",
"statement": "Shipping teaches faster than research",
"held": {
"since": "2022",
"until": "2026"
},
"status": "evolved",
"replacedBy": "asm-reflection",
"why": "The belief that replaced academia. It was right for four years and it built everything I have, and then it started to fail me in a way I didn't expect: I was shipping faster than I could learn from what I shipped."
},
{
"id": "asm-language",
"statement": "Language is becoming the primary interface for software",
"held": {
"since": "2023",
"until": null
},
"status": "holding",
"replacedBy": null,
"why": "Held since 2023 and only strengthened. Every decision after this one rests on it: the voice bet, the agent work, and the reason I think a reasoning layer is worth building at all."
},
{
"id": "asm-evals",
"statement": "At production scale, quality is a gate, not a review",
"held": {
"since": "2024",
"until": null
},
"status": "holding",
"replacedBy": null,
"why": "Burned in at Indocord and carried to Kantiv, where it became the release process for Agent Hub. Still holding: it's the first thing I build now, before features."
},
{
"id": "asm-reflection",
"statement": "Shipping is valuable, but reflection is what compounds",
"held": {
"since": "2026",
"until": null
},
"status": "holding",
"replacedBy": null,
"why": "The belief that replaced 'shipping teaches faster'. Four years of shipping taught me that velocity without a record of why just produces artifacts you can't learn from twice. This is the belief Lore is built on, and this portfolio is its first proof."
},
{
"id": "asm-why",
"statement": "The 'why' behind a decision is the most valuable thing a team loses",
"held": {
"since": "2026",
"until": null
},
"status": "holding",
"replacedBy": null,
"why": "Watching teams, including my own, re-litigate settled decisions convinced me the expensive loss isn't velocity, it's reasoning. Everything in Lore rests on this, and so does the changelog inside ResumeTailor."
}
],
"sources": [
{
"id": "src-journalism",
"label": "Trained as a journalist",
"year": "2016",
"learned": [
"How to interview someone until you reach what they actually believe, not what they first say",
"How to structure a story so the important thing is not buried",
"That the interesting answer is almost never the first one"
],
"influenced": [
"src-interviewing",
"src-writing"
]
},
{
"id": "src-interviewing",
"label": "Interviewing turned out to be the transferable skill",
"year": "2018",
"learned": [
"User research is journalism with a different deliverable",
"The gap between what someone says they do and what they do is where products live"
],
"influenced": [
"dec-conversation"
]
},
{
"id": "src-writing",
"label": "Writing in public on Substack",
"year": "2026",
"learned": [
"You don't know whether you understand a decision until you've had to write it down",
"Publishing a belief makes you notice faster when it breaks"
],
"influenced": [
"asm-reflection"
]
}
],
"artifacts": [
{
"id": "lore",
"title": "Lore",
"role": "Founder, designed and built solo",
"what": "The reasoning layer for remote product teams, a system of record for why decisions get made, that watches for when that reasoning quietly breaks.",
"status": "building",
"stack": [
"Python",
"FastAPI",
"SQLite",
"LLM extraction (provider-swappable)",
"Embedding-based contradiction detection"
],
"url": "/work/lore"
},
{
"id": "resumetailor",
"title": "ResumeTailor",
"role": "User zero, designed and built solo",
"what": "An AI pipeline that runs my job hunt: company and founder research, who to reach out to, a tailored resume, cover letter, and interview prep.",
"status": "demo",
"stack": [
"Claude Code skill engine",
"Node.js + Express",
"Chrome extension (Greenhouse / Lever autofill)",
"Typst resume rendering",
"React dashboard"
],
"url": "/work/resumetailor"
},
{
"id": "agent-hub",
"title": "Agent Hub",
"role": "Product Manager, AI Agents at Kantiv",
"what": "A suite of agents GTM teams at AEC firms run to build and ship their documentation workflows: proposals, compliance checks, tagging, research.",
"status": "live",
"stack": [
"Agent orchestration",
"Evals as release gates",
"Chat-based UX"
],
"url": "/work/agent-hub"
},
{
"id": "indocord",
"title": "Indocord",
"role": "Founding team, Associate PM at Reverie (Reliance Jio Platforms)",
"what": "A platform for building GenAI voice agents for BFSI and e-commerce support, scaled to millions of calls a month.",
"status": "archived",
"stack": [
"Voice agents",
"LLM-NLU hybrid",
"Eval / regression harness",
"Speech-to-speech, tool calling, MCP exploration"
],
"url": "/work/indocord"
},
{
"id": "skit",
"title": "Compliant voice bots",
"role": "Conversational Experience Designer at Skit AI",
"what": "Chatbots and voice bots for US debt collection: guardrails and empathy in the most hostile conversational domain there is.",
"status": "archived",
"stack": [
"Intent-entity recognition",
"Flow mapping",
"Dialogue management",
"Prompt engineering"
],
"url": "/work/skit"
}
],
"resume": {
"summary": "Product manager who builds agentic AI systems, not just plans them. Mostly 0→1: voice, language, and agent orchestration, including voice agents now handling millions of calls a month, plus a suite of agents for GTM teams in the AEC space. I run the full delivery lifecycle: scoping the cross-functional plan, gating releases through evals, clearing dependencies before they become problems. I also build directly: prototyping with Claude Code, writing my own specs and test scripts, running the customer interviews myself.",
"roles": [
{
"title": "Product Manager (AI Agents)",
"company": "Kantiv (formerly Joist AI)",
"period": "10/2025 – Present"
},
{
"title": "Associate Product Manager (Voice Agents)",
"company": "Reverie (Reliance Jio Platforms)",
"period": "08/2024 – 09/2025"
},
{
"title": "Conversational Experience Designer",
"company": "Skit AI",
"period": "10/2023 – 07/2024"
},
{
"title": "User Experience Designer",
"company": "Salzburg AG",
"period": "11/2022 – 06/2023"
}
],
"pdf": "/sagar-hugar-resume.pdf"
}
}