lantern

oculus-poke-content

🎯 The Oculus Poke Content Replacement Bug

Case Details

Case ID: task-d399666b-d272-4bf5-825f-7f158603a835 Status: parked Created: 2025-11-20T19:24:53.355Z Updated: 2025-11-20T19:24:53.355Z Priority: 3

Investigation Details

Case Type: report Urgency Level: routine

Notes

Issue: oculus_poke fails with generic "API call failed: Poke operation failed" error when attempting to replace entire page content.

Attempted Operation:

  • Path: diagnostic-ecs-cluster-orphans → content
  • Goal: Replace entire markdown content with new version using graphnode fences
  • Error: MCP error -32000: API call failed: Poke operation failed

Questions to Answer:

  • Can we poke the content path at all?
  • Is there a size limit on poke operations?
  • Is the path syntax correct for replacing full content?
  • Should we use a different approach (Edit tool vs poke)?

Test Plan:

  • Create isolated test node
  • Attempt small content replacement via poke
  • Attempt large content replacement via poke
  • Document findings and workarounds

Investigation Timeline

2025-11-20T19:24:53.356Z - System - case_created

Case opened from CLI

Consciousness Links

Auto-Detected Keywords

report

This case file is automatically updated. For investigation logs, see the corresponding log channel.

📋 Case To-Do List

This case has an integrated to-do list system that syncs with the Oculus knowledge graph. The to-do list uses the virtual:todo-list fence which auto-detects GitHub-style checkbox markdown.

How the To-Do System Works

  • Auto-Detection: Checkbox lists are automatically detected as virtual:todo-list fences
  • Alice Integration: Display in Alice dashboard using :::wonderland-todo-list slug="${current_case}"
  • ISA Operations: Use fence exec for add/check/update operations
  • Metadata Support: Add [assignee:name] [priority:level] tags to tasks

Case To-Do Operations

  • View state: oculus fence list ${slug} then oculus fence view ${slug} <fence-index>
  • Add task: oculus fence exec ${slug} <fence-index> add "New task"
  • Check task: oculus fence exec ${slug} <fence-index> check 0
  • Update task: oculus fence exec ${slug} <fence-index> update 0 "Updated content"
  • Reference: See virtual-fence-todo for full documentation

Current Case Tasks

  • 🎯 Solve the case
  • 📝 Document findings in investigation notes
  • 🔗 Link relevant evidence and consciousness resources
  • ✅ Update case status when complete

Next Steps

Add investigation notes and evidence tags as you progress. The to-do list will evolve with your investigation. Tasks can be managed via Oculus fence operations or edited directly in the node.