skills/boshu2__agentops
1
0
Fork 0
mirror of https://github.com/boshu2/agentops.git synced 2026-09-14 15:08:13 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: align box-drawing vertical lines in ASCII art

Browse Source 
Systematic pass over 104 markdown files with box-drawing characters.
Fixed 15 files where interior `│` / outer `┌┐└┘` / divider `┬┴` columns
were off by 1-2 cols from their reference row. Zero content changes —
only whitespace and `─` fill chars moved to recover column alignment.

## Files fixed

**docs/** — CI-CD.md, agentops-system-map.md, brownian-ratchet.md,
context-packet.md, curation-pipeline.md, the-science.md,
comparisons/README.md, comparisons/vs-claude-flow.md

**skills/** — SKILL-TIERS.md, swarm/SKILL.md,
crank/references/fire.md, standards/references/test-pyramid.md

**skills-codex/** — crank/references/fire.md,
quickstart/references/full-catalog.md,
standards/references/test-pyramid.md

## Common failure modes found

- Off-by-one closing corners (e.g., `└───────── ┘` with stray space → `└──────────┘`)
- Box width vs content width mismatch (interior row 1-2 chars wider than its `┌┐` box)
- Diverging canonical widths across rows (widened the narrow rows rather
  than truncate content)
- T-junctions (`┬` / `┴`) not aligned with `│` rows above/below

## Scope preserved

- Tree diagrams (`├── file.md` / `│   └── child.md`) — intentional
  variable-width indentation, left alone
- Markdown pipe tables — not ASCII art, not touched
- Content of labels/box text — unchanged

Verified: `scripts/docs-build.sh --check` (mkdocs strict) passes clean.
This commit is contained in:
Boden Fuller
2026-04-19 15:11:31 -04:00
parent 88cb16860c
commit 816a36d83f
15 changed files with 75 additions and 75 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/CI-CD.md
+2 -2
View File
@@ -54,13 +54,13 @@ The validate workflow runs **30 jobs** across 4 tiers of parallelism. Most jobs
│ file-manifest-overlap │
│ skill-lint learning-coherence │
│ bats-tests check-test-staleness │
└────────────────┬──────────────────────────────┘
└──────────────┬────────────────────────────────┘
│
┌──────────────┴──────────────┐
│ go-build (must complete) │
└──┬─────────────┬─────────┬──┘
│ │ │
┌─────┴──┐ ┌──────┴───┐ ┌───┴──────────┐
┌─────┴───┐ ┌──────┴───┐ ┌───┴─────────┐
│ doctor- │ │coverage- │ │json-flag- │
│ check │ │ ratchet │ │consistency │
└────┬────┘ └────┬─────┘ └──────┬──────┘
docs/agentops-system-map.md
+1 -1
View File
@@ -24,7 +24,7 @@ The top-level skill `/rpi` chains the full pipeline. Each node is a skill. Arrow
┌───────────────────────────────────────────────────────────────────┐
│ /rpi │
│ (full pipeline orchestrator) │
└──┬──────────┬───────────┬─────────────┬──────────┬─────────────── ┘
└──┬──────────┬───────────┬─────────────┬──────────┬────────────────┘
│ │ │ │ │
▼ ▼ ▼ ▼ ▼
/research /plan /pre-mortem /crank /post-mortem
docs/brownian-ratchet.md
+3 -3
View File
@@ -87,9 +87,9 @@ FIRE is the reconciliation engine that implements the Brownian Ratchet:
│ (state) (chaos) (ratchet) (recovery) │
│ │ │ │
│ └───────────────────────────────────┘ │
│ (loop) │
│ │
│ EXIT when: all work reaped │
│ (loop) │
│ │
│ EXIT when: all work reaped │
└──────────────────────────────────────────────────────────────┘
```
docs/comparisons/README.md
+2 -2
View File
@@ -37,8 +37,8 @@ The AI coding agent ecosystem has exploded. Here's how the major players stack u
│ │ Fast │ │ Fast │ │ Fast │ │Learn │ → │Recall│ → │Expert│ │
│ │ │ │ │ │ │ │ │ │ │ │ │ │
│ └──────┘ └──────┘ └──────┘ └──────┘ └──────┘ └──────┘ │
│ ↓ ↓ ↓ │ │ │ │
│ [reset] [reset] [reset] └──────────┴──────────┘ │
│ ↓ ↓ ↓ │ │ │ │
│ [reset] [reset] [reset] └──────────┴──────────┘ │
│ COMPOUNDS │
│ │
└─────────────────────────────────────────────────────────────────────┘
docs/comparisons/vs-claude-flow.md
+14 -14
View File
@@ -129,13 +129,13 @@ Claude-Flow excels at coordinating many agents. It doesn't provide the deep sema
### Claude-Flow Architecture
```
┌─────────────────────────────────────────────────────────────────┐
│ CLAUDE-FLOW V3 │
│ │
│ ┌─────────┐ ┌─────────────────────────────────────────┐ │
│ │ Task │───▶│ SWARM COORDINATOR │ │
│ └─────────┘ └─────────────────────────────────────────┘ │
│ │ │
┌────────────────────────────────────────────────────────────────┐
│ CLAUDE-FLOW V3 │
│ │
│ ┌─────────┐ ┌─────────────────────────────────────────┐ │
│ │ Task │───▶│ SWARM COORDINATOR │ │
│ └─────────┘ └─────────────────────────────────────────┘ │
│ │ │
│ ┌────────────────────┼────────────────────┐ │
│ ▼ ▼ ▼ │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
@@ -144,12 +144,12 @@ Claude-Flow excels at coordinating many agents. It doesn't provide the deep sema
│ └────┬────┘ └────┬────┘ └────┬────┘ │
│ │ │ │ │
│ └────────────────────┴────────────────────┘ │
│ │ │
│ ▼ │
│ │ │
│ ▼ │
│ ┌─────────┐ │
│ │ Results │ (session ends, gone) │
│ └─────────┘ │
└─────────────────────────────────────────────────────────────────┘
└────────────────────────────────────────────────────────────────┘
```
### AgentOps Architecture
@@ -168,11 +168,11 @@ Claude-Flow excels at coordinating many agents. It doesn't provide the deep sema
│ └──────┬──────┘ │ │
│ │ │ │
│ ▼ │ │
│ ┌─────────────┐ ┌─────────┐ │ │
│ │ /crank │────▶│ /vibe │──── pass ────────▶│ │
│ ┌─────────────┐ ┌──────────┐ │ │
│ │ /crank │────▶│ /vibe │──── pass ────────▶│ │
│ │ (implement) │ │(validate)│ │ │
│ └─────────────┘ └────┬────┘ │ │
│ │ fail │ │
│ └─────────────┘ └────┬─────┘ │ │
│ │ fail │ │
│ └───────▶ fix ───────────┘ │
│ │
│ Session ends → Learnings extracted → Next session benefits │
docs/context-packet.md
+3 -3
View File
@@ -28,9 +28,9 @@ The packet has five sections, each with a defined character budget, content sour
│ │ TASK │ │ PROTOCOL │ │
│ │ ~4K ch │ │ ~2K ch │ │
│ └─────────┘ └──────────┘ │
│ │
│ Total: ~28K chars / ~7K tokens │
│ Window utilization: <10% (leaves 90%+ for work) │
│ │
│ Total: ~28K chars / ~7K tokens │
│ Window utilization: <10% (leaves 90%+ for work) │
└──────────────────────────────────────────────────────────┘
```
docs/curation-pipeline.md
+3 -3
View File
@@ -500,7 +500,7 @@ The pipeline degrades gracefully. Each version is strictly better than the previ
│
▼
┌──────────────────────────┐
│ STAGE 2: VERIFY │ v1
│ STAGE 2: VERIFY │ v1
│ Mechanical checks: │
│ tests pass? goals up? │
│ → verification metadata │
@@ -508,7 +508,7 @@ The pipeline degrades gracefully. Each version is strictly better than the previ
│
▼
┌──────────────────────────┐
│ STAGE 3: INDEX │ v2
│ STAGE 3: INDEX │ v2
│ Tag by topic, skill, │
│ goal. Update search idx │
│ → ao search, ao lookup │
@@ -516,7 +516,7 @@ The pipeline degrades gracefully. Each version is strictly better than the previ
│
▼
┌──────────────────────────┐
│ STAGE 4: SCORE │ v2
│ STAGE 4: SCORE │ v2
│ 5-dim quality gate: │
│ specificity, action- │
│ ability, novelty, │
docs/the-science.md
+16 -16
View File
@@ -421,43 +421,43 @@ This is why progress can be made one-way at the artifact level, while system-lev
│ │ Feedback: Vibe, Pre-mortem, Citations, Utility scores │ │
│ │ Learning: Retros, Post-mortems, Pattern extraction │ │
│ └─────────────────────────────────────────────────────────┘ │
│ │ │
│ ▼ │
│ COGNITIVE LAYER (40% Rule) │
│ │ │
│ ▼ │
│ COGNITIVE LAYER (40% Rule) │
│ ┌─────────────────────────────────────────────────────────┐ │
│ │ Context utilization: 35% checkpoint, 40% alert │ │
│ │ JIT loading: Load what's needed, when it's needed │ │
│ │ Lost-in-middle prevention: Don't crowd the context │ │
│ └─────────────────────────────────────────────────────────┘ │
│ │ │
│ ▼ │
│ MEMRL LAYER (Utility Learning) │
│ │ │
│ ▼ │
│ MEMRL LAYER (Utility Learning) │
│ ┌─────────────────────────────────────────────────────────┐ │
│ │ Feedback loop: Use → Reward/Penalize → Update utility │ │
│ │ Retrieval: Freshness + Utility scoring │ │
│ │ Result: σ (retrieval effectiveness) improves over time │ │
│ └─────────────────────────────────────────────────────────┘ │
│ │ │
│ ▼ │
│ RATCHET LAYER (Progress Locking) │
│ │ │
│ ▼ │
│ RATCHET LAYER (Progress Locking) │
│ ┌─────────────────────────────────────────────────────────┐ │
│ │ Chaos: Multiple attempts, parallel exploration │ │
│ │ Filter: Validation gates (tests, vibe, CI) │ │
│ │ Ratchet: Merge, close, store (permanent) │ │
│ └─────────────────────────────────────────────────────────┘ │
│ │ │
│ ▼ │
│ THE GOAL (Escape Velocity) │
│ ┌─────────────────────────────────────────────────────────┐ │
│ │ │
│ ▼ │
│ THE GOAL (Escape Velocity) │
│ ┌──────────────────────────────────────────────────────────┐ │
│ │ │ │
│ │ σ × ρ > δ/100 │ │
│ │ │ │
│ │ retrieval × evidence-backed use > aging threshold │ │
│ │ retrieval × evidence-backed use > aging threshold │ │
│ │ │ │
│ │ When true: KNOWLEDGE COMPOUNDS │ │
│ │ │ │
│ └─────────────────────────────────────────────────────────┘ │
│ │
│ └──────────────────────────────────────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────────┘
```
skills-codex/crank/references/fire.md
+3 -3
View File
@@ -16,9 +16,9 @@ FIRE is the reconciliation loop that extracts progress from chaos. Like a forge
│ (state) (chaos) (ratchet) (recovery) │
│ │ │ │
│ └───────────────────────────────────┘ │
│ (loop) │
│ │
│ EXIT when: all children closed │
│ (loop) │
│ │
│ EXIT when: all children closed │
└──────────────────────────────────────────────────────────┘
```
skills-codex/quickstart/references/full-catalog.md
+1 -1
View File
@@ -26,7 +26,7 @@ $swarm ──► parallelize anything: research, brainstorm, implement, council
│ $implement ────► research + plan + build + vibe│
│ $vibe ─────────► $complexity + $council │
│ $pre-mortem ───► $council (failure simulation) │
│ $post-mortem ──► $council + knowledge lifecycle │
│ $post-mortem ──► $council + knowledge lifecycle│
│ $council ──────► parallel judges (multi-model) │
└─────────────────────────────────────────────────┘
```
skills-codex/standards/references/test-pyramid.md
+18 -18
View File
@@ -18,25 +18,25 @@
## Agent Autonomy Boundaries
```
┌─────────────────────────────────────────────────────┐
│ AGENT-AUTONOMOUS (L0–L3) │
│ Agent writes tests AND implementation. │
│ No human input needed for test design. │
│ │
│ L0: Contract — from SPEC.md alone │
│ L1: Unit — TDD RED→GREEN from spec │
│ L2: Integration — from subsystem spec + adapters │
┌───────────────────────────────────────────────────────┐
│ AGENT-AUTONOMOUS (L0–L3) │
│ Agent writes tests AND implementation. │
│ No human input needed for test design. │
│ │
│ L0: Contract — from SPEC.md alone │
│ L1: Unit — TDD RED→GREEN from spec │
│ L2: Integration — from subsystem spec + adapters │
│ L3: Component — agent writes, human defines scenarios│
├─────────────────────────────────────────────────────┤
│ HUMAN-GUIDED (L4–L7) │
│ Human defines WHAT to test. │
│ Agent builds the test infrastructure. │
│ │
│ L4: Smoke — human defines "critical path" │
│ L5: E2E — human designs flow, agent harness │
│ L6: Acceptance— human only validates │
│ L7: Prod — monitors + human judgment │
└─────────────────────────────────────────────────────┘
├───────────────────────────────────────────────────────┤
│ HUMAN-GUIDED (L4–L7) │
│ Human defines WHAT to test. │
│ Agent builds the test infrastructure. │
│ │
│ L4: Smoke — human defines "critical path" │
│ L5: E2E — human designs flow, agent harness │
│ L6: Acceptance— human only validates │
│ L7: Prod — monitors + human judgment │
└───────────────────────────────────────────────────────┘
```
## RPI Phase Mapping
skills/SKILL-TIERS.md
+1 -1
View File
@@ -67,7 +67,7 @@ RESEARCH PLAN IMPLEMENT VALIDATE
┌─────────┐ ┌───────────┐
│ swarm │ │complexity │
└────┬────┘ │ + council │
│ └───────────┘
│ └───────────┘
▼
┌─────────┐
│ crank │
skills/crank/references/fire.md
+3 -3
View File
@@ -16,9 +16,9 @@ FIRE is the reconciliation loop that extracts progress from chaos. Like a forge
│ (state) (chaos) (ratchet) (recovery) │
│ │ │ │
│ └───────────────────────────────────┘ │
│ (loop) │
│ │
│ EXIT when: all children closed │
│ (loop) │
│ │
│ EXIT when: all children closed │
└──────────────────────────────────────────────────────────┘
```
skills/standards/references/test-pyramid.md
+1 -1
View File
@@ -57,7 +57,7 @@ The Traditional Pyramid The AI-Native Shape
│ regression guards, L0 for contracts, L3 for subsystems. │
│ │
│ L0: Contract — from SPEC.md alone │
│ L1: Unit — always write for regression safety │
│ L1: Unit — always write for regression safety │
│ L2: Integration — DEFAULT for all agent-written tests │
│ L3: Component — agent writes, human defines scenarios │
├───────────────────────────────────────────────────────────┤
skills/swarm/SKILL.md
+4 -4
View File
@@ -202,10 +202,10 @@ File Ownership Map (Wave N):
┌─────────────────────────────┬──────────┬──────────┐
│ File │ Owner │ Conflict │
├─────────────────────────────┼──────────┼──────────┤
│ src/auth/middleware.go │ task-1 │ │
│ src/auth/middleware_test.go │ task-1 │ │
│ src/api/routes.go │ task-2 │ │
│ src/config/settings.go │ task-1,3 │ YES │
│ src/auth/middleware.go │ task-1 │ │
│ src/auth/middleware_test.go │ task-1 │ │
│ src/api/routes.go │ task-2 │ │
│ src/config/settings.go │ task-1,3 │ YES │
└─────────────────────────────┴──────────┴──────────┘
Conflicts: 1 (resolved: serialized task-3 into sub-wave 2)
```