𝗡𝗶𝗻𝗲 𝗽𝗹𝗮𝗰𝗲𝘀 𝘁𝗼 𝘂𝘀𝗲 𝗗𝗲𝗰𝗶𝘀𝗶𝗼𝗻 𝗠𝗼𝗱𝗲𝗹𝘀 (𝗝𝗲𝘃) 𝗶𝗻 𝗔𝗴𝗲𝗻𝘁𝗶𝗰 𝗥𝗔𝗚 𝘀𝘆𝘀𝘁𝗲𝗺 front to back 👇 𝟭. 𝗠𝗼𝗱𝗲𝗹 𝗿𝗼𝘂𝘁𝗶𝗻𝗴. The prompt goes to a decision model, i…


LinkedIn Content Strategy & Writing Style
Founder @ SwirlAI • Ex-CPO @ neptune.ai (Acquired by OpenAI) • UpSkilling the Next Generation of AI Talent • Author of SwirlAI Newsletter • Public Speaker
1 person tracking this creator on ViralBrain
Aurimas positions himself as a practitioner-educator for production AI, combining founder credibility at SwirlAI with experience as ex-CPO at neptune.ai and a mission to upskill the next generation of talent. His content centers on the engineering realities behind agentic systems: RAG architecture, MCP, memory, deployment patterns, decision models, evaluation, observability, cost, and governance. What distinguishes him is his insistence that teams move beyond impressive prototypes toward measurable, secure systems, using concrete concepts like TTFT, retrieval precision, AgentCore, and fallback paths. His work notably intersects technical education, enterprise consulting, and ecosystem-led product workshops, translating complex infrastructure into practical learning.
190.0K
30.0K
488
33
30
𝗡𝗶𝗻𝗲 𝗽𝗹𝗮𝗰𝗲𝘀 𝘁𝗼 𝘂𝘀𝗲 𝗗𝗲𝗰𝗶𝘀𝗶𝗼𝗻 𝗠𝗼𝗱𝗲𝗹𝘀 (𝗝𝗲𝘃) 𝗶𝗻 𝗔𝗴𝗲𝗻𝘁𝗶𝗰 𝗥𝗔𝗚 𝘀𝘆𝘀𝘁𝗲𝗺 front to back 👇 𝟭. 𝗠𝗼𝗱𝗲𝗹 𝗿𝗼𝘂𝘁𝗶𝗻𝗴. The prompt goes to a decision model, i…

𝗔𝗜 𝗔𝗴𝗲𝗻𝘁’𝘀 𝗠𝗲𝗺𝗼𝗿𝘆 is the most important piece of 𝗖𝗼𝗻𝘁𝗲𝘅𝘁 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴, this is how we define it 👇 In general, the memory for an agent is something that we provide via…

𝗔𝗜 𝗢𝗯𝘀𝗲𝗿𝘃𝗮𝗯𝗶𝗹𝗶𝘁𝘆 is a must have in your tool belt as an AI Engineer. 𝗧𝗿𝗮𝗰𝗶𝗻𝗴 sits at the core of it, why is it important? Tracing and instrumentation of software have been aroun…

This is how you measure your AI system as an AI Engineer 👇 For regular software you would track metrics like uptime, error rate, p95 latency. However, they say little about whether the system is fas…

𝗔𝗜 𝗔𝗴𝗲𝗻𝘁’𝘀 𝗠𝗲𝗺𝗼𝗿𝘆 is the most important piece of 𝗖𝗼𝗻𝘁𝗲𝘅𝘁 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴, this is how we define it 👇 In general, the memory for an agent is something that we provide via…

𝗔𝗜 𝗔𝗴𝗲𝗻𝘁’𝘀 𝗠𝗲𝗺𝗼𝗿𝘆 is the most important piece of 𝗖𝗼𝗻𝘁𝗲𝘅𝘁 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴, this is how we define it 👇 In general, the memory for an agent is something that we provide via…

0.0 posts/week
Posts / Week
30
Total Posts Analyzed
HIGH
Posting Frequency
487.6%
Avg Engagement Rate
STABLE
Performance Trend
0
Avg Length (Words)
HIGH
Depth Level
ADVANCED
Expertise Level
88/10
Uniqueness Score
YES
Question Usage
0%
Response Rate
Writing style breakdown
<start of post>
This is how you design observability for your AI Agent in production 👇
An AI Agent is not just an LLM call that returns a response. It is a software system that reasons, retrieves context, calls tools, makes decisions and sometimes repeats the whole loop several times.
If something goes wrong, looking only at the final answer will not tell you what actually happened.
➡️ Capture every step taken by the Agent, including the user query, prompts, retrieved context, tool calls and generated outputs.
➡️ Store the time spent in every step so you can understand whether the latency comes from retrieval, the model, a tool or the orchestration logic.
➡️ Keep the trace connected through the whole execution. A single final request is not enough when the Agent performs multiple LLM calls.
➡️ Track how often each tool is called and how often it fails.
➡️ Measure the latency of every tool separately. An Agent can look slow even when the LLM is fast because one external API is taking too long.
➡️ Record the input and output of the tool, while making sure that sensitive data is properly redacted.
➡️ Measure retrieval precision and recall on a labeled evaluation set.
➡️ Track how many retrieved documents are actually used in the final answer.
➡️ Observe the amount of duplicated, outdated or irrelevant context passed to the LLM.
If retrieval is not bringing the right information, generation quality will not solve the problem. The Agent can only reason over the context that it receives.
✅ Evaluate the final answer for correctness, groundedness and completeness.
✅ Track refusal, hallucination and policy violation rates.
✅ Compare the output against human labels or an LLM judge calibrated on representative examples.
The important part is to measure quality over time and not only during the initial launch. Prompt changes, model updates and changes in user behavior can silently degrade the system.
➡️ Track input and output tokens per completed task, not only per request.
➡️ Measure p50, p95 and p99 latency because average latency hides the users that are waiting the longest.
➡️ Track cost by user, team, application or workflow so you know which part of the system is becoming expensive.
❗️ The metric that matters most is usually not the cost of one LLM call. It is the cost of completing a successful task.
➡️ Track model errors, timeouts, rate limits and tool failures separately.
➡️ Observe how often the system retries or switches to another model.
➡️ Keep a record of the reason for the fallback. Otherwise a growing fallback rate can remain hidden while the system still looks available.
A production Agent should be observable at the level of the complete workflow, not only at the level of individual model requests.
➡️ A trace for every execution.
➡️ A metric for cost per successful task.
➡️ A quality evaluation that runs whenever the prompt or model changes.
With these in place, debugging becomes a lookup instead of a reconstruction.
What is the most useful metric you added to your Agent observability stack? Let me know in the comments 👇
<end of post>
Sign in to unlock the full writing analysis
Free tools to help you write, score, and benchmark in the same style.
Other creators worth studying alongside Aurimas Griciūnas.
Nick Abraham
I send 2M+ cold emails and 1M+ LinkedIn DMs per month for 1,000+ active clients across Leadbird and Cleverly
55 Viral Score

Matteo Fois
Co-Founder @ Kinetyca | I build GTM Systems that connect outbound, content, and paid ads into one revenue engine | Official Partners: Clay, Hubspot, Heyreach, Smartlead, Snov.io
124 Viral Score

Kellen Casebeer
Helping companies find Message-Market-Fit | Founder @ The Deal Lab
65 Viral Score

Daniel Priestley
Founder of Dent Global & ScoreApp | Awarded Entrepreneur of the Year | 7x business books | Founded/exited multiple ventures | Mission to develop entrepreneurs who stand out, scale up and make a dent.
14 Viral Score

Ben Labay
CEO @ Speero | Experimentation for growing SaaS, Ecommerce, Lead Gen
27 Viral Score

Yared Endale
Entrepreneur | HCD specialist | eSports Community Builder
1,579 Viral Score
ViralBrain plans, writes, and schedules your LinkedIn content, using official LinkedIn APIs so your account stays safe.
Write like Aurimas Griciūnas.