# UseCaseCatalog

Status: **draft scaffold** · Date: 2026-06-08

See InfoTechPrimers on coulomb.social for use-case catalog conventions.

## UC-01 — Standalone open wiki (L0)

**Actor:** Anonymous contributor  
**Goal:** Read and write wiki pages with full history and no external dependencies.  
**Notes:** Ward Cunningham / c2-style open mode. Recovery via Git history, not gatekeeping.

## UC-02 — Attach a Git repo shard

**Actor:** Maintainer  
**Goal:** Attach a repository or `wiki/` subdirectory as a shard of an information space.  
**Notes:** Preserve shard sovereignty and adapter capability profile.

## UC-03 — Project a remote shard page locally

**Actor:** Reader  
**Goal:** View a page from a remote or read-only shard as a local projection with provenance and freshness visible.  
**Notes:** Lazy projection; no silent mutation.

## UC-04 — Overlay edit on read-only shard

**Actor:** Author  
**Goal:** Propose changes to a remote/read-only page as overlay/draft/patch before destructive apply.  
**Notes:** Overlay-before-mutation principle.

## UC-05 — Union browse (BackLinks, RecentChanges)

**Actor:** Reader  
**Goal:** Navigate derived views across all attached shards.  
**Notes:** BackLinks over federated link graph is a strong core candidate (see research findings).

## UC-06 — Authenticated team wiki (L2+)

**Actor:** Authenticated principal  
**Goal:** Read/write under role-based authorization with identity from external provider.  
**Notes:** See `spec/ArchitectureBlueprint.md` capability ladder.

## UC-07 — Detect cross-shard divergence

**Actor:** Maintainer  
**Goal:** Identify when equivalent pages in different shards have diverged and reconcile.  
**Notes:** Union without erasure — conflicts visible, not hidden.