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

[loop-generated] [soul-gap] Source distinction not implemented in agent responses #463

New Issue
Closed
opened 2026-03-19 18:43:16 +00:00 by Timmy · 0 comments
Timmy commented 2026-03-19 18:43:16 +00:00
Owner
Copy Link

What

SOUL.md requires Source Distinction: "Every claim I make comes from one of two places: a verified source I can point to, or my own pattern-matching. My user must be able to tell which is which."

Currently, Timmy's responses have no mechanism to distinguish grounded (retrieved) claims from generated (pattern-matched) claims. Only thinking.py has a single reference to grounding.

Why

This is a core SOUL requirement, not a nice-to-have. Without source distinction, Timmy cannot be honest about what it knows vs. what it's guessing.

Acceptance criteria

  • Agent responses should tag claims as "grounded" (from memory/retrieval) vs "inferred" (pattern-matching)
  • At minimum, when memory_system retrieval provides context, the response should cite it
  • When no grounding source exists, responses should include appropriate hedging
  • Design doc before implementation — this is architectural

Files

  • src/timmy/agent.py (system prompt construction)
  • src/timmy/memory_system.py (retrieval context)
  • src/timmy/thinking.py (existing grounding ref)
## What SOUL.md requires Source Distinction: "Every claim I make comes from one of two places: a verified source I can point to, or my own pattern-matching. My user must be able to tell which is which." Currently, Timmy's responses have no mechanism to distinguish grounded (retrieved) claims from generated (pattern-matched) claims. Only `thinking.py` has a single reference to grounding. ## Why This is a core SOUL requirement, not a nice-to-have. Without source distinction, Timmy cannot be honest about what it knows vs. what it's guessing. ## Acceptance criteria - Agent responses should tag claims as "grounded" (from memory/retrieval) vs "inferred" (pattern-matching) - At minimum, when memory_system retrieval provides context, the response should cite it - When no grounding source exists, responses should include appropriate hedging - Design doc before implementation — this is architectural ## Files - src/timmy/agent.py (system prompt construction) - src/timmy/memory_system.py (retrieval context) - src/timmy/thinking.py (existing grounding ref)
Timmy closed this issue 2026-03-19 18:49:33 +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
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#463
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?