🎯 The Case of the Unpolished Paper

Case Details

Case ID: task-98528f96-210a-46a8-97cf-3e5f3e545f7a Status: parked Created: 2026-01-01T22:55:00.204Z Updated: 2026-01-01T22:55:00.204Z Priority: 2

Investigation Details

Case Type: investigation Urgency Level: routine

Notes

Review feedback for Wanderland paper prior to loss.dev publication. Multiple issues identified across content, metadata, and structure.

Summary of issues:

• Content gaps: Missing related work comparisons, unproven claims, no user studies
• Metadata: TBD authors, broken citation parser, misleading verification signals
• Structural: Inconsistent slot directions, provenance cascade unclear
• Minor: Data duplication risk, scaling concerns undiscussed

Investigation Timeline

2026-01-01T22:55:00.206Z - System - case_created

Case opened from CLI

Consciousness Links

Context: Paper revision pass before publication

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

Content Gaps

• Add missing related work comparisons (Jupyter, Observable, Notion, docs-as-code movement)
• Soften "structural isomorphism" claim or provide rigorous formal mapping
• Address lack of user study / authoring-effort metrics in evaluation
• Add measurement of provenance drift detection in production (or acknowledge gap)

Metadata Issues

• Fix Reference 2 authors (TBD → actual authors for arXiv:2502.17441)
• Fix Reference 3 authors (TBD → actual authors for arXiv:2406.02962)
• Fix citation parser extracting wrong authors (e.g., "Streit, M." as sole author)
• Acknowledge that link-checking ≠ citation verification (Knuth/Mac Lane are 🔴 but trustworthy)

Structural Inconsistencies

• Fix Introduction West slot (lists related-work as "Previous" when it's "Next")
• Document cardinal direction semantics or fix inconsistent usage
• Clarify provenance cascade behavior (child nodes 🔴, parent 🟡)

Minor Issues

• Consider having citation-verify fence consume YAML bibliography directly (avoid drift)
• Discuss cold start limitation (5s for 500 nodes) as scaling concern

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

Current Case Tasks