{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreib6i5u2htpgrmdlbxa7lcjvbrw56eywkyb4urrlrumiaecvjqhio4",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mkhlvbmive52"
  },
  "path": "/t/the-periodic-table-of-ai-architecture-assigning-clear-roles-to-scattered-ai-findings/175016#post_8",
  "publishedAt": "2026-04-27T07:05:14.000Z",
  "site": "https://discuss.huggingface.co",
  "textContent": "That makes sense as a teaching device.\n\nMy concern is not that metaphor has no value. My concern is that metaphor can hide the hard part.\n\nFor agent systems, the useful question is not whether the same pattern can be renamed across quantum, finance, cooking, biology, or institutions.\n\nThe useful question is:\n\nWhat becomes a durable object?\nWhat owns state?\nWhat validates transitions?\nWhat gets logged?\nWhat can be replayed?\nWhat can recover after failure?\nWhat policy is enforced at runtime?\nWhat evidence proves the system is doing less prompt replay?\nWhat changes in behavior when the framework is implemented?\n\nThat is where I separate vocabulary from architecture.\n\nA reusable metaphor can help people understand a system, but it does not itself create memory, persistence, routing, trace, governance, recovery, or reliable long horizon work.\n\nThose have to exist as runtime components.",
  "title": "The Periodic Table of AI Architecture: Assigning Clear Roles to Scattered AI Findings"
}