a66996ac10
Knowledge vault (Orion/PARA) migrated from the pre-Orion 484vault on 2026-10-01. Deliberately orphaned: prior history contained a plaintext password and stays local-only on branch archive/pre-boilerplate-history. Secrets and live Hermes state are gitignored.
36 lines
No EOL
1.9 KiB
Markdown
36 lines
No EOL
1.9 KiB
Markdown
|
|
|
|
```
|
|
TASK: Receipt Filing & Logging Automation
|
|
|
|
TRIGGER: Run this workflow when I ask you to process new receipts.
|
|
|
|
FOLDERS:
|
|
- Source (watch): /home/avi/DCIM/Camera/
|
|
- Destination A: /home/avi/Documents/Lab 484/Receipts L484 Expenses/
|
|
- Destination B: /home/avi/Documents/LLCs/LLC KCH Kingdom Compass/Receipts KCH Expenses/
|
|
|
|
SPREADSHEETS:
|
|
- Sheet A: /home/avi/Documents/00_EXPENSES_Lab484.ods ← logs files in Destination A
|
|
- Sheet B: /home/avi/Documents/00_Expenses_KCH.ods ← logs files in Destination B
|
|
|
|
WORKFLOW:
|
|
1. SCAN: List all receipt files in the source DCIM folder that are NOT yet logged in Sheet A. If none, tell me "No new receipts found" and stop.
|
|
|
|
2. ASK ME: For each new receipt, open/show it and ask: "What is this receipt for?" Wait for my answer (e.g., "gas", "groceries"). Do not guess.
|
|
|
|
3. NAME IT: Look at the existing filenames in Destination A and infer the naming convention (date format, vendor/category placement, numbering). Name the new file using that exact pattern, inserting my category answer where the other files put theirs. Show me the proposed filename before copying and wait for confirmation.
|
|
|
|
4. COPY: Copy (do not move) the receipt into both Destination A and Destination B using the confirmed name.
|
|
|
|
5. LOG IT: In each spreadsheet, add one row matching the existing style — same columns, same date format, same capitalization. Include a working hypTerlink pointing to the copied file in that sheet's corresponding folder. Match any formatting (bold headers, currency columns, etc.) already used.
|
|
|
|
6. Each sheet should have a hyperlink to the file just created following the format of all the other entries for example
|
|
|
|
7. CONFIRM: Report back with the filename and confirm both copies and both spreadsheet rows were written.
|
|
|
|
RULES:
|
|
- Never overwrite an existing file; if the name collides, append -2, -3, etc.
|
|
- Always copy, never move or delete from DCIM.
|
|
- If a step fails, stop and tell me exactly what failed rather than continuing.
|
|
``` |