wiki-ops

Wiki Operations

Overview

The wiki is your project's compiled knowledge base. Unlike learnings (individual observations, possibly ephemeral), wiki pages are persistent, cross-referenced, and indexed.

• Learnings = raw observations ("I found that X causes Y")
• Wiki pages = compiled knowledge ("How X works", "Architecture of Y", "Patterns for Z")

When to Ingest

1. After task completion — if you discovered how a system works, document it
2. After resolving a tricky bug — document the root cause and fix pattern
3. When a learning is marked useful 2+ times — promote it to a wiki page
4. During session shutdown — review what you learned, compile if notable
5. When you notice a gap — if you searched the wiki and didn't find what you needed, create the page after you find the answer

Creating/Updating a Wiki Page

~/.config/squadrant/scripts/wiki-ingest.sh "{spokeVaultPath}" "{slug}" "{title}" "{category}" "{body}" "{tags}" "{source}"

Parameters:

• slug: URL-friendly name (e.g., auth-flow, cairo-contract-patterns)
• title: Human-readable title
• category: One of: Architecture, Patterns, APIs, Configuration, Debugging, Conventions, Dependencies, Deployment
• body: Full markdown content (can be multi-paragraph)
• tags: Comma-separated keywords
• source: How this knowledge was discovered (e.g., "crew debugging issue #42")

Example:

~/.config/squadrant/scripts/wiki-ingest.sh "/path/to/spoke" "starknet-account-deploy" "StarkNet Account Deployment" "Patterns" "Account deployment on StarkNet requires a two-step process:

1. Compute the address from the class hash and constructor args
2. Fund the computed address with ETH
3. Call deploy_account

Common pitfall: the salt must match between compute and deploy." "starknet,deployment,account" "crew debugging deploy failures"

Querying the Wiki

Before starting a new task, check if the wiki has relevant knowledge:

~/.config/squadrant/scripts/wiki-query.sh "{spokeVaultPath}" "{keyword}"