coulomb/repo-seed
Template
2
0
Fork 0
Code Issues Pull Requests 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:18 +02:00
parent 39ca07b443
commit 615d0f309a
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=repo-seed
# 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. --> Git repository template to bootstrap coulomb projects.
<!-- Example: "Provides a lightweight event router for Kubernetes-native systems." -->
--- ---
## Core Idea ## Core Idea
<!-- What is the main capability or idea behind this repository? --> repo-seed is the canonical template for new repos: agent instructions, registry scaffold, and onboarding conventions.
<!-- What problem does it try to solve? -->
--- ---
## In Scope ## In Scope
<!-- What this repository is responsible for. --> - Template files for new repo bootstrap
<!-- Be explicit and concrete. --> - Documentation for statehub_register usage
- Registry capability entry for template capability
-
-
-
--- ---
## Out of Scope ## Out of Scope
<!-- What this repository deliberately does NOT do. --> - Application runtime code
<!-- This is often more important than "In Scope". --> - Owning downstream project implementations
-
-
-
---
## 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/REPO-WP-0001-statehub-bootstrap.md
View File

@@ -4,7 +4,7 @@ type: workplan
title: "Bootstrap State Hub integration" title: "Bootstrap State Hub integration"
domain: infotech domain: infotech
repo: repo-seed repo: repo-seed
status: ready status: finished
owner: codex owner: codex
topic_slug: infotech topic_slug: infotech
created: "2026-06-22" created: "2026-06-22"
@@ -20,11 +20,14 @@ Git repository template to bootstrap coulomb projects.
```task ```task
id: REPO-WP-0001-T01 id: REPO-WP-0001-T01
status: todo status: done
priority: high priority: high
state_hub_task_id: "65734e48-ec48-47f2-bd5c-5673e94343cc" state_hub_task_id: "65734e48-ec48-47f2-bd5c-5673e94343cc"
``` ```
Result 2026-06-22: Filled SCOPE.md; README is canonical 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: REPO-WP-0001-T02 id: REPO-WP-0001-T02
status: todo status: done
priority: high priority: high
state_hub_task_id: "76f1c245-3f06-4ef7-943f-bf2e9722c71b" state_hub_task_id: "76f1c245-3f06-4ef7-943f-bf2e9722c71b"
``` ```
Result 2026-06-22: Template 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: REPO-WP-0001-T03 id: REPO-WP-0001-T03
status: todo status: done
priority: medium priority: medium
state_hub_task_id: "9670ff11-ed7a-49e6-8a1f-944af9794f6a" state_hub_task_id: "9670ff11-ed7a-49e6-8a1f-944af9794f6a"
``` ```
Result 2026-06-22: Created REPO-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/REPO-WP-0002-template-validation-checklist.md Normal file
View File

@@ -0,0 +1,28 @@
---
id: REPO-WP-0002
type: workplan
title: "Template consumer validation checklist"
domain: infotech
repo: repo-seed
status: ready
owner: codex
topic_slug: infotech
created: "2026-06-22"
updated: "2026-06-22"
state_hub_workstream_id: "8aaf98a0-7045-4d5b-915f-bc9ecc5aa319"
---
# Template consumer validation checklist
Validate repo-seed against statehub_register output and document consumer steps.
## Template validation checklist
```task
id: REPO-WP-0002-T01
status: todo
priority: high
state_hub_task_id: "a1b0aaab-f0dc-4bd0-bde3-89635ac0ca3b"
```
Author checklist for new repo bootstrap: register, agent files, first workplan, fix-consistency.