lantern

native-poke-fence-execution

🎯 Native poke() in fence execution doesn't persist

Case Details

Case ID: task-bf993cdd-aac0-458d-8cff-dff1c5b29acb Status: parked Created: 2026-01-23T04:50:08.987Z Updated: 2026-01-23T04:50:08.987Z Priority: 3

Investigation Details

Case Type: investigation Urgency Level: routine

Notes

The native poke() function available inside Python fence execution context reports success but doesn't actually persist changes to the graph.

Reproduction:

  • Execute the add-to-reading-list fence with a new topic
  • Fence reports success with count incrementing
  • Execute get-reading-list for same topic - returns empty/not found

Evidence:

  • add-to-reading-list fence uses: poke("required-reading", f"required-reading-lists.readings.yaml.{topic}", current_list)
  • Reports {"success": true, "message": "added to as-above-so-below", "count": 1}
  • But data doesn't persist - subsequent get returns empty

Comparison:

  • Native peek() in same fence context works correctly
  • MCP _____poke tool works correctly with same path
  • Direct poke via MCP with path readings.yaml.as-above-so-below successfully persisted

Root cause hypothesis: The native poke() wrapper in fence execution context may be:

  • Not calling the actual write method
  • Writing to a cached/transient copy
  • Missing a flush/commit step

Affected tools:

  • add-to-reading-list fence in required-reading node
  • Potentially any fence that uses native poke() for persistence

Investigation Timeline

2026-01-23T04:50:08.992Z - System - case_created

Case opened from CLI

Consciousness Links

Auto-Detected Keywords

investigation

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.

Provenance

Document

  • Status: 🔴 Unverified