@realtimex/folio 0.1.14 → 0.1.16
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/api/src/routes/ingestions.ts +6 -1
- package/api/src/services/SDKService.ts +48 -2
- package/dist/api/src/routes/ingestions.js +6 -1
- package/dist/api/src/services/SDKService.js +37 -2
- package/dist/assets/{index-aI2VZJFA.js → index-dnBz6SWG.js} +2 -2
- package/dist/index.html +1 -1
- package/docs-dev/ingestion-engine.md +3 -3
- package/package.json +1 -1
package/dist/index.html
CHANGED
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
|
|
6
6
|
<link rel="icon" type="image/svg+xml" href="/favicon.svg" />
|
|
7
7
|
<title>Folio</title>
|
|
8
|
-
<script type="module" crossorigin src="/assets/index-
|
|
8
|
+
<script type="module" crossorigin src="/assets/index-dnBz6SWG.js"></script>
|
|
9
9
|
<link rel="stylesheet" crossorigin href="/assets/index-DzN8-j-e.css">
|
|
10
10
|
</head>
|
|
11
11
|
<body>
|
|
@@ -9,13 +9,14 @@ Think of `realtimex.ai` desktop app as your backend API, even though it's runnin
|
|
|
9
9
|
|
|
10
10
|
#### Step 0: The Dropzone
|
|
11
11
|
* Folio does **not** store raw document bytes in the database.
|
|
12
|
-
* Folio creates a physical "Dropzone" folder on the local machine (e.g., `~/.realtimex/
|
|
12
|
+
* Folio creates a physical "Dropzone" folder on the local machine (e.g., `~/.realtimex.ai/Resources/local-apps/{appId}/dropzone` via `sdk.getAppDataDir()` or a configured `storage_path`).
|
|
13
|
+
* In development mode with API key auth, the SDK resolves this directory from the masked API key to avoid collisions across environments.
|
|
13
14
|
|
|
14
15
|
#### Step 1: Ingestion (Folio)
|
|
15
16
|
* Folio detects or receives `scan_001.pdf` via the UI or Watcher.
|
|
16
17
|
* Folio saves the physical file into the **Dropzone**.
|
|
17
18
|
* Folio generates a `task_id` and inserts a task into the `rtx_activities` table (Compatible Mode).
|
|
18
|
-
* **Crucially**: The `raw_data` JSON only contains a metadata pointer to the physical file: `{ "file_path": "/Users/local/.realtimex/
|
|
19
|
+
* **Crucially**: The `raw_data` JSON only contains a metadata pointer to the physical file: `{ "file_path": "/Users/local/.realtimex.ai/Resources/local-apps/{appId}/dropzone/scan_001.pdf" }`.
|
|
19
20
|
|
|
20
21
|
#### Step 2: The Handshake (Folio $\rightarrow$ RealTimeX SDK)
|
|
21
22
|
Folio uses the RealTimeX SDK (via Compatible Mode `rtx_fn_claim_task`) to queue the work. The extraction schema (derived from the Policy) is also provided so the LLM output is strictly typed JSON.
|
|
@@ -66,4 +67,3 @@ graph LR
|
|
|
66
67
|
C -->|Trigger Action| H(Folio Actuator)
|
|
67
68
|
H -->|Move File| I[Organized Final Folder]
|
|
68
69
|
```
|
|
69
|
-
|