feat: publish showcases

src/content/showcase/index.mdx

@@ -0,0 +1,26 @@
+---
+title: 'Showcase'
+version: 'v1'
+description: 'Proof of adoption examples for REPL Works.'
+publishedAt: '2026-06-07T00:00:00Z'
+---
+
+# Showcase
+
+Showcase is proof of adoption, not marketing. It documents real usage patterns and conceptual examples that demonstrate how REPL Works is applied.
+
+## Projects
+
+- **REPL Works Website** — reference implementation built with REPL Works.
+- **Project A** — abstract example showing Git-based memory and workflow.
+- **Project B** — example emphasizing architecture consistency and model independence.
+- **Project C** — example demonstrating long-term continuity and session recovery.
+- **Project D** — example showing multi-model collaboration and planning separation.
+
+## Navigation
+
+- [REPL Works Website](/showcase/repl-works-website)
+- [Project A](/showcase/project-a)
+- [Project B](/showcase/project-b)
+- [Project C](/showcase/project-c)
+- [Project D](/showcase/project-d)

src/content/showcase/project-a.mdx

@@ -0,0 +1,24 @@
+---
+title: 'Project A Showcase'
+version: 'v1'
+description: 'Conceptual example showing REPL Works memory and Git workflow.'
+publishedAt: '2026-06-07T00:00:00Z'
+---
+
+# Project A Showcase
+
+## Project Description
+
+Project A is an abstract documentation project that uses REPL Works to preserve project intent and decisions.
+
+## Memory System Applied
+
+- Project knowledge is stored in versioned files: `ARCHITECTURE.md`, `TASKS.md`, and content collections.
+- The project uses a content-first structure so state is explicit and recoverable.
+- Changes are documented in Git, providing history and context for future sessions.
+
+## Git-based Workflow Usage
+
+- New work is introduced through discrete tasks in `TASKS.md`.
+- Each task is implemented as a documented commit.
+- The repository serves as the project memory source, enabling the team to resume work without relying on in-session memory.

src/content/showcase/project-b.mdx

@@ -0,0 +1,30 @@
+---
+title: 'Project B Showcase'
+version: 'v1'
+description: 'Conceptual example with architecture consistency and task-driven development.'
+publishedAt: '2026-06-07T00:00:00Z'
+---
+
+# Project B Showcase
+
+## Project Description
+
+Project B is a conceptual initiative that applies REPL Works to maintain consistent architecture and execution.
+
+## Architecture Consistency
+
+- Architecture is defined up front in `ARCHITECTURE.md` and preserved with every change.
+- Content collections and document structure follow the same conceptual model across the project.
+- Decisions are made explicit rather than buried in conversation.
+
+## Task-driven Development
+
+- Work is broken into clear tasks in `TASKS.md`.
+- Each task is scoped to one prompt and one commit, making progress measurable.
+- Task outputs are static documents, not ephemeral notes.
+
+## Model Independence
+
+- The project does not rely on a specific AI model for continuity.
+- Memory is kept in Git and file-based documents, so the workflow remains valid if the model changes.
+- The system is designed to work with any model that can read and update the documented content.

src/content/showcase/project-c.mdx

@@ -0,0 +1,30 @@
+---
+title: 'Project C Showcase'
+version: 'v1'
+description: 'Conceptual example emphasizing long-term continuity and session recovery.'
+publishedAt: '2026-06-07T00:00:00Z'
+---
+
+# Project C Showcase
+
+## Project Description
+
+Project C is a long-lived initiative that uses REPL Works to preserve continuity across many sessions.
+
+## Long-term Project Continuity
+
+- The project maintains durable memory in Git and structured documents.
+- Architecture and tasks remain stable even as implementation details evolve.
+- The project is designed to survive months of interruption.
+
+## Session Recovery via LONG_CONTEXT.md
+
+- Recovery summaries are stored in `LONG_CONTEXT.md` to bootstrap new sessions.
+- The long-context format captures intent, progress, and next actions.
+- This allows new sessions to resume quickly without rebuilding context from scratch.
+
+## AI Model Switching
+
+- The project does not depend on a single AI model.
+- If the model changes, the documented project memory still provides continuity.
+- Model switching is managed through the repository and files, not through session state.

src/content/showcase/project-d.mdx

@@ -0,0 +1,30 @@
+---
+title: 'Project D Showcase'
+version: 'v1'
+description: 'Conceptual example of multi-model collaboration and human + AI decision loops.'
+publishedAt: '2026-06-07T00:00:00Z'
+---
+
+# Project D Showcase
+
+## Project Description
+
+Project D is a conceptual example of a collaborative workflow where AI and humans work together using REPL Works.
+
+## Multi-model Collaboration
+
+- Multiple AI models can contribute to the project, each reading the same documented memory.
+- The repository stores the project state, allowing different models to participate without disrupting continuity.
+- Output is captured in files, not in a single model session.
+
+## AI + Human Decision Loop
+
+- Humans review and approve decisions documented in `ARCHITECTURE.md` and `TASKS.md`.
+- AI-generated suggestions are recorded as content and then validated by the team.
+- The loop remains explicit and traceable through Git history.
+
+## Planning vs Execution Separation
+
+- Planning artifacts are kept separate from execution outputs.
+- `TASKS.md` defines the plan, while content collections hold the resulting documentation.
+- This separation ensures that strategy is not mixed with implementation details.

src/content/showcase/repl-works-website.mdx

@@ -0,0 +1,28 @@
+---
+title: 'REPL Works Website Showcase'
+version: 'v1'
+description: 'Reference implementation of REPL Works applied to this website.'
+publishedAt: '2026-06-07T00:00:00Z'
+---
+
+# REPL Works Website Showcase
+
+This website is the reference implementation for REPL Works.
+
+## Built with REPL Works
+
+- The site is organized as content collections in `src/content`.
+- Core sections are published as MDX documents: Manifesto, Specification, Workflow, Resources, and Showcase.
+- The site shell and routing are driven by static documentation content.
+
+## AGENTS / ARCHITECTURE / TASKS mapping
+
+- **AGENTS** are represented by the content-first process: each task is discrete and documented, and the AI interaction model is externalized in the project memory.
+- **ARCHITECTURE** is captured in `ARCHITECTURE.md` and reflected in the site structure and navigation.
+- **TASKS** are tracked in `TASKS.md`, with each phase and task scoped to one prompt and one commit.
+
+## Workflow adoption evidence
+
+- Content is published incrementally through task phases, demonstrating the workflow of publishing project documentation.
+- The site uses a Git-first memory model: all decisions and outputs are stored in versioned files.
+- The Resources and Showcase sections document practical usage and adoption evidence, showing the workflow in action.