Soren_Molty/Knowledge
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added all of chat-topics, persona;-history, projects, receipts and vehicle. This is the knowledge base section after all....

Browse Source
This commit is contained in:
Soren (Molty)
2026-05-26 16:53:50 +10:00
parent 85f78332d1
commit 6ada86fe73
91 changed files with 3983 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files
projects/smsf/README.md
+20 -1
View File
@@ -32,7 +32,9 @@ Working area for Michael's SMSF-related records, tools, decisions, and reference
## Key decisions captured
- Use a dedicated SMSF tracker workbook rather than ad hoc notes.
- Keep **actual executed transactions** separate from allocation proposals/ideas.
- Use `transactions/actual-transactions.csv` as the canonical analyzable ledger for tax/reporting work.
- Use `smsf.sqlite` as the canonical structured ledger for tax/reporting work.
- Generate spreadsheets/CSV/PDF reports on demand from the DB for accountant/auditor/government requirements; do not manually maintain parallel spreadsheets as source-of-truth records.
- Keep `transactions/actual-transactions.csv` as a preserved legacy/import seed until the DB workflow is fully established.
- Prioritise AUD reporting support for SMSF/admin/accounting use.
- Include a cleaner accountant/auditor-facing summary tab separate from detailed working sheets.
- Keep this project under `knowledge/projects/smsf/` as the long-term checkpoint location.
@@ -45,3 +47,20 @@ Working area for Michael's SMSF-related records, tools, decisions, and reference
## Notes
- This is a documentation and operational support area, not tax or financial advice.
- Final compliance/accounting treatment should still be validated with the SMSF accountant/auditor.
## SQLite structured ledger layer
Created 2026-05-14:
- `smsf.sqlite` — structured SQLite ledger for audit/tax reporting support.
- `smsf-schema.sql` — schema dump for review/versioning.
- `scripts/build_smsf_db.py` — repeatable importer/rebuilder from current CSV/source documents.
- `reports/sqlite-migration-verification.md` — migration counts/totals verification.
- `reports/holdings-from-db.md` — holdings generated from SQLite.
- `reports/sqlite-usage.md` — useful queries and process notes.
Existing Markdown, CSV, workbook, and source documents were preserved. The DB is intended to become the structured query/reporting layer while source documents remain the immutable audit evidence.
## Reporting/export convention
Going forward, SMSF updates and processing should go directly into `smsf.sqlite`. Spreadsheets are generated on demand for a specific request, requirement, accountant/auditor format, or review purpose. This avoids manually maintaining duplicate sources of truth.