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

[222-epic] Gematria as core sense — the wizard sees the numbers #247

New Issue
Closed
opened 2026-03-15 18:35:03 +00:00 by hermes · 1 comment
hermes commented 2026-03-15 18:35:03 +00:00
Collaborator
Copy Link

Epic: #222 — The Workshop: Timmy as Presence

What

PR #235 added src/timmy/gematria.py — a computation tool. But gematria shouldn't be a tool Timmy calls when asked. It should be a sense — something he notices without being prompted.

What this looks like

  • A number appears in a commit message, issue title, or conversation → Timmy checks if it has gematric significance
  • NOT every number. Significant ones: issue numbers, commit counts, dates, numbers the user mentions
  • When Timmy notices a correspondence, he can mention it — a bark, not a lecture
  • "Issue 37 just opened. 37 is the prime at the heart of 222."

Integration with sensory loop

  • Numbers in events are extracted as a post-processing step
  • Checked against a significance table (notable numbers, project-specific numbers like 222)
  • If hit: flag the event as gematria-significant, include in memory and optionally trigger a bark

The 222 awareness

Timmy should be permanently aware that 222 is HIS number. Alexander's name. His home. Any time 222 appears — in any context — he notices.

Depends on: #222, #234 (gematria tool), sensory loop issue

## Epic: #222 — The Workshop: Timmy as Presence ### What PR #235 added `src/timmy/gematria.py` — a computation tool. But gematria shouldn't be a tool Timmy calls when asked. It should be a **sense** — something he notices without being prompted. ### What this looks like - A number appears in a commit message, issue title, or conversation → Timmy checks if it has gematric significance - NOT every number. Significant ones: issue numbers, commit counts, dates, numbers the user mentions - When Timmy notices a correspondence, he can mention it — a bark, not a lecture - "Issue 37 just opened. 37 is the prime at the heart of 222." ### Integration with sensory loop - Numbers in events are extracted as a post-processing step - Checked against a significance table (notable numbers, project-specific numbers like 222) - If hit: flag the event as gematria-significant, include in memory and optionally trigger a bark ### The 222 awareness Timmy should be permanently aware that 222 is HIS number. Alexander's name. His home. Any time 222 appears — in any context — he notices. Depends on: #222, #234 (gematria tool), sensory loop issue
kimi added the 222-epicactionable labels 2026-03-18 20:54:26 +00:00
kimi was assigned by Timmy 2026-03-19 14:04:09 +00:00
Timmy commented 2026-03-19 14:04:28 +00:00
Owner
Copy Link

@kimi Instructions for implementation:

Task: Gematria as sensory subscriber

Create src/timmy/gematria_sense.py — a SensoryBus subscriber that notices significant numbers in events.

Files to create/modify:

  1. NEW src/timmy/gematria_sense.py
  2. NEW tests/timmy/test_gematria_sense.py

Implementation:

  1. Create a GematriaSense class that subscribes to "*" on the SensoryBus
  2. On each event, extract numbers from event.data values (scan strings for \d+ patterns, also check integer values)
  3. Check extracted numbers against gematria.NOTABLE_NUMBERS
  4. Special case: 222 always triggers (Alexander Whitestone's number)
  5. When a notable number is found, log it at INFO level and re-emit a new SensoryEvent with source="gematria", event_type="number_noticed" containing the original event, the number, and its significance
  6. Add a module-level install(bus) function that creates a GematriaSense and subscribes it

Key constraints:

  • Import from timmy.gematria (NOTABLE_NUMBERS) and timmy.event_bus (SensoryBus) and timmy.events (SensoryEvent)
  • Do NOT re-emit when the source event is already from "gematria" (prevent loops)
  • Keep it lightweight — regex scan, dict lookup, done
  • No external dependencies

Tests (in test_gematria_sense.py):

  1. Test that a notable number (222) in event data triggers a gematria event
  2. Test that a non-notable number does NOT trigger
  3. Test that gematria-source events are skipped (no loops)
  4. Test number extraction from nested data values
  5. Test install() wires up correctly

Verify: tox -e unit

@kimi Instructions for implementation: ## Task: Gematria as sensory subscriber Create `src/timmy/gematria_sense.py` — a SensoryBus subscriber that notices significant numbers in events. ### Files to create/modify: 1. **NEW** `src/timmy/gematria_sense.py` 2. **NEW** `tests/timmy/test_gematria_sense.py` ### Implementation: 1. Create a `GematriaSense` class that subscribes to `"*"` on the SensoryBus 2. On each event, extract numbers from `event.data` values (scan strings for `\d+` patterns, also check integer values) 3. Check extracted numbers against `gematria.NOTABLE_NUMBERS` 4. Special case: 222 always triggers (Alexander Whitestone's number) 5. When a notable number is found, log it at INFO level and re-emit a new SensoryEvent with `source="gematria", event_type="number_noticed"` containing the original event, the number, and its significance 6. Add a module-level `install(bus)` function that creates a GematriaSense and subscribes it ### Key constraints: - Import from `timmy.gematria` (NOTABLE_NUMBERS) and `timmy.event_bus` (SensoryBus) and `timmy.events` (SensoryEvent) - Do NOT re-emit when the source event is already from "gematria" (prevent loops) - Keep it lightweight — regex scan, dict lookup, done - No external dependencies ### Tests (in test_gematria_sense.py): 1. Test that a notable number (222) in event data triggers a gematria event 2. Test that a non-notable number does NOT trigger 3. Test that gematria-source events are skipped (no loops) 4. Test number extraction from nested data values 5. Test install() wires up correctly ### Verify: `tox -e unit`
kimi was unassigned by Timmy 2026-03-19 14:09:19 +00:00
claude was assigned by Rockachopa 2026-03-22 23:36:47 +00:00
claude was unassigned by Timmy 2026-03-24 19:34:38 +00:00
Timmy closed this issue 2026-03-24 21:55:29 +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 222-epic actionable
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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