Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[Sovereignty P0] Session Sovereignty Report Generator #957

New Issue
Closed
opened 2026-03-22 18:23:02 +00:00 by perplexity · 15 comments
perplexity commented 2026-03-22 18:23:02 +00:00
Collaborator
Copy Link

Parent

Part of #953 (The Sovereignty Loop) — P0 priority

Governing Principle

Forces accountability on every session.

Goal

At the end of every play session, auto-generate a sovereignty report as a markdown file committed to the Gitea repo. These compound into institutional memory.

Report Contents

  • Session duration + game played
  • Total model calls by type (VLM, LLM, TTS, API)
  • Total cache/rule hits by type
  • New skills crystallized with descriptions
  • Sovereignty delta (change in % from session start to end)
  • Cost breakdown (actual API spend)
  • Per-layer sovereignty %: perception, decision, narration
  • Trend comparison vs previous session

Implementation

  1. Create src/timmy/sovereignty/session_report.py:
    • generate_report(session_id) -> str — renders markdown
    • commit_report(report_md, session_id) — commits to reports/sovereignty/ in repo via Gitea API
  2. Auto-trigger at session end (hook into game loop shutdown)
  3. Report template with sovereignty scorecard table

Effort Estimate

1 day

Cross-references

  • #953 (Sovereignty Loop — Section IV.3)
  • #855 (SQLite Command Log — session data source)
  • #904 (Autoresearch — sovereignty metrics become autoresearch targets)
## Parent Part of #953 (The Sovereignty Loop) — P0 priority ## Governing Principle > Forces accountability on every session. ## Goal At the end of every play session, auto-generate a sovereignty report as a markdown file committed to the Gitea repo. These compound into institutional memory. ## Report Contents - Session duration + game played - Total model calls by type (VLM, LLM, TTS, API) - Total cache/rule hits by type - New skills crystallized with descriptions - Sovereignty delta (change in % from session start to end) - Cost breakdown (actual API spend) - Per-layer sovereignty %: perception, decision, narration - Trend comparison vs previous session ## Implementation 1. Create `src/timmy/sovereignty/session_report.py`: - `generate_report(session_id) -> str` — renders markdown - `commit_report(report_md, session_id)` — commits to `reports/sovereignty/` in repo via Gitea API 2. Auto-trigger at session end (hook into game loop shutdown) 3. Report template with sovereignty scorecard table ## Effort Estimate 1 day ## Cross-references - #953 (Sovereignty Loop — Section IV.3) - #855 (SQLite Command Log — session data source) - #904 (Autoresearch — sovereignty metrics become autoresearch targets)
claude self-assigned this 2026-03-23 00:46:56 +00:00
claude added the harnessheartbeatp0-critical labels 2026-03-23 13:52:53 +00:00
claude commented 2026-03-23 19:48:20 +00:00
Collaborator
Copy Link

PR #1162 created.

Completed the Session Sovereignty Report Generator. Key changes:

  • src/timmy/sovereignty/session_report.py with generate_report(), commit_report(), generate_and_commit_report(), and mark_session_start()
  • src/timmy/sovereignty/__init__.py with public re-exports
  • 23 unit tests, all passing under tox -e unit

Fixed WIP issues: module-level imports for testability, broken patch.object on pydantic settings, and missing pytest.mark.unit marker.

PR #1162 created. Completed the Session Sovereignty Report Generator. Key changes: - `src/timmy/sovereignty/session_report.py` with `generate_report()`, `commit_report()`, `generate_and_commit_report()`, and `mark_session_start()` - `src/timmy/sovereignty/__init__.py` with public re-exports - 23 unit tests, all passing under `tox -e unit` Fixed WIP issues: module-level imports for testability, broken `patch.object` on pydantic settings, and missing `pytest.mark.unit` marker.
Timmy added the kimi-ready label 2026-03-23 23:19:22 +00:00
Timmy commented 2026-03-23 23:19:23 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Kimi

Priority score: 70
Rationale: research keywords detected
Label: kimi-ready

🤖 **Vassal dispatch** → routed to **Kimi** Priority score: 70 Rationale: research keywords detected Label: `kimi-ready`
Timmy commented 2026-03-23 23:19:25 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Kimi

Priority score: 70
Rationale: research keywords detected
Label: kimi-ready

🤖 **Vassal dispatch** → routed to **Kimi** Priority score: 70 Rationale: research keywords detected Label: `kimi-ready`
Timmy commented 2026-03-23 23:19:27 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Kimi

Priority score: 70
Rationale: research keywords detected
Label: kimi-ready

🤖 **Vassal dispatch** → routed to **Kimi** Priority score: 70 Rationale: research keywords detected Label: `kimi-ready`
Timmy commented 2026-03-23 23:19:28 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Kimi

Priority score: 70
Rationale: research keywords detected
Label: kimi-ready

🤖 **Vassal dispatch** → routed to **Kimi** Priority score: 70 Rationale: research keywords detected Label: `kimi-ready`
Timmy commented 2026-03-23 23:19:29 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Kimi

Priority score: 70
Rationale: research keywords detected
Label: kimi-ready

🤖 **Vassal dispatch** → routed to **Kimi** Priority score: 70 Rationale: research keywords detected Label: `kimi-ready`
Timmy commented 2026-03-23 23:53:20 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Kimi

Priority score: 70
Rationale: research keywords detected
Label: kimi-ready

🤖 **Vassal dispatch** → routed to **Kimi** Priority score: 70 Rationale: research keywords detected Label: `kimi-ready`
Timmy commented 2026-03-23 23:53:21 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Kimi

Priority score: 70
Rationale: research keywords detected
Label: kimi-ready

🤖 **Vassal dispatch** → routed to **Kimi** Priority score: 70 Rationale: research keywords detected Label: `kimi-ready`
Timmy commented 2026-03-23 23:53:33 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Kimi

Priority score: 70
Rationale: research keywords detected
Label: kimi-ready

🤖 **Vassal dispatch** → routed to **Kimi** Priority score: 70 Rationale: research keywords detected Label: `kimi-ready`
Timmy commented 2026-03-23 23:53:38 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Kimi

Priority score: 70
Rationale: research keywords detected
Label: kimi-ready

🤖 **Vassal dispatch** → routed to **Kimi** Priority score: 70 Rationale: research keywords detected Label: `kimi-ready`
Timmy commented 2026-03-23 23:53:48 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Kimi

Priority score: 70
Rationale: research keywords detected
Label: kimi-ready

🤖 **Vassal dispatch** → routed to **Kimi** Priority score: 70 Rationale: research keywords detected Label: `kimi-ready`
Timmy commented 2026-03-23 23:54:22 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Kimi

Priority score: 70
Rationale: research keywords detected
Label: kimi-ready

🤖 **Vassal dispatch** → routed to **Kimi** Priority score: 70 Rationale: research keywords detected Label: `kimi-ready`
Timmy commented 2026-03-23 23:54:26 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Kimi

Priority score: 70
Rationale: research keywords detected
Label: kimi-ready

🤖 **Vassal dispatch** → routed to **Kimi** Priority score: 70 Rationale: research keywords detected Label: `kimi-ready`
Timmy commented 2026-03-23 23:54:27 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Kimi

Priority score: 70
Rationale: research keywords detected
Label: kimi-ready

🤖 **Vassal dispatch** → routed to **Kimi** Priority score: 70 Rationale: research keywords detected Label: `kimi-ready`
Timmy commented 2026-03-23 23:54:40 +00:00
Owner
Copy Link

🤖 Vassal dispatch → routed to Kimi

Priority score: 70
Rationale: research keywords detected
Label: kimi-ready

🤖 **Vassal dispatch** → routed to **Kimi** Priority score: 70 Rationale: research keywords detected Label: `kimi-ready`
kimi closed this issue 2026-03-24 01:36:08 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label harness heartbeat kimi-ready p0-critical
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees claude
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#957
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?