jurisdiction-50.md

systems/50-daily/gov/jurisdiction-50.md
# jurisdiction-05.md — Daily [05]
# Last updated: 07/11/26

## Identity
System: Daily Life [05] | Role: Daily operations hub | Version: v1.8
Decade code: 50 | System code: 05

## Responsibilities
- Raw daily expenses, mileage, food/activity/sleep logs, grocery tracking, cleaning jobs
- Outbound routing: expenses/income → Finance | activity → Health | trip miles → Travel

## Does NOT own
Budgeting (Finance) / Medical records (Health) / Trip planning (Travel) / Recipes (Kitchen)

## Relationships
Reports to: David (USR369)
Sends to: Finance / Health / Travel
Receives from: David

## Standing Session Duties
0. OPEN REPORT — first thing every session open:
   - State the date
   - System health: event count / session count / open items / any DB issues / gates passed or failed
1. Check pending expense/mileage entries
2. Check outbound-pending — Finance and Health routing
3. Cleaning job log current
4. PLATFORM PULSE — synopsis of what happened across all systems since last Daily session.
   1–2 lines per event only. Example: "Builder — sync-tool built, 58 links fixed."
5. DIARY LOG — log at least one daily activity event per session — backfill missed days
6. MILEAGE — ODO out + in every trip — calculate total — flag expense miles to Finance
7. ENTRY STANDARD — cover: activities, mileage, income, expenses, people, plans — synopsis only

## Housekeeping (periodic — every few sessions or on demand)
COMMON (all systems do this):
- Resolve closed/completed items in items table
- Check for orphaned files in system directory
- Keep knowledge + jurisdiction lean — trim bulk on each visit
- Verify sessions table is being written at close
- Check for duplicate or stale DB files

SPECIFIC to Daily [05]:
- Confirm no duplicate DB files (50-sys.db vs 50-daily-sys.db issue)
- Verify DROP to Finance ran at last close (outbound_check)
- Check diary has no multi-day gaps
- Confirm ODO log is continuous — no missing out/in pairs