open-mind-mcp-server/examples/sample-open-mind-artifacts/glossary.json at main · HelloThisWorld/open-mind-mcp-server · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
{
  "schemaVersion": "1.0.0",
  "entries": [
    {
      "term": "Backpressure",
      "kind": "concept",
      "description": "The mechanism that slows order intake when the event pipeline falls behind.",
      "evidence": [
        {
          "file": "README.md",
          "line": 27,
          "snippet": "| Backpressure | The mechanism that slows order intake when the event pipeline falls behind. |"
        }
      ],
      "confidence": "high"
    },
    {
      "term": "DLQ",
      "kind": "concept",
      "description": "dead letter queue",
      "evidence": [
        {
          "file": "docs/GLOSSARY.md",
          "line": 11,
          "snippet": "- **RetryPolicy**: The exponential backoff schedule for failed event deliveries: attempts wait 1s, 4s, 16s, 64s, then 256s before the event is parked in the dead letter queue (DLQ)."
        }
      ],
      "confidence": "high"
    },
    {
      "term": "EventPublisher",
      "kind": "class",
      "description": "Delivers domain events to subscribers with at-least-once semantics; failed deliveries are retried on the backoff schedule and parked in the dead letter queue when attempts are exhausted.",
      "evidence": [
        {
          "file": "docs/GLOSSARY.md",
          "line": 8,
          "snippet": "- **EventPublisher**: Delivers domain events to subscribers with at-least-once semantics; failed deliveries are retried on the backoff schedule and parked in the dead letter queue when attempts are ex"
        }
      ],
      "confidence": "high"
    },
    {
      "term": "IdempotencyKey",
      "kind": "concept",
      "description": "A client-supplied unique key sent with order creation requests; the stored first response is replayed for repeated submissions so duplicate orders are never created.",
      "evidence": [
        {
          "file": "docs/GLOSSARY.md",
          "line": 12,
          "snippet": "- **IdempotencyKey**: A client-supplied unique key sent with order creation requests; the stored first response is replayed for repeated submissions so duplicate orders are never created."
        }
      ],
      "confidence": "high"
    },
    {
      "term": "NotificationService",
      "kind": "class",
      "description": "Sends the confirmation message to the customer after an order is created. A delivery failure is logged and retried; it never fails the order itself.",
      "evidence": [
        {
          "file": "docs/GLOSSARY.md",
          "line": 9,
          "snippet": "- **NotificationService**: Sends the confirmation message to the customer after an order is created. A delivery failure is logged and retried; it never fails the order itself."
        }
      ],
      "confidence": "high"
    },
    {
      "term": "OrderCreatedEvent",
      "kind": "concept",
      "description": "The domain event emitted exactly once per successfully created order. It carries the order id, amount, currency, and charge id.",
      "evidence": [
        {
          "file": "docs/GLOSSARY.md",
          "line": 10,
          "snippet": "- **OrderCreatedEvent**: The domain event emitted exactly once per successfully created order. It carries the order id, amount, currency, and charge id."
        }
      ],
      "confidence": "high"
    },
    {
      "term": "OrderService",
      "kind": "class",
      "description": "Coordinates order creation end to end: it validates the payload, charges payment, publishes the order-created event, and triggers the confirmation notification.",
      "evidence": [
        {
          "file": "docs/GLOSSARY.md",
          "line": 6,
          "snippet": "- **OrderService**: Coordinates order creation end to end: it validates the payload, charges payment, publishes the order-created event, and triggers the confirmation notification."
        }
      ],
      "confidence": "high"
    },
    {
      "term": "PaymentGateway",
      "kind": "class",
      "description": "The payment charging component. It authorizes and captures the order amount and never stores raw card numbers; only an opaque charge id is kept with the order.",
      "evidence": [
        {
          "file": "docs/GLOSSARY.md",
          "line": 7,
          "snippet": "- **PaymentGateway**: The payment charging component. It authorizes and captures the order amount and never stores raw card numbers; only an opaque charge id is kept with the order."
        }
      ],
      "confidence": "high"
    },
    {
      "term": "RetryPolicy",
      "kind": "concept",
      "description": "The exponential backoff schedule for failed event deliveries: attempts wait 1s, 4s, 16s, 64s, then 256s before the event is parked in the dead letter queue (DLQ).",
      "evidence": [
        {
          "file": "docs/GLOSSARY.md",
          "line": 11,
          "snippet": "- **RetryPolicy**: The exponential backoff schedule for failed event deliveries: attempts wait 1s, 4s, 16s, 64s, then 256s before the event is parked in the dead letter queue (DLQ)."
        }
      ],
      "confidence": "high"
    },
    {
      "term": "SLA",
      "kind": "concept",
      "description": "The service level agreement for order intake: 99.9% of orders acknowledged within 2 seconds.",
      "evidence": [
        {
          "file": "README.md",
          "line": 26,
          "snippet": "| SLA | The service level agreement for order intake: 99.9% of orders acknowledged within 2 seconds. |"
        }
      ],
      "confidence": "high"
    }
  ]
}