---
title: "llm-wiki-sync Circular Flow"
topic: technical
data_type: cycle
complexity: moderate
point_count: 7
source_language: zh
user_language: en
---

## Main Topic
A cyclical knowledge management pipeline that transforms raw notes into structured wiki pages through continuous LLM-powered ingestion, extraction, and reuse.

## Learning Objectives
After viewing this infographic, the viewer will understand:
1. The continuous circular flow of llm-wiki-sync from raw notes to reusable knowledge
2. The key extraction outputs: Summary, Claims, Entities, Concepts, Connections
3. How feedback and reuse complete the cycle back to new raw material

## Target Audience
- **Knowledge Level**: Intermediate technical audience
- **Context**: Developers and knowledge workers interested in AI-powered knowledge management
- **Expectations**: Clear understanding of the llm-wiki-sync pipeline and its cyclical nature

## Content Type Analysis
- **Data Structure**: Cyclic process with recurring steps
- **Key Relationships**: Raw → Ingest → Extract → Source Page → Graph/Site → Reuse → Raw (feedback loop)
- **Visual Opportunities**: Circular flow with nodes for each stage, arrows showing direction, center concept

## Key Data Points (Verbatim)

### Core Pipeline Steps
1. **Raw Note** - Original document in raw/ folder
2. **Ingest** - LLM analyzes and extracts structured information
3. **Extract** - Summary, Claims, Quotes, Entities, Concepts, Connections
4. **Source Page** - Structured wiki/sources/ page with frontmatter
5. **Graph & Site** - graph.json and Quartz static site generation
6. **Reuse** - Synthesize, query, create new content from structured knowledge
7. **Feedback Loop** - New raw notes created from reused knowledge

### Extraction Outputs
- **Summary**: 核心主题, 问题域, 方法/机制, 结论/价值
- **Key Claims**: Verifiable assertions extracted from text
- **Key Entities**: LaunchDarkly, HP, Christian Dior, etc.
- **Key Concepts**: RTO, RPO, Feature Flag, Kill Switch, Gradual Rollout
- **Connections**: depends_on, enables, provides relationships

### Key Quotes
- "RTO is about speed: how fast you get back online. RPO is about data: how much you can afford to lose."
- "Deploy != Release. Feature flags change this. You can deploy code to production without releasing it to users."

## Layout × Style Signals
- Content type: cycle → circular-flow
- Tone: technical educational → chalkboard
- Audience: developers → clear, legible, professional
- Complexity: moderate → balanced density with clear visual hierarchy

## Design Instructions (from user input)
- **Layout**: circular-flow (NOT linear - must emphasize recurring cycle)
- **Style**: chalkboard (dark background, hand-drawn chalk accents)
- **Aspect**: 16:9 landscape
- **Language**: English
- Circular flow showing: raw note -> ingest -> extract -> source page -> graph/static site -> reuse/feedback -> knowledge base
- Include core extraction outputs as recurring nodes/callouts
- Keep text concise and legible
- Dark chalkboard background with hand-drawn chalk accents
- Avoid clutter, make cycle visually clear and publication-ready

## Recommended Combinations
1. **circular-flow + chalkboard** (Recommended): Perfect match for cycle/process content with chalkboard aesthetic
2. **hub-spoke + technical-schematic**: For emphasizing central concepts with technical precision
3. **bento-grid + craft-handmade**: For multiple topic overview with friendly handmade feel