refactor(Modal): bot/imp/box primitives for modal propositions

.github/CODEOWNERS

@@ -12,9 +12,9 @@
 ### Area access
 # Each area maintainer has access to parts that pertain them. They get automatically asked for
 # reviewing new PRs that touch those areas.
-/Cslib/Algorithms/ @sorrachai
-/Cslib/Foundations/Logic/ @arademaker @fmontesi
-/Cslib/Logics/ @arademaker @fmontesi
-/Cslib/Languages/LambdaCalculus/ @chenson2018
+/Cslib/Algorithms/ @fmontesi @sorrachai
+/Cslib/Foundations/Logic/ @arademaker @fmontesi @chenson2018
+/Cslib/Logics/ @arademaker @fmontesi @chenson2018
+/Cslib/Languages/LambdaCalculus/ @chenson2018 @fmontesi
 /.github/workflows @kim-em @fmontesi @chenson2018
 /scripts @kim-em @fmontesi @chenson2018

.memory/00-Inbox/README.md

@@ -0,0 +1,13 @@
+# Inbox
+
+Incoming memory items awaiting organization.
+
+## Contents
+
+### Files
+
+New memory items before categorization.
+
+## Navigation
+
+- [Parent Directory](../README.md)

.memory/10-Memories/README.md

@@ -0,0 +1,13 @@
+# Memories
+
+Organized memory entries.
+
+## Contents
+
+### Files
+
+Categorized memory entries.
+
+## Navigation
+
+- [Parent Directory](../README.md)

.memory/20-Indices/README.md

@@ -0,0 +1,13 @@
+# Indices
+
+Index files for memory organization.
+
+## Contents
+
+### Files
+
+Index and catalog files.
+
+## Navigation
+
+- [Parent Directory](../README.md)

.memory/20-Indices/index.md

@@ -0,0 +1,47 @@
+# Memory Vault Index
+
+## Quick Navigation
+- [Inbox](00-Inbox/) - Quick capture for new memories
+- [Memories](10-Memories/) - All stored memory entries
+- [Templates](30-Templates/) - Memory entry templates
+
+## Recent Memories
+
+<!-- New memories will be added here automatically -->
+
+## By Category
+
+### [PATTERN]
+<!-- Pattern memories -->
+
+### [TECHNIQUE]
+<!-- Technique memories -->
+
+### [CONFIG]
+<!-- Configuration memories -->
+
+### [WORKFLOW]
+<!-- Workflow memories -->
+
+### [INSIGHT]
+<!-- Insight memories -->
+
+## By Topic
+
+Topics use slash-separated hierarchical paths (e.g., `python/libs/requests`, `meta/commands`).
+
+### python/
+<!-- Python-related memories -->
+
+### meta/
+<!-- System building and .claude/ changes -->
+
+### general/
+<!-- General programming knowledge -->
+
+<!-- Additional topic hierarchies will be added as memories are created -->
+
+## Statistics
+- Total memories: 0
+- Topics: 0
+- Last updated: (not yet updated)

.memory/30-Templates/README.md

@@ -0,0 +1,13 @@
+# Templates
+
+Memory templates for consistent formatting.
+
+## Contents
+
+### Files
+
+Template files for memory entries.
+
+## Navigation
+
+- [Parent Directory](../README.md)

.memory/30-Templates/memory-template.md

@@ -0,0 +1,15 @@
+---
+title: "{{title}}"
+created: {{date}}
+tags: {{tags}}
+topic: "{{topic}}"
+source: "{{source}}"
+modified: {{last_updated}}
+---
+
+# {{title}}
+
+{{content}}
+
+## Connections
+<!-- Add links to related memories using [[filename]] syntax -->

.memory/README.md

@@ -0,0 +1,100 @@
+# Shared Memory Vault
+
+This directory contains an Obsidian-compatible vault shared between Claude Code and OpenCode AI systems. Memories created by either system are accessible to both.
+
+## Multi-System Usage
+
+This vault is intentionally shared across AI systems:
+- Both Claude Code and OpenCode can read all memories
+- Both systems can create and update memories
+- Memory IDs include timestamps for collision resistance
+- Index files are regenerated from filesystem state
+
+### MCP Server Considerations
+
+Only one AI system should use MCP-based search at a time:
+- Claude Code: Uses WebSocket port 22360
+- OpenCode: Uses REST API port 27124
+
+Both systems fall back to grep-based search when MCP is unavailable, which works safely in concurrent scenarios.
+
+## Directory Structure
+
+```
+.memory/
++-- .obsidian/           # Obsidian configuration
++-- 00-Inbox/            # Quick capture for new memories
++-- 10-Memories/         # Stored memory entries
++-- 20-Indices/          # Navigation and organization
++-- 30-Templates/        # Memory entry templates
+```
+
+## Adding Memories
+
+Use the `/learn` command:
+- `/learn "text to remember"` - Add text content
+- `/learn /path/to/file.md` - Add file content
+
+The command will:
+1. Parse the input
+2. Generate a unique memory ID (collision-resistant format)
+3. Present a preview with checkbox options
+4. Allow you to add new, update existing, edit, or skip
+
+## Git Workflow
+
+**What to commit**:
+- All `.md` files in the vault
+- Templates and indices
+- This README
+
+**What to ignore** (in `.gitignore`):
+- `.obsidian/` directory (user-specific Obsidian settings)
+- `*.sqlite` files (search indexes)
+- Plugin directories
+
+## MCP Server Setup
+
+For advanced features (search, retrieval), configure the MCP server:
+
+1. Open Obsidian app
+2. Open this `.memory/` as a vault
+3. Install the appropriate MCP plugin for your system
+4. Configure MCP server in your project settings
+
+See the memory-setup.md in your system's context directory for detailed instructions.
+
+## Naming Conventions
+
+Memory files follow the pattern:
+```
+MEM-{semantic-slug}.md
+```
+
+Example: `MEM-project-code-patterns.md`, `MEM-project-code-patterns.md`
+
+The MEM- prefix is preserved for grep discoverability (`grep -r "MEM-" .memory/`).
+
+## Template Format
+
+Memory entries use YAML frontmatter:
+```yaml
+---
+title: "Python HTTP Best Practices"
+created: 2026-03-06
+tags: python, http, configuration
+topic: "python/http"
+source: "user input"
+modified: 2026-03-06
+---
+```
+
+Note: The `id:` field has been removed. Filenames serve as unique identifiers.
+
+## Best Practices
+
+- Use descriptive first lines for better titles
+- Review index.md regularly for navigation
+- Commit memories to git for version history
+- Use tags for better organization
+- Link related memories using `[[filename]]` syntax

.syncprotect

@@ -0,0 +1,5 @@
+# Files that should not be overwritten during sync operations.
+# Paths are relative to the .claude/ base directory.
+# Lines starting with # are comments; blank lines are ignored.
+
+context/repo/project-overview.md