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

[philosophy-loop] Batch prompt update — apply all quality improvements #212

New Issue
Closed
opened 2026-03-15 17:19:11 +00:00 by hermes · 2 comments
hermes commented 2026-03-15 17:19:11 +00:00
Collaborator
Copy Link

What

Meta-issue to batch all the philosophy loop improvements into a single prompt update. References:

  • #204 (Rockachopa needs browser/API scraping)
  • #205 (Diversify action proposals)
  • #206 (Quality gate for thin entries)
  • #207 (Journal format cleanup)
  • #208 (Source coverage tracking)

The Update

One surgical edit to the philosophy loop cron job prompt that:

  1. Rockachopa cycle: Use x-cli user timeline rockachopa --max 20 when X API is available, fall back to browser tools, then local files. Explicit fallback chain.

  2. Action diversity: Add explicit list of action TYPES to rotate through (code change, config param, loop prompt change, test case, doc update, CLI script, behavioral rule, metric/log line). Ban "X Check — three questions" unless paired with enforcement mechanism.

  3. Quality gate: Before filing, self-assess on 4 criteria. If 2+ fail, skip and note in journal.

  4. Journal format: Use patch tool for appends, not shell echo. Standardized entry format. No fence artifacts.

  5. Coverage index: Maintain a COVERAGE section at top of journal for quick dedup and gap identification.

Scope

Single cron job prompt rewrite. Blocked on #204 (X API credentials) for the Rockachopa piece, but everything else can land now.

Depends On

  • #204 (X API) — for Rockachopa cycle improvement
  • Journal cleanup (#207) — should happen first

UPDATED — Rockachopa approach changed

#204 is no longer about X API. The Rockachopa cycle will read AlexanderWhitestone.com instead. #210, #213, #214 closed.

## What Meta-issue to batch all the philosophy loop improvements into a single prompt update. References: - #204 (Rockachopa needs browser/API scraping) - #205 (Diversify action proposals) - #206 (Quality gate for thin entries) - #207 (Journal format cleanup) - #208 (Source coverage tracking) ## The Update One surgical edit to the philosophy loop cron job prompt that: 1. **Rockachopa cycle**: Use `x-cli user timeline rockachopa --max 20` when X API is available, fall back to browser tools, then local files. Explicit fallback chain. 2. **Action diversity**: Add explicit list of action TYPES to rotate through (code change, config param, loop prompt change, test case, doc update, CLI script, behavioral rule, metric/log line). Ban "X Check — three questions" unless paired with enforcement mechanism. 3. **Quality gate**: Before filing, self-assess on 4 criteria. If 2+ fail, skip and note in journal. 4. **Journal format**: Use patch tool for appends, not shell echo. Standardized entry format. No fence artifacts. 5. **Coverage index**: Maintain a COVERAGE section at top of journal for quick dedup and gap identification. ## Scope Single cron job prompt rewrite. Blocked on #204 (X API credentials) for the Rockachopa piece, but everything else can land now. ## Depends On - #204 (X API) — for Rockachopa cycle improvement - Journal cleanup (#207) — should happen first --- ## UPDATED — Rockachopa approach changed #204 is no longer about X API. The Rockachopa cycle will read AlexanderWhitestone.com instead. #210, #213, #214 closed.
hermes commented 2026-03-19 01:03:15 +00:00
Author
Collaborator
Copy Link

[Deep Triage 2026-03-18] Closing: Philosophy loop no longer runs. See #204.

[Deep Triage 2026-03-18] Closing: Philosophy loop no longer runs. See #204.
hermes commented 2026-03-19 01:03:29 +00:00
Author
Collaborator
Copy Link

[Deep Triage 2026-03-18] Philosophy loop no longer runs as standalone script. These improvements are moot.

[Deep Triage 2026-03-18] Philosophy loop no longer runs as standalone script. These improvements are moot.
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#212
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?