<- Back
Comments (48)
- finnborgeThis feels to me like a lovely example of both high-quality systems design and information theory. From my perspective, one of the more abstractly interesting thoughts surfaced by this write-up is the degree to which you've "encoded" a highly complex set of relationships through use of metaphor.That type of encoding (starting with the statement: you're at a teaching hospital) is profoundly more efficient than having to deeply and reliably articulate what each of the various roles your agents embody are, let alone their interactions.Perhaps there is more room for any of us to consider what existing systems or identities are described abundantly in training sets and can be leveraged to ritualistically encode these social/civic/cultural dynamics saying: "act as though you're ___." Not exactly a new point, but one this write-up certainly is pulling me towards.Thank you for sharing and the care you put into writing this!
- K0baltI set different kinds of structures for different projects, Complete with setting and ambiance. It’s like agents work better if they are role-playing. It’s extremely disorienting and people with marginal mental stability are going to really have a bad time. What have we wrought?
- anonymous908213I can think of nothing I'd like to use less than a database or filesystem vibecoded by Gas Town-flavored psychosis. Roleplaying with LLMs is not the secret to producing amazing code.
- james_marksA hint at why GitHub actions have been unreliable. How many teams are running factories like this on GH infra now?
- fathermarzI’m surprised at the reasoning behind using the most expensive model which likely led to the “doing too much”. I think it would have been nice to have A/B tested different hospital setups in order to maximize not only efficiency but to see where the strength of each model started to emerge in a given role.Fable feels like overkill for this also.
- kinduffSince we are all building our version of this, what mistakes did you made until you arrived to a well-balanced solution? I really like that you know how much an issue is, because then you can start optimizing.
- ajstormRafi and I, who authored this post, will be hanging out here for any questions people may have.
- anonundefined
- dingaling911Maybe I missed it, but I didn't really see anything about the long term quality or maintainability of the code. All I see is agent agent agent.
- mncharityOne role I didn't see was patient advocate/representative? That might be another approach to non-convergence - "how is this going?" and escalation.
- drc500freeI absolutely love how you are able to pull so much latent behavior from the underlying LLM. I wonder what other analogies can be pulled into agentic coding that come baked into the existing weights.
- jordanlewisGreat post!One thing I've been experimenting with in my own agent orchestration system is an agent that hangs around and does post-merge acceptance testing after the work ships. Any plans to add a follow-up phase? Travel nurse?
- zmjNice writeup. Structured handoffs and external plan reviews are good takeaways.
- singularity2001congenially my agents started calling bugs gaps
- VeeloxYou give a very precise measure of redundancy in the skills. Can you give a bit more detail in how you decided you needed to audit them and how you went about it? Was it fully agent driven? Mostly human?
- anonundefined
- Spooky23Reminds me of the “surgical team” development model in the Mythical Man Month.
- git_rancherThe patient “leaves” when the bug is fixed?
- khotem[flagged]
- ContinuityLab[flagged]