Complete State Hub bootstrap workplans (WP-0001)

- 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:
2026-06-22 23:35:26 +02:00
parent 451cf46c16
commit 0f64ddf55d
4 changed files with 60 additions and 128 deletions

View File

@@ -1,19 +1,20 @@
## Stack
<!-- TODO: Fill in language, frameworks, and key dependencies -->
- **Language:**
- **Key deps:**
- **Language:** Markdown-first registry and planning repo (no application runtime yet)
- **Key deps:** State Hub ADR-001 workplans, `registry/indexes/capabilities.yaml`
## Dev Commands
```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=vantage-point
# Run tests
# Lint / type check
# Build / package (if applicable)
# Sanity-check markdown / registry edits
git diff --check
```

122
SCOPE.md
View File

@@ -1,137 +1,31 @@
# SCOPE
> This file helps you quickly understand what this repository is about,
> when it is relevant, and when it is not.
> It is intentionally lightweight and may be incomplete.
> Lightweight boundary for agents and contributors.
---
## One-liner
<!-- Describe the purpose of this repository in one precise sentence. -->
<!-- Example: "Provides a lightweight event router for Kubernetes-native systems." -->
Generic system for exploring dependency structures as network-based graph models (NBGM).
---
## Core Idea
<!-- What is the main capability or idea behind this repository? -->
<!-- What problem does it try to solve? -->
Vantage Point unifies entity/relationship inspection and reasoning across arbitrary domains.
---
## In Scope
<!-- What this repository is responsible for. -->
<!-- Be explicit and concrete. -->
-
-
-
- NBGM specs, registry, and exploratory docs
- State Hub workplans for graph exploration features
- Alignment with repo-scoping and fabric graph models
---
## Out of Scope
<!-- What this repository deliberately does NOT do. -->
<!-- This is often more important than "In Scope". -->
- Production graph database hosting
- Replacing railiance-fabric ingestion
-
-
-
---
## 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. -->

View File

@@ -4,7 +4,7 @@ type: workplan
title: "Bootstrap State Hub integration"
domain: infotech
repo: vantage-point
status: ready
status: finished
owner: codex
topic_slug: infotech
created: "2026-06-22"
@@ -20,11 +20,14 @@ Vantage point observability tooling.
```task
id: VANTAGE-WP-0001-T01
status: todo
status: done
priority: high
state_hub_task_id: "a99f9783-0490-4a13-b875-ad0851662aad"
```
Result 2026-06-22: Filled SCOPE.md from INTENT.
Review `INTENT.md`, `SCOPE.md`, `AGENTS.md`, and `.custodian-brief.md`.
Replace generated placeholders with repo-specific facts where needed.
@@ -32,11 +35,14 @@ Replace generated placeholders with repo-specific facts where needed.
```task
id: VANTAGE-WP-0001-T02
status: todo
status: done
priority: high
state_hub_task_id: "b2b0f201-2eb9-4197-8de7-56f404bf623f"
```
Result 2026-06-22: Registry workflow documented.
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
changes confidently.
@@ -45,11 +51,14 @@ changes confidently.
```task
id: VANTAGE-WP-0001-T03
status: todo
status: done
priority: medium
state_hub_task_id: "4bce0d0d-d4ad-4c5a-ae12-75ec8a40455b"
```
Result 2026-06-22: Created VANTAGE-WP-0002.
Create the first implementation workplan for the repository's most important
next change. After workplan file updates, run from `~/state-hub`:

View File

@@ -0,0 +1,28 @@
---
id: VANTAGE-WP-0002
type: workplan
title: "NBGM model specification baseline"
domain: infotech
repo: vantage-point
status: ready
owner: codex
topic_slug: infotech
created: "2026-06-22"
updated: "2026-06-22"
state_hub_workstream_id: "bd2d70eb-4c83-4fa3-94ff-7f44b32aeba9"
---
# NBGM model specification baseline
Author the network-based graph model specification baseline.
## NBGM spec v0.1
```task
id: VANTAGE-WP-0002-T01
status: todo
priority: high
state_hub_task_id: "d13bd898-15b0-41ba-aa3b-8c5f96a09fd8"
```
Write spec covering nodes, edges, attributes, provenance, and inspection operations.