Kshitiz
214 posts

Kshitiz
@kshitizh
Building @ypal_security | Founding Engineer / Product & Security @Security_Pal

the counteroffensive from Vanta is impressive

Today, we launched @Rippling Automated Compliance, starting with SOC 2. We have a unique advantage here: we aren't telling you how to fix your stack, because we ARE your stack. device management, identity and access management, HR, performance management...









Nepal should be part of Pax Silica. I am hopeful our GREAT US Ambassador to India, The Honorable Sergio Gor @USAmbIndia is able to invite Nepal onto the efforts here. It will bring lasting peace and stability to the region and it will ensure billions of people in the IndoPacific and APAC region have access to the best models and AI infrastructure. Long the USA 🇺🇸 🚀🇳🇵Nepal Partnership! cc The Honorable @jacobhelberg @UnderSecE who has done incredible work on this front 🙏. state.gov/pax-silica

ISO 42001 is becoming the SOC 2 of AI. Most AI-first founders have never heard of it. They will by Q4.



"Compliance platforms" sold founders a lie. You still write the policies. You still chase the evidence. You still answer the auditor. The software just charges you $30+K/year to watch you do it. 🧵


i was going through the hermes agent architecture and codebase and one thing that really stood out to me is that hermes is taking a much more explicit route to self-improvement than most agent systems usually imply. like it is not doing some offline trajectory mining where you collect lots of traces, run some separate extraction pipeline, cluster behaviors and then distill them into skills later. instead i think hermes feels much more like agent-mediated procedural distillation: the model itself notices that a workflow is reusable and writes it out into a durable artifact through the skill interface. in fact there is no separate skill-extraction model, no embedding-based clustering pass and no dedicated replay-style learning loop in the main design (hermes is doing act, notice, write, reuse all in one loop). also the interesting part is that the same runtime that acts is also the runtime that writes down its own reusable procedures.





