coulomb/coordination-engine
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Complete State Hub bootstrap workplans (WP-0001)

Browse Source 
- Review integration files; fill SCOPE where templated
- Document dev workflow in stack-and-commands.md
- Seed WP-0002 implementation workplan; mark bootstrap finished
- Hub sync via fix-consistency
This commit is contained in:
Bernd Worsch
2026-06-22 23:35:06 +02:00
parent 01d4314b3f
commit 1aac55e978
4 changed files with 60 additions and 128 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
.claude/rules/stack-and-commands.md
View File

@@ -1,19 +1,20 @@
## Stack ## Stack
<!-- TODO: Fill in language, frameworks, and key dependencies --> - **Language:** Markdown-first registry and planning repo (no application runtime yet)
- **Language:** - **Key deps:** State Hub ADR-001 workplans, `registry/indexes/capabilities.yaml`
- **Key deps:**
## Dev Commands ## Dev Commands
```bash ```bash
# TODO: Fill in the standard commands for this repo # Orient (offline-safe)
cat .custodian-brief.md
cat INTENT.md
cat SCOPE.md
ls workplans/
# Install dependencies # After workplan or registry edits — from ~/state-hub
make fix-consistency REPO=coordination-engine
# Run tests # Sanity-check markdown / registry edits
git diff --check
# Lint / type check
# Build / package (if applicable)
``` ```

122
SCOPE.md
View File

@@ -1,137 +1,31 @@
# SCOPE # SCOPE
> This file helps you quickly understand what this repository is about, > Lightweight boundary for agents and contributors.
> when it is relevant, and when it is not.
> It is intentionally lightweight and may be incomplete.
--- ---
## One-liner ## One-liner
<!-- Describe the purpose of this repository in one precise sentence. --> Framework for goal-driven digital coordination as communication.
<!-- Example: "Provides a lightweight event router for Kubernetes-native systems." -->
--- ---
## Core Idea ## Core Idea
<!-- What is the main capability or idea behind this repository? --> coordination-engine captures coordination models, specs, and registry entries for how actors align on shared goals.
<!-- What problem does it try to solve? -->
--- ---
## In Scope ## In Scope
<!-- What this repository is responsible for. --> - Coordination specs, history, and registry indexes
<!-- Be explicit and concrete. --> - State Hub workplans and agent instructions
- Capability registration when coordination patterns stabilize
-
-
-
--- ---
## Out of Scope ## Out of Scope
<!-- What this repository deliberately does NOT do. --> - Runtime orchestration engine implementation (future repos)
<!-- This is often more important than "In Scope". --> - Replacing issue trackers or chat systems
-
-
-
---
## Relevant When
<!-- When should someone consider using or exploring this repository? -->
-
-
-
---
## Not Relevant When
<!-- When should someone ignore this repository? -->
-
-
-
---
## Current State
<!-- Rough indication of maturity. No strict format required. -->
- Status: <!-- e.g. concept / experimental / active / stable / deprecated -->
- Implementation: <!-- e.g. idea / partial / substantial / complete -->
- Stability: <!-- e.g. unstable / evolving / stable -->
- Usage: <!-- e.g. none / personal / internal / production -->
<!-- Add any notes that help set expectations. -->
---
## How It Fits
<!-- Where does this repository sit in the bigger picture? -->
- Upstream dependencies:
- Downstream consumers:
- Often used with:
---
## Terminology
<!-- Terms that are important to understand this repo. -->
<!-- Especially useful if naming differs from other repos. -->
- Preferred terms:
- Also known as:
- Potentially confusing terms:
---
## Related / Overlapping Repositories
<!-- List repositories that have similar or adjacent responsibilities. -->
<!-- Helps detect duplication and navigate the ecosystem. -->
- <repo-name> — <!-- how it relates -->
---
## Getting Oriented
<!-- If someone decides to look deeper, where should they start? -->
- Start with:
- Key files / directories:
- Entry points:
---
## Provided Capabilities
<!-- What can this repo's domain provide to other domains on request? -->
<!-- Each capability block is parsed by the state-hub capability catalog ingest. -->
<!-- Remove the examples and add your own, or leave empty if none. -->
<!--
```capability
type: infrastructure
title: Example capability title
description: What this capability provides, in one or two sentences.
keywords: [keyword1, keyword2, keyword3]
```
-->
---
## Notes
<!-- Anything else worth knowing. Keep it short. -->

17
workplans/COORDINATION-WP-0001-statehub-bootstrap.md
View File

@@ -4,7 +4,7 @@ type: workplan
title: "Bootstrap State Hub integration" title: "Bootstrap State Hub integration"
domain: communication domain: communication
repo: coordination-engine repo: coordination-engine
status: ready status: finished
owner: codex owner: codex
topic_slug: communication topic_slug: communication
created: "2026-06-22" created: "2026-06-22"
@@ -20,11 +20,14 @@ Coordination engine for inter-repo workflows.
```task ```task
id: COORDINATION-WP-0001-T01 id: COORDINATION-WP-0001-T01
status: todo status: done
priority: high priority: high
state_hub_task_id: "95769b93-99ce-4cbd-be90-a41dbb87fda0" state_hub_task_id: "95769b93-99ce-4cbd-be90-a41dbb87fda0"
``` ```
Result 2026-06-22: Filled SCOPE.md from INTENT.
Review `INTENT.md`, `SCOPE.md`, `AGENTS.md`, and `.custodian-brief.md`. Review `INTENT.md`, `SCOPE.md`, `AGENTS.md`, and `.custodian-brief.md`.
Replace generated placeholders with repo-specific facts where needed. Replace generated placeholders with repo-specific facts where needed.
@@ -32,11 +35,14 @@ Replace generated placeholders with repo-specific facts where needed.
```task ```task
id: COORDINATION-WP-0001-T02 id: COORDINATION-WP-0001-T02
status: todo status: done
priority: high priority: high
state_hub_task_id: "1c1930c6-8bd7-4979-b0a6-cfa476674129" state_hub_task_id: "1c1930c6-8bd7-4979-b0a6-cfa476674129"
``` ```
Result 2026-06-22: Registry-oriented dev workflow documented.
Identify the repo's install, test, lint, build, and run commands. Add or refine Identify the repo's install, test, lint, build, and run commands. Add or refine
those commands in the agent instructions so future coding sessions can verify those commands in the agent instructions so future coding sessions can verify
changes confidently. changes confidently.
@@ -45,11 +51,14 @@ changes confidently.
```task ```task
id: COORDINATION-WP-0001-T03 id: COORDINATION-WP-0001-T03
status: todo status: done
priority: medium priority: medium
state_hub_task_id: "f74ef97e-8f0a-4d54-b17c-12dcb68ac3f1" state_hub_task_id: "f74ef97e-8f0a-4d54-b17c-12dcb68ac3f1"
``` ```
Result 2026-06-22: Created COORDINATION-WP-0002.
Create the first implementation workplan for the repository's most important Create the first implementation workplan for the repository's most important
next change. After workplan file updates, run from `~/state-hub`: next change. After workplan file updates, run from `~/state-hub`:

28
workplans/COORDINATION-WP-0002-coordination-model-spec.md Normal file
View File

@@ -0,0 +1,28 @@
---
id: COORDINATION-WP-0002
type: workplan
title: "Coordination model specification baseline"
domain: communication
repo: coordination-engine
status: ready
owner: codex
topic_slug: communication
created: "2026-06-22"
updated: "2026-06-22"
state_hub_workstream_id: "2b62c9df-577d-45ce-81a7-cf343e2fb6b0"
---
# Coordination model specification baseline
Draft the first coordination ontology and message lifecycle spec for the engine.
## Author coordination spec v0.1
```task
id: COORDINATION-WP-0002-T01
status: todo
priority: high
state_hub_task_id: "0ece010b-4597-4ae9-b77d-26a3ff8c906f"
```
Write `spec/coordination-model-v0.1.md` covering actors, goals, commitments, and observation loops.