{"graphSha256":"f29d7b1eedeb88387238d2abda347f810d2179c5fdbead47c3ef48507ab20ca5","node":{"id":"N1805","type":"ficha","title":"xSeil orchestration","url":"https://dakleyer.github.io/perspective-beyond/sources/xseil-orchestration-n1805/","original":"https://jubap.net/xseil-orchestration/","aliases":[],"clusters":["net"],"tags":["agentes","documentacion","movilidad"],"summary":"","commit":null,"sourcePath":null,"commitUrl":null,"documentId":"doc-7623f7089eace86ac4","tagWeights":{"agentes":0.4286,"documentacion":0.2381,"movilidad":0.3333},"reading":"Before agent frameworks became mainstream, deployed mission-critical systems implemented centralized equivalents of behaviours now attributed to multi-agent architectures. We document three such mechanisms in xSeil (2016–2017): a pacing daemon computing a multiplicative saturation index over destination pressure and issuing physical speed commands to vehicles through iterative marginal load-shifting; a scenario system with a full simulation twin evaluating counterfactual plans against a shared persistent configuration library; and an evidence-gated escalation ladder that widens search scope only on demonstrated insufficiency. We show that the daemon’s saturation index is structurally identical to the fragility measure F = P(anomalies) × P(propagation) formalized by the same group a decade later, map each mechanism to its modern agentic counterpart as explicit retrospective interpretation, and specify a benchmark protocol for the open empirical question of what decentralization buys — and costs — against a centralized baseline possessing global visibility and deterministic auditability.\n\nA companion Technical Code Annex supplies the verbatim production code behind every claim below — the control-loop state machine, the geofence→delay→forward-propagation sensor, and the saturation-index→speed-command actuator — so the closed loop and the fragility identity are auditable, not narrated.","readingSource":{"url":"https://jubap.net/xseil-orchestration/","section":"Abstract","observed":"2026-11-04","sourceSha256":"9ea473fcff7604fa51ca771c6d36ff7216572e08501463a472e8a1297ac91773"},"readingSummary":"Before agent frameworks became mainstream, deployed mission-critical systems implemented centralized equivalents of behaviours now attributed to multi-agent architectures.","contextTokens":322},"relations":[["apoyo:N1805:C06","N1805","C06","documenta el concepto","",null,"apoyo",""],["apoyo:N1805:C44","N1805","C44","documenta el concepto","",null,"apoyo",""],["apoyo:N1805:C45","N1805","C45","documenta el concepto","",null,"apoyo",""],["documento:G023","GH023","N1805","analogy only","The later cartography distinguishes semantic compatibility from shared-resource dependence, a useful retrospective lens on xSeil’s state-dependent allocation.",null,"documento","xSeil no se convierte por esta comparación en una implementación distribuida de MSCA."],["documento:G071","N1805","GH023","analogy only","The historical allocation mechanism can inspire a later cartographic treatment of shared dependencies without being relabeled as an MSCA deployment.",null,"documento","Se propone una comparación posterior, no una prueba de influencia causal documentada para cada decisión de arquitectura."],["documento:R096","N1805","N1822","editorial comparison","For a complementary reading, see [Pre-Agentic Orchestration: the canonical paper](https://jubap.net/xseil-agentic-features/).",null,"documento",""]]}