lantern

villa-villekulla-pipeline

🎯 Villa Villekulla - Pipeline Visual IDE

Case Details

Case ID: task-692f67a5-ec38-4f3c-898e-6c74a8aedc6e Status: parked Created: 2026-01-26T16:16:02.035Z Updated: 2026-01-26T16:16:02.035Z Priority: 2

Investigation Details

Case Type: investigation Urgency Level: routine Assigned Detective: Claude

Notes

Vision

A web-based visual IDE for composing and running Oculus pipelines. Same backend as pippi CLI, different UX surface.

Design Constraints

Target User: Early competent analysts - above help desk, below senior technical Aesthetic: Canada.ca government style - clean, flat, professional, obvious Not: Kid-y, wiggly, flashy, silly

Layout: Classic IDE

  • Main canvas (center) - grid for tile placement
  • Workbench/palette (right) - fence banks by tag
  • Trace/output panel (bottom) - execution trace, context diffs

Core Model (from Sprout Garden)

Garden Villa Villekulla
Plot Tile (fence)
Vine Arrow (next address)
Sprout Context object
Tend Fence execution
Spring Context loader
Harvest Final context collector

Two Composition Modes

  • Code Mode - YAML syntax for power users
  • Visual Mode - Drag tiles, draw arrows, click to configure

Key Features

  • Fence palette from fence index (filtered by tags)
  • Grid canvas for visual composition
  • Gates for conditional branching (two outputs)
  • Trace panel showing step history with cache status
  • Click any step to see context at that point
  • Tile color coding: hit (green), miss (yellow), stored (cyan), failed (red)
  • Export to pipeline YAML node

Related Work

  • Sprout Garden (kid version, same execution model)
  • Pippi CLI (same API, different surface)
  • Elephant Design Language (design constraints)
  • Pipeline execution, caching, tracing (case task-141c8bfd)

Investigation Timeline

2026-01-26T16:16:02.045Z - Claude - case_created

Case opened from CLI

Consciousness Links

Context: Visual IDE for pipeline composition - grown-up version of Sprout Garden concept

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