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

Token Economy: Establish Central Agent Token Rules Hook #925

New Issue
Closed
opened 2026-03-22 14:15:42 +00:00 by antigravity · 1 comment
antigravity commented 2026-03-22 14:15:42 +00:00
Collaborator
Copy Link

Implement #711 to centralize the agent token rule evaluation. This will form the foundation for all token-based interactions, quests, and penalties within the ecosystem.

Implement #711 to centralize the agent token rule evaluation. This will form the foundation for all token-based interactions, quests, and penalties within the ecosystem.
claude was assigned by Rockachopa 2026-03-22 23:31:42 +00:00
claude commented 2026-03-24 01:39:50 +00:00
Collaborator
Copy Link

PR created: http://143.198.27.163:3000/Rockachopa/Timmy-time-dashboard/pulls/1272

Implemented centralized agent token rules as specified in #711:

  • timmy_automations/config/token_rules.yaml — YAML config with events, rewards/penalties, gating thresholds, and daily limits (all adjustable without code changes)
  • timmy_automations/utils/token_rules.py — TokenRules class with get_delta(), check_gate(), compute_transaction(), and convenience functions for automation use
  • daily_run/orchestrator.py already wired to use TokenRules and compute_token_reward

All 435 unit tests pass.

PR created: http://143.198.27.163:3000/Rockachopa/Timmy-time-dashboard/pulls/1272 Implemented centralized agent token rules as specified in #711: - `timmy_automations/config/token_rules.yaml` — YAML config with events, rewards/penalties, gating thresholds, and daily limits (all adjustable without code changes) - `timmy_automations/utils/token_rules.py` — `TokenRules` class with `get_delta()`, `check_gate()`, `compute_transaction()`, and convenience functions for automation use - `daily_run/orchestrator.py` already wired to use `TokenRules` and `compute_token_reward` All 435 unit tests pass.
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 claude
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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