Initial commit

2025-08-20 09:32:35 +02:00
commit 20c8336b9c
4 changed files with 530 additions and 0 deletions
--- a/requests_log.md
+++ b/requests_log.md
@ -0,0 +1,156 @@
+## 📥 Request - 2025-07-30T11:24:13.692836
+
+**Timestamp:** 2025-07-30T11:24:13.692836
+
+### Headers
+\```json
+{
+    "host": "localhost:8000",
+    "api-key": "dddd",
+    "content-type": "application/json; charset=utf-8",
+    "content-length": "1242"
+}
+\```
+
+### Message Contents
+\```markdown
+- **system:** You will be provided with COBOL source code.
+
+Response needs to be in .md format and contain description of the code.
+
+You need to follow these rules:
+
+1. Use vocabulary suited for design documentation.
+
+2. Describe each statement inside the code in numbered list. Be as detailed as possible.
+
+2.1. Describe each statement in separate numbered line, do not group statements. I really do mean each and every single one. Describe them all, not just some of them. You are allowed to repeat yourself if necessary. DO NOT IMPROVISE.
+
+2.2. If there are nested statements increase numbering outline for each nested statement.
+
+3. There should be no text after numerated part is finished.
+
+
+- **user:** DISPLAY "Please input one upper-case letter. >>" WITH NO ADVANCIN
+       ACCEPT IN-DATA.
+       PERFORM TEST BEFORE
+       VARYING COUNTER FROM 1 BY 1 UNTIL COUNTER > 26
+       IF IN-DATA = ALP(COUNTER:1) THEN
+       EXIT PERFORM
+       END-IF
+       END-PERFORM.
+       IF COUNTER <= 26 THEN
+       DISPLAY IN-DATA " is character " COUNTER " in alphabetical order.
+
+\```
+
+### Full Body
+\```json
+{
+    "messages": [
+        {
+            "role": "system",
+            "content": "You will be provided with COBOL source code.\r\nResponse needs to be in .md format and contain description of the code.\r\nYou need to follow these rules:\r\n1. Use vocabulary suited for design documentation.\r\n2. Describe each statement inside the code in numbered list. Be as detailed as possible.\r\n2.1. Describe each statement in separate numbered line, do not group statements. I really do mean each and every single one. Describe them all, not just some of them. You are allowed to repeat yourself if necessary. DO NOT IMPROVISE.\r\n2.2. If there are nested statements increase numbering outline for each nested statement.\r\n3. There should be no text after numerated part is finished.\r\n"
+        },
+        {
+            "role": "user",
+            "content": "DISPLAY \"Please input one upper-case letter. >>\" WITH NO ADVANCIN\n       ACCEPT IN-DATA.\n       PERFORM TEST BEFORE\n       VARYING COUNTER FROM 1 BY 1 UNTIL COUNTER > 26\n       IF IN-DATA = ALP(COUNTER:1) THEN\n       EXIT PERFORM\n       END-IF\n       END-PERFORM.\n       IF COUNTER <= 26 THEN\n       DISPLAY IN-DATA \" is character \" COUNTER \" in alphabetical order.\n"
+        }
+    ],
+    "temperature": 0.01,
+    "top_p": 0.01,
+    "max_tokens": 900
+}
+\```
+
+### 📤 Response
+\```json
+{
+    "id": "chatcmpl-mock123",
+    "object": "chat.completion",
+    "created": 1753867453,
+    "model": "gpt-4",
+    "choices": [
+        {
+            "index": 0,
+            "message": {
+                "role": "assistant",
+                "content": "Lorem ipsum dolor sit amet, consectetur adipiscing elit."
+            },
+            "finish_reason": "stop"
+        }
+    ],
+    "usage": {
+        "prompt_tokens": 10,
+        "completion_tokens": 12,
+        "total_tokens": 22
+    }
+}
+\```
+
+---
+## 📥 Request - 2025-07-30T11:24:13.716838
+
+**Timestamp:** 2025-07-30T11:24:13.716838
+
+### Headers
+\```json
+{
+    "host": "localhost:8000",
+    "api-key": "dddd",
+    "content-type": "application/json; charset=utf-8",
+    "content-length": "596"
+}
+\```
+
+### Message Contents
+\```markdown
+- **system:** You will be provided with COBOL source code description. This description represents one COBOL procedure division.
+
+Please provide short summary describing the function of this procedure division. Start description with words "This procedure division".
+
+Don't describe each paragraph separately, but whole division at once. Be as short as possible.
+
+
+- **user:** 
+
+## PROCEDURE DIVISION BODY
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit.
+
+
+
+
+
+
+\```
+
+### Full Body
+\```json
+{
+    "messages": [
+        {
+            "role": "system",
+            "content": "You will be provided with COBOL source code description. This description represents one COBOL procedure division.\r\nPlease provide short summary describing the function of this procedure division. Start description with words \"This procedure division\".\r\nDon't describe each paragraph separately, but whole division at once. Be as short as possible.\r\n"
+        },
+        {
+            "role": "user",
+            "content": "\r\n## PROCEDURE DIVISION BODY\r\nLorem ipsum dolor sit amet, consectetur adipiscing elit.\r\n\r\n\r\n"
+        }
+    ],
+    "temperature": 0.01,
+    "top_p": 0.01,
+    "max_tokens": 900
+}
+\```
+
+### 📤 Response
+\```json
+{
+    "id": "chatcmpl-mock123",
+    "object": "chat.completion",
+    "created": 1753867453,
+    "model": "gpt-4",
+    "choices": [
+        {
+            "index": 0,