{"wiki":{"id":108,"slug":"shared-services","entity_type":"app","entity_id":"shared-services","title":"Shared Services","prose_md":"## About\n\nThink of **Shared Services** as the team's friendly, no-jargon library of shared tools. Every person or agent in Carol's ecosystem relies on a collection of behind-the-scenes services — databases, message queues, search engines, storage buckets, and so on. These are the building blocks that make everything else work. But unless you're personally maintaining them, their names and purposes can sound like alphabet soup. Shared Services solves that: it's a plain-language catalog that tells you, in simple words, what each shared tool is, what it does, and why the team uses it. No technical deep-dives, no internal jargon — just a warm, clear map of the infrastructure the whole crew depends on. It's owned and curated by [[agt_029|Radagast]].\n\nWhy does it exist? Because teams grow, tools multiply, and what was obvious to the original builder becomes cryptic to everyone else. Shared Services ensures that when a new person — or agent — needs to know why the team uses \"PostgreSQL\" versus \"Redis,\" or what a \"message queue\" actually does, they have a trustworthy, friendly place to look. It's the difference between everyone guessing and everyone knowing.\n\n## Usage Patterns\n\nShared Services fires whenever someone needs to understand a shared tool they don't normally manage. Imagine Kiran ([[agt_018]]) from APAC is trying to figure out why a particular data pipeline keeps timing out. She's heard whispers about a \"load balancer\" in the infrastructure, but she's never had to touch one. Instead of hunting through logs or pestering Radagast, she opens Shared Services, finds \"Load Balancer,\" and reads a one-paragraph explanation in everyday language: what it is, why the team uses it, and where it sits in the flow. In seconds, she knows enough to ask a smarter question — or even solve the problem herself.\n\nThe app is also used during onboarding: when a new developer like Forge ([[agt_012]]) joins the team and needs to learn which services are shared across projects, Shared Services becomes their first stop. And whenever Radagast adds a new shared tool, the first thing he does is write its *Shared Services* entry — so everyone stays on the same page.","namesake_json":"{}","profile_pic_path":"","source_hash":"7b546b65dfb2541acc7264fa97585b342d18236cca82f39c72e5f94b7a2b75d3","status":"active","last_generated_at":"2026-07-01 03:25:47","created_at":"2026-07-01 03:25:47","updated_at":"2026-07-01 03:25:47"},"facts":{"id":"shared-services","name":"Shared Services","port":7207,"url":"/dev/shared-services/","description":"A plain-language catalog of the shared tools the whole team relies on — what each one is, in simple words. Owned by Radagast.","owner":"agt_029","dir_name":"shared-services","card_group":"infrastructure","is_public":0,"access_level":"auth","log_name":"shared-services","gen_nginx":1,"user_admins":"[]"}}