@fx-data/ai-diagnostics 0.1.20261026070913 → 0.1.20261107142011

package/content/knowledge/update/diagnostic/observability/lookups/analysis-update-after-commit-delivery.json

@@ -1,131 +0,0 @@
-{
-  "lookup_id": "analysis-update-after-commit-delivery",
-  "logical_event": "frontier-published-after-visibility",
-  "lifecycle_stage": "queue",
-  "graph_kind": "execution",
-  "signal_status": "source-confirmed",
-  "signals": {
-    "span_names": [],
-    "attribute_keys": [],
-    "structured_fields": [],
-    "log_signatures": [
-      "send nodeTaskId {} , executeId {}"
-    ],
-    "metric_names": []
-  },
-  "service_scope": [
-    "main-server"
-  ],
-  "produced_when": "AbstractDispatchHandler emits this exact template after producer.sendNodeTask returns and after any PENDING_SENT flag update; an active transaction schedules that action after commit, while the no-transaction path runs immediately.",
-  "correlations": [
-    {
-      "edge_id": "edge-execution-detail-to-publication",
-      "from_unit": "execution-detail",
-      "to_unit": "queue-publication",
-      "correlation_keys": [
-        "execution detail ID"
-      ],
-      "semantics": "A message containing the detail ID, node ID, and context is published after detail visibility.",
-      "asynchronous": true,
-      "correlation_status": "source-confirmed-payload",
-      "durability": "detail-and-message-lifetime",
-      "coverage_limit": "No separate publication ID is created."
-    },
-    {
-      "edge_id": "edge-publication-to-attempt",
-      "from_unit": "queue-publication",
-      "to_unit": "execution-attempt",
-      "correlation_keys": [
-        "execution detail ID"
-      ],
-      "semantics": "A main-queue delivery starts one consumer attempt for the payload detail.",
-      "asynchronous": true,
-      "correlation_status": "source-confirmed-payload",
-      "durability": "message-lifetime",
-      "coverage_limit": "The detail ID cannot distinguish repeated deliveries or attempt numbers."
-    },
-    {
-      "edge_id": "edge-ready-recovery-to-publication",
-      "from_unit": "requeue",
-      "to_unit": "queue-publication",
-      "correlation_keys": [
-        "execution detail ID"
-      ],
-      "semantics": "Ready inspection republishes a still-PENDING_SENT root detail under its existing detail ID.",
-      "asynchronous": true,
-      "correlation_status": "source-confirmed-durable",
-      "durability": "frontier-lifetime",
-      "coverage_limit": "The edge does not apply to SENT child details."
-    }
-  ],
-  "counting_unit": "queue-publication",
-  "input_units": [
-    "execution-detail"
-  ],
-  "output_units": [
-    "queue-publication"
-  ],
-  "state_owner": "Dispatch publisher plus execution-detail send flag.",
-  "reads": [
-    "detail ID, node ID, and serialized context",
-    "transaction synchronization state"
-  ],
-  "writes": [
-    "node-task message",
-    "root detail send flag from PENDING_SENT to SENT"
-  ],
-  "success_condition": "Publication occurs only after the corresponding detail is visible, and the root send flag records successful publication.",
-  "failure_recovery": [
-    {
-      "branch": "after-commit executor rejects or publication fails for a root detail",
-      "outcome": "The error is logged and the PENDING_SENT root remains eligible for ready inspection.",
-      "recovery": "Ready inspection republishes the root detail and marks it SENT."
-    },
-    {
-      "branch": "publication succeeds but send-flag update fails",
-      "outcome": "The message may be delivered while the detail remains PENDING_SENT.",
-      "recovery": "Ready inspection may republish; duplicate suppression remains a separate consumer concern."
-    },
-    {
-      "branch": "child publication fails",
-      "outcome": "Child details are created with SENT, so the PENDING_SENT ready inspector does not cover this branch.",
-      "recovery": "No equivalent source-confirmed recovery path was found within coverage."
-    }
-  ],
-  "source_evidence_grade": "source-confirmed-with-enabled-test",
-  "edge_refs": [
-    "edge-execution-detail-to-publication",
-    "edge-publication-to-attempt",
-    "edge-ready-recovery-to-publication"
-  ],
-  "field_presence_preflight": [
-    {
-      "field": "send nodeTaskId {} , executeId {}",
-      "signal_type": "log-signature",
-      "required": true,
-      "failure_effect": "needs_revalidation"
-    }
-  ],
-  "coverage_limits": [
-    "A publication count is not an attempt count, because the broker may redeliver and recovery may republish.",
-    "The template has no publication ID, broker acknowledgement, route, or attempt ordinal; it confirms the producer call returned, not broker delivery.",
-    "The identical template in INIT recovery is a separate source anchor and must not be conflated by text alone."
-  ],
-  "invalidators": [
-    {
-      "kind": "revision-change",
-      "event": "The frozen main-server revision or build anchor changes.",
-      "effect": "needs_revalidation"
-    },
-    {
-      "kind": "signal-drift",
-      "event": "A named span, attribute, structured field, log template, metric, or its production condition changes.",
-      "effect": "needs_revalidation"
-    },
-    {
-      "kind": "scope-change",
-      "event": "The dispatch, update, queue, listener, or engine-handoff service boundary changes.",
-      "effect": "needs_revalidation"
-    }
-  ]
-}

package/content/knowledge/update/diagnostic/observability/lookups/analysis-update-attempt-consumed.json

@@ -1,175 +0,0 @@
-{
-  "lookup_id": "analysis-update-attempt-consumed",
-  "logical_event": "execution-attempt-consumed",
-  "lifecycle_stage": "consumer",
-  "graph_kind": "execution",
-  "signal_status": "source-confirmed",
-  "signals": {
-    "span_names": [
-      "update"
-    ],
-    "attribute_keys": [
-      "corpId",
-      "tableId"
-    ],
-    "structured_fields": [],
-    "log_signatures": [
-      "handle nodeTaskId {}, executeId {}"
-    ],
-    "metric_names": []
-  },
-  "service_scope": [
-    "main-server"
-  ],
-  "produced_when": "The main Rabbit listener enters DispatchTraceContext.doUpdate for each delivery, which creates one linked update consumer span; DispatchExecuteHandler logs the node and execution-detail IDs at handler entry.",
-  "correlations": [
-    {
-      "edge_id": "edge-publication-to-attempt",
-      "from_unit": "queue-publication",
-      "to_unit": "execution-attempt",
-      "correlation_keys": [
-        "execution detail ID"
-      ],
-      "semantics": "A main-queue delivery starts one consumer attempt for the payload detail.",
-      "asynchronous": true,
-      "correlation_status": "source-confirmed-payload",
-      "durability": "message-lifetime",
-      "coverage_limit": "The detail ID cannot distinguish repeated deliveries or attempt numbers."
-    },
-    {
-      "edge_id": "edge-attempt-to-capacity-deferral",
-      "from_unit": "execution-attempt",
-      "to_unit": "requeue",
-      "correlation_keys": [
-        "execution detail ID",
-        "tenant ID"
-      ],
-      "semantics": "An attempt that cannot obtain a tenant permit publishes the same detail to the slow route before node work.",
-      "asynchronous": true,
-      "correlation_status": "source-confirmed-payload",
-      "durability": "message-lifetime",
-      "coverage_limit": "The deferral has no independent requeue ID."
-    },
-    {
-      "edge_id": "edge-attempt-to-lock-requeue",
-      "from_unit": "execution-attempt",
-      "to_unit": "requeue",
-      "correlation_keys": [
-        "execution detail ID",
-        "node table ID",
-        "update chain ID"
-      ],
-      "semantics": "A node-running lock timeout republishes the same execution detail to the main queue.",
-      "asynchronous": true,
-      "correlation_status": "source-confirmed-payload",
-      "durability": "message-lifetime",
-      "coverage_limit": "No attempt or requeue ID is added."
-    },
-    {
-      "edge_id": "edge-attempt-to-merge",
-      "from_unit": "execution-attempt",
-      "to_unit": "merge-decision",
-      "correlation_keys": [
-        "execution detail ID",
-        "node table ID"
-      ],
-      "semantics": "An attempt holding the node lock queries eligible same-node frontier details and selects a merge result.",
-      "asynchronous": false,
-      "correlation_status": "source-confirmed-in-process",
-      "durability": "execution-scope",
-      "coverage_limit": "No merge-decision ID is persisted."
-    }
-  ],
-  "counting_unit": "execution-attempt",
-  "input_units": [
-    "queue-publication",
-    "execution-detail"
-  ],
-  "output_units": [
-    "execution-attempt"
-  ],
-  "state_owner": "Main node-task consumer and dispatch execution handler.",
-  "reads": [
-    "message detail ID, node ID, and serialized context",
-    "tenant capacity",
-    "chain-node duplicate flag",
-    "node execution lock"
-  ],
-  "writes": [
-    "temporary capacity permit and duplicate-suppression state",
-    "later branch-specific publications or node results"
-  ],
-  "success_condition": "One main-consumer delivery is classified into capacity deferral, duplicate suppression, lock requeue, merge and work, infrastructure recovery, or ignored failure.",
-  "failure_recovery": [
-    {
-      "branch": "lock conflict",
-      "outcome": "The same detail is republished to the main queue.",
-      "recovery": "A later main-consumer delivery is a new attempt with no native attempt ID."
-    },
-    {
-      "branch": "infrastructure or dependency stop condition",
-      "outcome": "The delivery is rejected to dead-letter recovery after clearing the duplicate flag.",
-      "recovery": "Dead-letter recovery republishes when the execution checker succeeds."
-    },
-    {
-      "branch": "other unhandled consumer exception",
-      "outcome": "The listener logs and ignores the execution info.",
-      "recovery": "No generic business retry is claimed."
-    }
-  ],
-  "source_evidence_grade": "source-confirmed",
-  "edge_refs": [
-    "edge-publication-to-attempt",
-    "edge-attempt-to-capacity-deferral",
-    "edge-attempt-to-lock-requeue",
-    "edge-attempt-to-merge"
-  ],
-  "field_presence_preflight": [
-    {
-      "field": "update",
-      "signal_type": "span-name",
-      "required": true,
-      "failure_effect": "needs_revalidation"
-    },
-    {
-      "field": "corpId",
-      "signal_type": "attribute",
-      "required": false,
-      "failure_effect": "needs_revalidation"
-    },
-    {
-      "field": "tableId",
-      "signal_type": "attribute",
-      "required": false,
-      "failure_effect": "needs_revalidation"
-    },
-    {
-      "field": "handle nodeTaskId {}, executeId {}",
-      "signal_type": "log-signature",
-      "required": true,
-      "failure_effect": "needs_revalidation"
-    }
-  ],
-  "coverage_limits": [
-    "The detail ID is reused and no attempt number or attempt ID is persisted.",
-    "No attempt ID or ordinal exists; repeated deliveries reuse the execution-detail ID.",
-    "corpId and tableId are set on the pre-existing current span before the linked update span is created, so queries must preflight their actual span placement."
-  ],
-  "invalidators": [
-    {
-      "kind": "revision-change",
-      "event": "The frozen main-server revision or build anchor changes.",
-      "effect": "needs_revalidation"
-    },
-    {
-      "kind": "signal-drift",
-      "event": "A named span, attribute, structured field, log template, metric, or its production condition changes.",
-      "effect": "needs_revalidation"
-    },
-    {
-      "kind": "scope-change",
-      "event": "The dispatch, update, queue, listener, or engine-handoff service boundary changes.",
-      "effect": "needs_revalidation"
-    }
-  ]
-}

package/content/knowledge/update/diagnostic/observability/lookups/analysis-update-candidate-root-filter.json

@@ -1,119 +0,0 @@
-{
-  "lookup_id": "analysis-update-candidate-root-filter",
-  "logical_event": "candidate-root-filtered",
-  "lifecycle_stage": "entry",
-  "graph_kind": "logical",
-  "signal_status": "source-confirmed",
-  "signals": {
-    "span_names": [],
-    "attribute_keys": [],
-    "structured_fields": [],
-    "log_signatures": [
-      "table don't need update, tableId = {}, tenantId = {}",
-      "table is not exist in db, can't update, tableId = {}, tenantId = {}"
-    ],
-    "metric_names": []
-  },
-  "service_scope": [
-    "main-server"
-  ],
-  "produced_when": "Dispatchers emits one stable template when a common entry filter removes an existing table that needs no update, and another when the candidate table is absent.",
-  "correlations": [
-    {
-      "edge_id": "edge-request-to-candidate-root",
-      "from_unit": "update-request",
-      "to_unit": "candidate-root",
-      "correlation_keys": [
-        "in-process request object and candidate collection"
-      ],
-      "semantics": "The producer invocation supplies the candidate table set evaluated by the entry.",
-      "asynchronous": false,
-      "correlation_status": "source-confirmed-in-process",
-      "durability": "not-durable",
-      "coverage_limit": "There is no dedicated request ID."
-    },
-    {
-      "edge_id": "edge-candidate-to-effective-root",
-      "from_unit": "candidate-root",
-      "to_unit": "effective-root",
-      "correlation_keys": [
-        "table ID within the same dispatch invocation"
-      ],
-      "semantics": "Entry eligibility and ancestor reduction determine whether a candidate remains an effective root.",
-      "asynchronous": false,
-      "correlation_status": "source-confirmed-in-process",
-      "durability": "not-durable",
-      "coverage_limit": "Filtered candidates are not stored as a durable ledger."
-    }
-  ],
-  "counting_unit": "candidate-root",
-  "input_units": [
-    "candidate-root"
-  ],
-  "output_units": [
-    "eligible-candidate-root"
-  ],
-  "state_owner": "Analysis-update entry filtering.",
-  "reads": [
-    "asset table records",
-    "app-table classification",
-    "current metadata and need-update rules"
-  ],
-  "writes": [
-    "in-memory eligible root set"
-  ],
-  "success_condition": "Every candidate is retained or removed by current eligibility behavior before dispatch root reduction.",
-  "failure_recovery": [
-    {
-      "branch": "candidate table is absent or an app table",
-      "outcome": "Candidate is removed.",
-      "recovery": "No execution work for that candidate."
-    },
-    {
-      "branch": "need-update evaluation fails",
-      "outcome": "The entry falls back to allUpdates for the candidate instead of proving no work.",
-      "recovery": "Dispatch continues conservatively."
-    }
-  ],
-  "source_evidence_grade": "source-confirmed",
-  "edge_refs": [
-    "edge-request-to-candidate-root",
-    "edge-candidate-to-effective-root"
-  ],
-  "field_presence_preflight": [
-    {
-      "field": "table don't need update, tableId = {}, tenantId = {}",
-      "signal_type": "log-signature",
-      "required": false,
-      "failure_effect": "needs_revalidation"
-    },
-    {
-      "field": "table is not exist in db, can't update, tableId = {}, tenantId = {}",
-      "signal_type": "log-signature",
-      "required": false,
-      "failure_effect": "needs_revalidation"
-    }
-  ],
-  "coverage_limits": [
-    "Entry variants may intentionally bypass the common eligibility helper; the inventory of producers belongs to Phase 1.",
-    "These templates cover only the common need-update and absent-table removal branches; retained candidates and entry variants that bypass this helper have no per-candidate signal.",
-    "The placeholders are not correlation identities; table and tenant similarity must not join separate requests."
-  ],
-  "invalidators": [
-    {
-      "kind": "revision-change",
-      "event": "The frozen main-server revision or build anchor changes.",
-      "effect": "needs_revalidation"
-    },
-    {
-      "kind": "signal-drift",
-      "event": "A named span, attribute, structured field, log template, metric, or its production condition changes.",
-      "effect": "needs_revalidation"
-    },
-    {
-      "kind": "scope-change",
-      "event": "The dispatch, update, queue, listener, or engine-handoff service boundary changes.",
-      "effect": "needs_revalidation"
-    }
-  ]
-}

package/content/knowledge/update/diagnostic/observability/lookups/analysis-update-capacity-deferred.json

@@ -1,121 +0,0 @@
-{
-  "lookup_id": "analysis-update-capacity-deferred",
-  "logical_event": "attempt-capacity-deferred",
-  "lifecycle_stage": "queue",
-  "graph_kind": "execution",
-  "signal_status": "source-confirmed",
-  "signals": {
-    "span_names": [],
-    "attribute_keys": [],
-    "structured_fields": [],
-    "log_signatures": [
-      "Tenant limit exceeded: tenant {}, nodeTaskId {}, executeId {}"
-    ],
-    "metric_names": [
-      "update_tasks"
-    ]
-  },
-  "service_scope": [
-    "main-server"
-  ],
-  "produced_when": "DispatchExecuteHandler emits the stable capacity template after sendToSlowNodeTask when tenantLimit.tryAcquire returns null; update_tasks is a concurrent-handler gauge updated around the attempt.",
-  "correlations": [
-    {
-      "edge_id": "edge-attempt-to-capacity-deferral",
-      "from_unit": "execution-attempt",
-      "to_unit": "requeue",
-      "correlation_keys": [
-        "execution detail ID",
-        "tenant ID"
-      ],
-      "semantics": "An attempt that cannot obtain a tenant permit publishes the same detail to the slow route before node work.",
-      "asynchronous": true,
-      "correlation_status": "source-confirmed-payload",
-      "durability": "message-lifetime",
-      "coverage_limit": "The deferral has no independent requeue ID."
-    },
-    {
-      "edge_id": "edge-capacity-deferral-to-attempt",
-      "from_unit": "requeue",
-      "to_unit": "execution-attempt",
-      "correlation_keys": [
-        "execution detail ID"
-      ],
-      "semantics": "When capacity is available, the slow consumer republishes the same detail to the main queue for a later attempt.",
-      "asynchronous": true,
-      "correlation_status": "source-confirmed-payload",
-      "durability": "message-lifetime",
-      "coverage_limit": "Intermediate slow-queue cycles are requeues, not main-consumer attempts."
-    }
-  ],
-  "counting_unit": "requeue",
-  "input_units": [
-    "execution-attempt"
-  ],
-  "output_units": [
-    "requeue"
-  ],
-  "state_owner": "Tenant capacity semaphore and slow-node queue consumer.",
-  "reads": [
-    "effective tenant limit",
-    "available tenant permits"
-  ],
-  "writes": [
-    "slow-queue publication or main-queue republication",
-    "temporary renewable permit when capacity is acquired"
-  ],
-  "success_condition": "Capacity-unavailable work is deferred without executing node work and is returned to the main queue only after capacity becomes available.",
-  "failure_recovery": [
-    {
-      "branch": "capacity remains unavailable",
-      "outcome": "The slow consumer republishes to the slow queue.",
-      "recovery": "A later slow-queue cycle rechecks capacity."
-    },
-    {
-      "branch": "shutdown signal while handling slow work",
-      "outcome": "The slow consumer republishes to the slow queue.",
-      "recovery": "Processing resumes after a later delivery."
-    }
-  ],
-  "source_evidence_grade": "source-confirmed",
-  "edge_refs": [
-    "edge-attempt-to-capacity-deferral",
-    "edge-capacity-deferral-to-attempt"
-  ],
-  "field_presence_preflight": [
-    {
-      "field": "Tenant limit exceeded: tenant {}, nodeTaskId {}, executeId {}",
-      "signal_type": "log-signature",
-      "required": true,
-      "failure_effect": "needs_revalidation"
-    },
-    {
-      "field": "update_tasks",
-      "signal_type": "metric",
-      "required": false,
-      "failure_effect": "needs_revalidation"
-    }
-  ],
-  "coverage_limits": [
-    "Slow-queue cycles are requeue operations and are not main-consumer node attempts.",
-    "update_tasks is a global current-work gauge rather than a capacity-decision counter and has no tenant, detail, or requeue identity.",
-    "The template proves one slow-route call but not broker acceptance or a unique capacity-cycle ID."
-  ],
-  "invalidators": [
-    {
-      "kind": "revision-change",
-      "event": "The frozen main-server revision or build anchor changes.",
-      "effect": "needs_revalidation"
-    },
-    {
-      "kind": "signal-drift",
-      "event": "A named span, attribute, structured field, log template, metric, or its production condition changes.",
-      "effect": "needs_revalidation"
-    },
-    {
-      "kind": "scope-change",
-      "event": "The dispatch, update, queue, listener, or engine-handoff service boundary changes.",
-      "effect": "needs_revalidation"
-    }
-  ]
-}