{"graphSha256":"f29d7b1eedeb88387238d2abda347f810d2179c5fdbead47c3ef48507ab20ca5","node":{"id":"N1274","type":"ficha","title":"Tiger Team Models","url":"https://dakleyer.github.io/perspective-beyond/sources/tiger-team-models-n1274/","original":"https://jubap.net/tiger-team-models/","aliases":[],"clusters":["net"],"tags":["control-minimo","integridad-ia","transformacion"],"summary":"","commit":null,"sourcePath":null,"commitUrl":null,"documentId":"doc-e5c993c074c54f2957","tagWeights":{"control-minimo":0.1579,"integridad-ia":0.3684,"transformacion":0.4737},"reading":"Tiger Teams appear in several traditions, from expert swarms and aerospace problem solving to cybersecurity and Skunk Works. The JubAp.Net model is differentiated by continuous operational accountability across intervention and stabilisation.\n\nIn some organizations, it refers to a group of experts assembled quickly to solve a critical problem. In others, it refers to a cybersecurity unit, an engineering task force, a crisis response group, a special product team, or a senior consulting squad created to unblock a complex initiative.\n\nThe expression has a serious technical lineage. It has been associated with aerospace, NASA-style engineering problem solving, mission assurance, security testing, enterprise troubleshooting and high-stakes technical intervention. NASA, for example, has used Tiger Team approaches through engineering and safety structures for complex technical problems, while the broader aerospace and defence world has long relied on small, high-capability teams for problems where normal structures move too slowly.\n\nSome are highly mature. Some are informal. Some are mostly tactical. Some are deeply procedural. Some are brilliant but fragile. Some are little more than a premium label for gathering expensive experts around a hard problem.\n\nUnderstanding the different models is important because the same word can describe very different operating realities.","readingSource":{"url":"https://jubap.net/tiger-team-models/","section":"Opening paragraphs","observed":"2026-11-04","sourceSha256":"406a9761618ec6d2a60e972d9afb65cfac1bca0373a9b3bcf87bbfb0e13b0bd4"},"readingSummary":"Tiger Teams appear in several traditions, from expert swarms and aerospace problem solving to cybersecurity and Skunk Works.","contextTokens":310},"relations":[["apoyo:N1274:C37","N1274","C37","documenta el concepto","",null,"apoyo",""],["apoyo:N1274:C41","N1274","C41","documenta el concepto","",null,"apoyo",""],["apoyo:N1274:C51","N1274","C51","documenta el concepto","",null,"apoyo",""],["apoyo:N1274:C88","N1274","C88","documenta el concepto","",null,"apoyo",""],["documento:M012","N1274","T886","analogy only","An integrated mission team and a federated integrity function solve different coordination problems and need not share the same governance structure.",null,"documento","La taxonomía de equipos y la propuesta de función de AI Integrity tienen escalas y responsabilidades diferentes."],["documento:F046","N1274","T886","analogy only","A mission team and a federated integrity function can share explicit decision interfaces without requiring the same organizational structure.",null,"documento","Los modelos Tiger Team no se ordenan en una jerarquía universal; cada tradición responde a un problema y alcance diferentes."],["documento:F047","N1274","T2729","candidate transfer","Team configuration can be assessed against the mission's required capabilities and response obligations before comparing the burden of alternative structures.",null,"documento","MSCA no prescribe una plantilla de personal ni demuestra que el equipo más pequeño sea suficiente o superior."],["documento:R127","N1274","N1276","editorial comparison","For a complementary reading, see [The Tiger Team maturity lens](https://jubap.net/tiger-team-maturity-model/).",null,"documento",""]]}