Daniel Graham

Identity verification shouldn’t take weeks of integrations, custom logic, and stitching APIs from five different standards. Hovi Core SDK gives developers a single, unified way to verify any credential SD-JWT, mDocs, JSON-LD, and more. One API call. One pipeline. Zero complexity. From strong authentication to automated access control and reusable KYC/KYB, you can make your app identity-aware without becoming identity-complex. Build trust once. Scale it everywhere. #Developers #DigitalIdentity #VerifiableCredentials 

2

People often ask how our VPs are prepared before working with clients.​ ◉ They don’t get placed and then “figure it out.”​ ◉ They train inside structured workflows first.​ ◉ They practice inside system environments.​ ◉ They review documentation for accuracy.​ ◉ They shadow real processes.​ ◉ They’re supervised while owning parts of the workflow.​ ​ By the time they’re client-facing, they’ve already operated inside structure - not just studied it.​ That preparation shows up in the details. #Savvital #AIEnabledOperator #SavvitalTraining​

23

"I have only made this letter longer because I have not had the time to make it shorter." - Blaise Pascal'' This also applies to software demos. We've tightened the onboarding workflow and now have a 60 second demo of the journey from a blank slate in Claude Code to a deployed preview application on VeilStream.

2

1 Comment

GitHub Copilot is making developers faster at the wrong thing. Hear me out: Copilot helps write code 30% faster. But code production is maybe 20% of development time. So you're optimizing 20% of 30%—that's a 6% improvement. Not transformation. Meanwhile, the real bottlenecks—requirements clarity, architecture decisions, integration complexity—remain completely untouched. We're celebrating marginal gains while the fundamental constraints haven't budged. AI-native development doesn't make the existing process faster. It replaces the process entirely. Instead of humans writing code with AI assistance, AI systems generate implementations while humans orchestrate intent, validate context, and ensure alignment with business outcomes. That's the shift from augmentation to transformation. #SoftwareDevelopment #AITransformation #EngineeringLeadership #DevOps #TechLeadership

35

13 Comments

Great framing. Technical accountants have always known the hardest part isn’t finding guidance, it’s excluding the noise. That’s where most AI falls short. Accountants shouldn’t have to guess how much context is “enough” for a model. This is what TAbot is built for. It continuously curates and feeds the right amount of high-signal context to the AI, so accountants get leverage without having to become prompt engineers. AI should adapt to accounting judgment, not the other way around. Highly recommend the read: https://lnkd.in/gxv3kiJx

2

📖 Scale your tenants, not your growing pains. As SaaS platforms grow, teams often hit friction from manual sharding, noisy neighbors, and rigid schemas. These challenges create operational drag and slow innovation. In this new guide, learn how teams like Atlassian, Manus, and Conga use modern data architectures to scale multi-tenant platforms with less complexity. Inside, you’ll learn how to achieve: 🔸 Elastic scalability without manual sharding 🔸 Strong tenant isolation for true multi-tenancy 🔸 Real-time, in-app analytics 🔸 Faster development with fewer operational constraints Download the free guide: https://ow.ly/1RIE50XZJUP #SaaS #MultiTenancy #DistributedSQL #TiDB #DatabaseArchitecture

10

The CMS ACCESS Model FHIR Implementation Guide is Up. My co-founder Hadi Javeed sat down with me last night and we pulled up the specs. Four API operations, seven subscription event types, twelve FHIR profiles. More impressive than that- he created an interactive sandbox for builders!! We mapped each operation against the clinical tracks, walked through the payment model line by line, and sketched out how we would integrate this into our software infrastructure. Then we wrote it up on The Techy Surgeon! I still believe the most compelling component to this model is the partnership architecture. An MSK practice collecting $180 per care episode while forgoing downstream surgical revenue of FFS billing is thin. Impractical as a standalone play. But an MSK practice or PT group that functions as the specialty care node in a broader value-based network -- receiving referrals from ACOs, coordinating with rehab partners for triage and PROM collection, with co-management payments flowing to the upstream entities that feed the pipeline and expanding their tech enabled capabilities -- that's a different model entirely. The ACCESS Model doesn't reward isolation. It rewards coordination. And the participants who build the network around them will be the ones who make the economics work. We're in the MSK and Behavioral Health tracks. The MSK improvement-only design with early success reporting at Day 185 maps directly to what we've built at RevelAi Health -- PROM trajectory monitoring, clinically informed AI powered patient engagement, distributed care coordination, partner data exchange. And the BH track opens an adjacent market where the same partnership-dependent architecture applies and the need for coordination infrastructure is even more acute. And yes, without AI -- it becomes impossible for this program to work for the ACCESS participant. Will this program actually enhance access? That remains to be seen, but we're determined to try. The full analysis and sandbox on The Techy Surgeon (link in comments). If you're an ACO, PT group, or specialty practice exploring ACCESS and want to talk partnership structures: hello@revelaihealth.com or visit us at the MSK ACCESS website (link in comments) #ACCESSModel #CMS #ValueBasedCare #FHIR #MSK #BehavioralHealth #DigitalHealth #CareCoordination

40

7 Comments

Anthropic Opus / Sonnet Models Push Agent Capabilities Forward Trend: Anthropic rolled out Opus/Sonnet updates improving coding, long context and agentic workflows. Why it matters: Stronger agents reduce developer toil but increase the need for agent governance and audit trails. Question: Would you deploy agents to triage tickets or keep humans first for context-sensitive work? 🔁 Repost if agents are changing your engineering flow 🔔 Follow me for model and agent governance signals 🌟 Takeaway: Agents can scale teams, pair them with strict review and traceability

3