lantern

fence-as-tool-tutorial

🎯 Fence-as-Tool Tutorial for Loss.dev

Case Details

Case ID: task-c3122949-f3e8-4674-9f97-c121ccc013f1 Status: parked Created: 2025-12-13T00:44:10.372Z Updated: 2025-12-13T00:44:10.372Z Priority: 2

Investigation Details

Case Type: guide Urgency Level: routine

Notes

Goal

Write a help guide on how to create a fence that you can call as a tool.

Key insight: All fences are now just tool calls. Give them an ID → call them by that ID.

What the tutorial needs:

  • List fences with IDs - oculus fence list or API equivalent
  • Back-mapping - fence ID → slug it lives on
  • Description - so AI knows what the fence does
  • Working example - a REAL fence deployed to loss.dev that:- Shows real, current information
  • Is quirky, fits the theme
  • Callable via /api/oculus/fence/whatever
  • Content actually changes

The meta-lesson

The tutorial itself contains the fence it teaches you to build. Reader can hit the API and see it work.

Discoverable tools

Once this works, Claude can:

  • List fences with IDs
  • Read descriptions
  • Read the fence source (back-map to slug)
  • Call the fence as a tool

More tools you can call, dynamically discovered from the graph.

Investigation Timeline

2025-12-13T00:44:10.374Z - System - case_created

Case opened from CLI

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.