coulomb/reuse-surface
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
reuse-surface/SCOPE.md

316 lines
16 KiB
Markdown
Raw Permalink Normal View History

Seeded intent and maturity model
2026-06-15 00:04:09 +02:00
# SCOPE
## One-liner
Capability registry for planning and implementation reuse based on discovery and delivery maturity.
## Core Idea
Bootstrap and first implementation
2026-06-15 01:04:30 +02:00
`reuse-surface` provides a registry-centric reuse layer for capabilities. It
makes capabilities visible, comparable, assessable, and reusable for planning,
implementation, and operation. A capability that is not registered is invisible
for reuse within this product boundary.
Seeded intent and maturity model
2026-06-15 00:04:09 +02:00
## In Scope
Bootstrap and first implementation
2026-06-15 01:04:30 +02:00
- Maintain the capability maturity model, standards, schemas, registry formats,
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
sample entries, indexes, validation guidance, CLI tooling, hub service, and
agent instructions.
Bootstrap and first implementation
2026-06-15 01:04:30 +02:00
- Keep `INTENT.md`, `specs/`, registry artifacts, and State Hub workplans
aligned on the registry-first reuse boundary.
- Support humans and agents as registry consumers through Markdown-first
authoring and machine-readable metadata.
- Record decisions, progress, and workplan status through State Hub.
Complete REUSE-WP-0003: registry CLI, docs alignment, and coverage Align INTENT.md with delivered layout, add CapabilityRegistryConcept guide, extend schema with promotion_history, ship reuse-surface validate/query/export CLI, register three more helix_forge capabilities, and refresh SCOPE and gap analysis to reflect A3 tooling and D5/A3/C4/R2 self-assessment.
2026-06-15 01:12:09 +02:00
- Verify changes with `reuse-surface validate`, `git diff --check`, and ADR-001
Bootstrap and first implementation
2026-06-15 01:04:30 +02:00
consistency checks.
Seeded intent and maturity model
2026-06-15 00:04:09 +02:00
## Out of Scope
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
- Host or operate the registered capabilities themselves (except the federation
hub coordinator, which stores repo metadata and index URLs only).
Bootstrap and first implementation
2026-06-15 01:04:30 +02:00
- Replace package registries, service catalogs, issue trackers, or project
management systems.
- Judge internal code quality as capability maturity.
- Own unrelated adjacent systems or make irreversible operational decisions
without human approval.
Seeded intent and maturity model
2026-06-15 00:04:09 +02:00
Add standard SCOPE.md sections and capability blocks (REUSE-WP-0020-T07) Clears the hub scope check's C5b/C5c warnings: Relevant When, Not Relevant When, How It Fits, Terminology, Related / Overlapping, and Provided Capabilities were all missing, along with any fenced capability block. The Terminology section calls out something this workplan ran into for real: the fenced `capability` blocks in SCOPE.md (type/title/description/keywords) look like index rows in registry/indexes/capabilities.yaml but are a different shape and are not validated. evidence-binder copied the SCOPE block shape into its index, which is why it had no `id` and broke federation composition. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-21 03:21:45 +02:00
## Relevant When
- Deciding whether a capability already exists before planning or building one
(`reuse-surface plan-check`).
- Registering a new capability so it becomes visible for reuse.
- Promoting a capability along the D/A/C/R maturity axes with evidence.
- Comparing candidate capabilities by maturity, scope, relations, and consumer
guidance.
- Detecting overlap or duplication between capabilities across repos.
- Adding a sibling repo to the federation, or debugging why its index does not
appear in the federated view.
- Recording or interpreting reuse telemetry as R-axis evidence.
---
## Not Relevant When
- Hosting, running, or operating the capabilities themselves — the registry
describes capabilities, it does not execute them.
- Looking for a package registry, service catalog, issue tracker, or project
management system. Those are different tools with different guarantees.
- Judging internal code quality. Maturity here is about discovery and delivery,
not about how the implementation is written.
- Deploying the hub. The Kubernetes release lives in `railiance-apps`
(`charts/reuse-surface/`); this repo owns the image and the deploy guide only.
- Routing credentials. See `.claude/rules/credential-routing.md` — ops-warden
issues SSH certificates, OpenBao holds secrets.
---
## How It Fits
`reuse-surface` sits between planning and implementation. A workplan or intent
is checked against the federated index before work starts; the verdict is
reuse, extend, or new. Capabilities registered by sibling repos flow in through
federation, and observed reuse flows back as maturity evidence.
- **Upstream:** each sibling repo publishes `registry/indexes/capabilities.yaml`
from its own checkout. The repo owns its entries; this registry never edits
them.
- **Here:** the federation composer merges member indexes into
`registry/indexes/federated.yaml`, and the hosted hub serves the same view at
`GET /v1/federated`.
- **Downstream:** humans and agents query the index, the CLI, or the hub before
building. `plan-check --record-outcome` returns telemetry that feeds the
R axis.
State Hub is the coordination layer, not the registry: workplans and decisions
live there, capability descriptions live here.
---
## Terminology
| Term | Meaning |
|---|---|
| **Capability** | A reusable unit of function, described by a registry entry. Not a package, not a service — either can implement one. |
| **Maturity vector** | `D / A / C / R` — Discovery, Availability, Consumability, Reliability. See `specs/CapabilityMaturityStandard.md`. |
| **Registry entry** | Markdown with YAML front matter under `registry/capabilities/`, validated against `schemas/capability.schema.yaml`. |
| **Index** | `registry/indexes/capabilities.yaml` — one row per entry, the discovery surface for this repo. |
| **Federated index** | The composed view across all member repos. |
| **Member / source** | A repo registered in `registry/federation/sources.yaml` or on the hub. |
| **Hub** | The hosted service at `https://reuse.coulomb.social` that composes and serves the federated index. |
| **Promotion** | Raising a maturity axis, backed by evidence and recorded in `promotion_history`. |
**Note on two similar formats.** The fenced `capability` blocks in a repo's
`SCOPE.md` (`type` / `title` / `description` / `keywords`) are *not* the same
shape as index rows in `registry/indexes/capabilities.yaml`
(`id` / `name` / `summary` / `vector` / `domain` / `status` / `owner` / `path` /
`tags` / `consumption_modes`). SCOPE blocks are a prose-level advertisement;
index rows are validated registry data and require an `id`. Copying one shape
into the other is a real and observed failure mode — it silently breaks
federation for that member.
---
## Related / Overlapping
| Repo / system | Relationship |
|---|---|
| **State Hub** (`~/state-hub`) | Coordination read model: workplans, tasks, decisions, progress. Complementary — it tracks *work*, this tracks *capabilities*. |
| **railiance-apps** | Owns the Kubernetes release for the hub (`charts/reuse-surface/`, RAILIANCE-WP-0007). Deploys what this repo builds. |
| **ops-warden** | Credential and access routing. Explicitly out of scope here. |
| **Sibling domain repos** | Federation members. Each owns its own entries and index; this repo owns only composition and the standard. |
| **Package registries** (PyPI, npm, OCI) | Distribute artifacts. This registry describes capabilities and may reference artifacts, but does not host them. |
---
## Provided Capabilities
```capability
type: registry
title: Capability registration and maturity assessment
description: Register capabilities as validated Markdown entries with D/A/C/R maturity vectors, promotion history, and evidence, so they become discoverable and comparable for planning and implementation reuse.
keywords: [registry, capability, maturity, discovery, promotion, reuse, governance]
```
```capability
type: service
title: Capability index federation
description: Compose capability indexes published by many repos into one federated view, served locally by CLI and in production by a hosted hub with webhook-driven refresh and staleness visibility.
keywords: [federation, index, compose, hub, webhook, capabilities, cross-repo]
```
```capability
type: tooling
title: Pre-build reuse check
description: Match a draft workplan or free-text intent against the federated capability index and return a reuse, extend, or new verdict, bridging a new verdict to a State Hub capability request and recording the outcome as reuse telemetry.
keywords: [plan-check, reuse, verdict, planning, telemetry, capability-request]
```
---
Add intent-scope gap analysis and REUSE-WP-0003 workplan Document gaps between INTENT.md and SCOPE.md, refresh SCOPE with current MVP capabilities, and seed the follow-up workplan for documentation alignment, registry CLI tooling, and coverage growth.
2026-06-15 01:09:53 +02:00
## What Is Possible Now
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
The MVP registry foundation, CLI tooling (REUSE-WP-0003), federation stack
(WP-0005/0010), and hosted hub (WP-0011) are in place. Humans and agents can:
Add intent-scope gap analysis and REUSE-WP-0003 workplan Document gaps between INTENT.md and SCOPE.md, refresh SCOPE with current MVP capabilities, and seed the follow-up workplan for documentation alignment, registry CLI tooling, and coverage growth.
2026-06-15 01:09:53 +02:00
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
- **Discover capabilities** via `registry/indexes/capabilities.yaml`,
`reuse-surface query`, or `GET https://reuse.coulomb.social/v1/federated`
Add intent-scope gap analysis and REUSE-WP-0003 workplan Document gaps between INTENT.md and SCOPE.md, refresh SCOPE with current MVP capabilities, and seed the follow-up workplan for documentation alignment, registry CLI tooling, and coverage growth.
2026-06-15 01:09:53 +02:00
- **Add a new capability** at D0/A0/C0/R0 using
`templates/capability-entry.template.md`
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
- **Promote capabilities** with evidence, `promotion_history`, and index vector
updates
Add intent-scope gap analysis and REUSE-WP-0003 workplan Document gaps between INTENT.md and SCOPE.md, refresh SCOPE with current MVP capabilities, and seed the follow-up workplan for documentation alignment, registry CLI tooling, and coverage growth.
2026-06-15 01:09:53 +02:00
- **Compare candidates** using maturity vectors, scope, relations, and consumer
Complete REUSE-WP-0003: registry CLI, docs alignment, and coverage Align INTENT.md with delivered layout, add CapabilityRegistryConcept guide, extend schema with promotion_history, ship reuse-surface validate/query/export CLI, register three more helix_forge capabilities, and refresh SCOPE and gap analysis to reflect A3 tooling and D5/A3/C4/R2 self-assessment.
2026-06-15 01:12:09 +02:00
guidance
Add intent-scope gap analysis and REUSE-WP-0003 workplan Document gaps between INTENT.md and SCOPE.md, refresh SCOPE with current MVP capabilities, and seed the follow-up workplan for documentation alignment, registry CLI tooling, and coverage growth.
2026-06-15 01:09:53 +02:00
- **Record expectations** through `external_evidence.completeness` and
Complete REUSE-WP-0003: registry CLI, docs alignment, and coverage Align INTENT.md with delivered layout, add CapabilityRegistryConcept guide, extend schema with promotion_history, ship reuse-surface validate/query/export CLI, register three more helix_forge capabilities, and refresh SCOPE and gap analysis to reflect A3 tooling and D5/A3/C4/R2 self-assessment.
2026-06-15 01:12:09 +02:00
`external_evidence.reliability`
- **Validate entries automatically** with `reuse-surface validate`
- **Export a machine-readable bundle** with `reuse-surface export`
Complete REUSE-WP-0004: CI, overlap detection, and catalog generation Add Gitea CI workflow for registry validation, reuse-surface overlaps and catalog commands, generated catalog artifacts, and documentation updates closing gap analysis priorities 9-11.
2026-06-15 01:20:31 +02:00
- **Detect overlap candidates** with `reuse-surface overlaps`
- **Generate a human-readable catalog** with `reuse-surface catalog`
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
- **Browse a searchable catalog** at `docs/catalog/search.html`
Complete REUSE-WP-0005: registry federation and relation graphs Add federation manifest and schema, federation compose and graph CLI commands, relation cycle/reference checks, federated index and Mermaid graph artifacts, RegistryFederation guide, and CI validation updates.
2026-06-15 01:43:02 +02:00
- **Compose federated indexes** with `reuse-surface federation compose`
Complete WP-0010: HTTP remote federation with cache Extend federation manifest schema for url sources with auth and TTL metadata. Fetch remote capability indexes over HTTP(S), cache under registry/federation/cache/, and fall back to stale cache on fetch failure. Add --refresh flag, seven federation tests, and updated federation docs.
2026-06-15 02:28:44 +02:00
(local paths and remote HTTP URLs with cache)
Finish REUSE-WP-0011: document hub workflow and close workplan Hub deployed at reuse.coulomb.social (image cb7a6e4). Dogfood registration verified; update RegistryFederation, SCOPE, and gap analysis.
2026-06-15 10:15:36 +02:00
- **Register federation sources on the hosted hub** with `reuse-surface hub`
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
against `https://reuse.coulomb.social`
Implement REUSE-WP-0012 federation scale and intent alignment Add hub sync and report cohorts CLI commands with pytest coverage, document sibling index publish contract and hub hardening path, align INTENT layout, raise external evidence on three registry entries, and close gap priorities 19-23 (priority 18 deferred on sibling index blocks).
2026-06-16 00:42:50 +02:00
- **Sync local federation manifest from hub** with `reuse-surface hub sync`
- **Export planning cohorts** with `reuse-surface report cohorts`
REUSE-WP-0015: dedup owner entries, add report gaps (T02/T03/T05) Remove 17 owner-migrated capabilities from reuse-surface index (keep activity-core stub). Add report gaps CLI, roster stats + gaps CI steps. T01 remains operator-blocked on Gitea publish.
2026-06-16 02:22:17 +02:00
- **Report registry gaps** with `reuse-surface report gaps` (roster blockers,
empty scaffolds, dedup stubs)
Implement REUSE-WP-0013 registry establish, update, and stats Add stats, establish (scaffold, publish-check, discover), and update CLI commands with optional llm-connect bridge, validate --root for sibling repos, pytest coverage, and documentation for sibling registry onboarding.
2026-06-16 01:21:01 +02:00
- **Bootstrap a sibling registry** with `reuse-surface establish --scaffold`
- **Verify index publish readiness** with `reuse-surface establish --publish-check`
docs: refresh SCOPE and INTENT↔SCOPE gap analysis post WP-0014 SCOPE.md reflects 60-repo rollout, federation compose metrics, and open publish/dedup blockers. IntentScopeGapAnalysis maps INTENT success criteria to delivery and proposes priorities 25–27.
2026-06-16 02:17:07 +02:00
- **View registry stats** with `reuse-surface stats` (per-repo or
`--roster registry/federation/local-repo-roster.yaml --federation-ready`)
Implement REUSE-WP-0013 registry establish, update, and stats Add stats, establish (scaffold, publish-check, discover), and update CLI commands with optional llm-connect bridge, validate --root for sibling repos, pytest coverage, and documentation for sibling registry onboarding.
2026-06-16 01:21:01 +02:00
- **Draft or refresh entries** with `reuse-surface establish --discover` and
`reuse-surface update` (optional llm-connect backend)
WP-0016 finished: interactive registry maintain with llm-connect automation Closes the registry maintenance loop from inside each domain repo: interactive prompting for judgment calls, full automation for safe and high-confidence changes, both backed by the llm-connect HTTP bridge. - New modules: maintain.py, maintain_llm.py, patches.py, interactive.py - Schema: schemas/registry-patch.schema.json - CLI: reuse-surface maintain; establish --scaffold --hook - Sibling templates: Makefile fragment, pre-commit hook - Deterministic signal collectors extended; validate cwd auto-detect - Docs, gap priority 28, SCOPE update - Tests: test_maintain.py, test_interactive.py (59 pytest total) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-18 04:00:39 +02:00
- **Maintain registry interactively or automatically** with `reuse-surface maintain`
(TTY prompts, `--auto`, optional llm-connect, `--publish` chain)
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
- **Run the hub locally or in a container** with `reuse-surface serve`
Complete REUSE-WP-0005: registry federation and relation graphs Add federation manifest and schema, federation compose and graph CLI commands, relation cycle/reference checks, federated index and Mermaid graph artifacts, RegistryFederation guide, and CI validation updates.
2026-06-15 01:43:02 +02:00
- **Generate relation graphs** with `reuse-surface graph`
Complete WP-0006 through WP-0009: registry expansion, catalog, graph, tests Register six new capabilities (12 total), add searchable catalog UI and graph explorer, introduce pytest suite with CI fail-on-warnings, and close gap analysis priorities 13 and 16. WP-0010 remains backlog for network federation.
2026-06-15 02:24:20 +02:00
- **Explore relations interactively** at `docs/graph/index.html`
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
- **Avoid duplicates** by querying the index and checking overlaps before adding
entries
REUSE-WP-0018 T01/T02/T04/T06: plan-check deterministic matching + State Hub bridge T01: specs/PlanCheck.md design doc, plan-check-result.schema.json and reuse-event.schema.json (the latter shared with WP-0019's reuse telemetry). T02: reuse_surface/plan_check.py + 'reuse-surface plan-check' CLI command. Deterministic token-Jaccard matching against registry/indexes/federated.yaml (reuses overlaps.py's TOKEN_RE rather than a second scoring method), with reuse/extend/new verdicts, markdown and --format json output, staleness warning, and --record-outcome JSONL telemetry. T04: reuse_surface/statehub_bridge.py bridges plan-check 'new' verdicts to State Hub capability requests (--file-request) and surfaces open requests with no matching capability (report gaps --check-capability-requests, opt-in to stay offline-safe). Verified against the live local State Hub API; status field (not catalog_entry_id presence) is the correct open/closed signal, and the list endpoint needs a longer timeout than the health check (~7s observed with 5 rows). T06: docs (tools/README.md, RegistryFederation.md, SCOPE.md, IntentScopeGapAnalysis.md priority 29) and an informational CI smoke step. T03 (LLM rerank) not started -- llm-connect isn't running on this workstation. T05 (ecosystem rollout) remains blocked: WP-0017 has drafted entries for all 61 repos but they're still local-only pending its own T05 push/publish pass, so the federated index isn't yet worth rolling out plan-check as ecosystem convention. 16 new tests, all mocked -- no network calls in the default test run. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-07 00:57:18 +02:00
- **Check before building** with `reuse-surface plan-check` (REUSE-WP-0018) —
match a draft workplan or free-text intent against the federated index and
get a reuse/extend/new verdict; `--file-request` bridges a `new` verdict to
a State Hub capability request; `report gaps --check-capability-requests`
surfaces open requests with no matching capability
REUSE-WP-0019-T04: reuse telemetry store and recording Implements the hub side of the shared reuse-event schema (already drafted in WP-0018-T01, schemas/reuse-event.schema.json): a SQLite reuse_events table, POST /v1/reuse-events (token-auth), GET /v1/reuse-events?capability_id= (read-only). reuse_surface/plan_check.py: refactored record_outcome around a new shared post_or_fallback_reuse_event() helper -- tries the hub first, falls back to the local JSONL only on failure/unreachability, never both. New record_manual_reuse_event() backs a new CLI command, reuse-surface record-reuse, for retroactive facts recorded outside plan-check. Privacy/scope (repo slugs and capability ids only, no code, no secrets) is enforced structurally via the schema's additionalProperties: false, not just by convention. 21 new pytest cases, 145 total pass. Live-verified against a real running hub instance: POST/GET /v1/reuse-events directly, record-reuse and plan-check --record-outcome both posting successfully to the hub, and -- after actually killing the hub process -- confirmed the fallback path writes correctly to the local JSONL instead of erroring. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-07 22:32:19 +02:00
- **Get automatic hub refresh** (REUSE-WP-0019-T02/T03) — a Forgejo push
REUSE-WP-0019-T03: add Forgejo Actions workflows (part 2 of prior commit) The .forgejo/workflows/ files and doc updates described in 4862ed6 didn't actually get staged there (git add silently skipped them after an earlier pathspec miss on the already-deleted .gitea file) -- committing them now. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-07 21:25:01 +02:00
webhook (`POST /v1/webhooks/forgejo`, HMAC-signed) recomposes the hub's
federated index when a registered repo's `registry/indexes/` changes,
with `composed_at`/`stale` visibility on `GET /v1/federated` and a
scheduled fallback recompose if a webhook delivery is ever missed
REUSE-WP-0019-T04: reuse telemetry store and recording Implements the hub side of the shared reuse-event schema (already drafted in WP-0018-T01, schemas/reuse-event.schema.json): a SQLite reuse_events table, POST /v1/reuse-events (token-auth), GET /v1/reuse-events?capability_id= (read-only). reuse_surface/plan_check.py: refactored record_outcome around a new shared post_or_fallback_reuse_event() helper -- tries the hub first, falls back to the local JSONL only on failure/unreachability, never both. New record_manual_reuse_event() backs a new CLI command, reuse-surface record-reuse, for retroactive facts recorded outside plan-check. Privacy/scope (repo slugs and capability ids only, no code, no secrets) is enforced structurally via the schema's additionalProperties: false, not just by convention. 21 new pytest cases, 145 total pass. Live-verified against a real running hub instance: POST/GET /v1/reuse-events directly, record-reuse and plan-check --record-outcome both posting successfully to the hub, and -- after actually killing the hub process -- confirmed the fallback path writes correctly to the local JSONL instead of erroring. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-07 22:32:19 +02:00
- **Record reuse telemetry** (REUSE-WP-0019-T04) — `plan-check
--record-outcome` and `reuse-surface record-reuse` post facts to
`POST /v1/reuse-events` when the hub is reachable, falling back to
`registry/telemetry/plan-check-events.jsonl` otherwise (same schema
either way); `GET /v1/reuse-events?capability_id=` aggregates them
REUSE-WP-0019-T05: reuse telemetry aggregation into R-axis evidence reuse_surface/reports.py: collect_reuse_events() merges the hub's GET /v1/reuse-events (if reachable) with this repo's local JSONL fallback, deduped. collect_reuse_report() aggregates per-capability consumer counts, outcome breakdown, and last-used. collect_reused_by_suggestions() proposes evidence-gated relation_add patches -- only for capabilities this repo owns, only for consumer repos not already listed -- reusing the existing patches.py:apply_patches mechanism (relation_add already isn't in SAFE_DETERMINISTIC_KINDS, so it was already never auto-applied by maintain --auto). New CLI: reuse-surface report reuse [--capability-id] [--format] [--suggest-relations] [--apply]. --apply requires --suggest-relations and is the only thing that writes -- nothing happens automatically from telemetry alone. schemas/capability.schema.yaml: added relations.reused_by as a new repoSlugList type, distinct from the existing capability-id relations, since reused-by targets are consumer repo slugs. specs/CapabilityMaturityStandard.md Sec8.9: what observed-reuse evidence counts toward R2->R3 (single corroborating consumer) vs R3->R4+ (multiple independent consumers) and what it never substitutes for. 19 new pytest cases, 162 total pass. Live-verified with synthetic local events against a real capability entry: --suggest-relations --apply correctly wrote relations.reused_by via the real apply_patches path (reverted after, since it was a smoke test). Deliberately deferred: surfacing consumer counts in the catalog/graph -- graph.py's relation model is capability-to-capability edges, a different namespace than repo-slug reused_by targets; catalog.py doesn't currently parse full front matter per entry. Left for a follow-up. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-07 22:47:51 +02:00
- **Aggregate reuse telemetry into R-axis evidence** (REUSE-WP-0019-T05) —
`reuse-surface report reuse` shows per-capability consumer counts,
outcomes, and last-used; `--suggest-relations` proposes evidence-gated
`relations.reused_by` patches (via the same `apply_patches` mechanism
`maintain` uses), applied only with an explicit `--apply` — never
automatic. `specs/CapabilityMaturityStandard.md` §8.9 documents what
observed-reuse evidence does (and doesn't) count toward R2/R3+
Add intent-scope gap analysis and REUSE-WP-0003 workplan Document gaps between INTENT.md and SCOPE.md, refresh SCOPE with current MVP capabilities, and seed the follow-up workplan for documentation alignment, registry CLI tooling, and coverage growth.
2026-06-15 01:09:53 +02:00
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
Registry **tooling** availability is **A4** (CLI plus hosted hub HTTP API).
Registry **authoring** remains Markdown-first; consumption combines entries, the
index, CLI automation, and the production hub.
Add intent-scope gap analysis and REUSE-WP-0003 workplan Document gaps between INTENT.md and SCOPE.md, refresh SCOPE with current MVP capabilities, and seed the follow-up workplan for documentation alignment, registry CLI tooling, and coverage growth.
2026-06-15 01:09:53 +02:00
## What Is Not Possible Yet
Close REUSE-WP-0020: evidence-binder live, 64 capabilities federated evidence-binder published their repaired index at e462775 and correctly held the re-enable request until it was visible on Forgejo. Pre-checked this time before touching production: backing entries return 200, and a local compose of all 61 sources gave 64 capabilities with zero warnings and no duplicate IDs. Public endpoint now serves 61 sources / 64 capabilities, with both capability.evidence.binding and capability.evidence.rect-registry at D3 / A2 / C3 / R3. Open T09 for the gap this exposed: enabling a source does not invalidate the composed index. The endpoint kept serving a stale compose, reporting stale: false throughout, until POST /v1/federated/compose was called by hand. A repo can be correctly registered and silently invisible. SCOPE.md: refresh the federated counts, record the deployed image, and correct the multi-domain claim — member rows have begun carrying their own domain (evidence-binder publishes domain: infotech) even though the manifest is still composed under helix_forge. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-21 10:46:59 +02:00
- **Multi-domain federation** — the federated index is still composed under a
single `helix_forge` manifest domain, though member rows have begun carrying
their own (`evidence-binder` publishes `domain: infotech`)
WP-0015 follow-up: hub-core publish pass, refresh docs Re-run federation sweep — hub-core now passes Gitea raw URL probe (12/60 blockers remain). Update workplan progress, SCOPE.md, IntentScopeGapAnalysis, and operator checklist to reflect T02/T03 closure and current compose stats (20 capabilities, 0 duplicate warnings).
2026-06-16 03:46:01 +02:00
- **Planning analytics breadth** — `report gaps` shipped (REUSE-WP-0015-T03);
no roadmap views or standardization tracker beyond `overlaps` and compose
collision warnings
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
- **Managed platform posture** — hub runs as a container (A5 artifact) without
docs: refresh SCOPE and INTENT↔SCOPE gap analysis post WP-0014 SCOPE.md reflects 60-repo rollout, federation compose metrics, and open publish/dedup blockers. IntentScopeGapAnalysis maps INTENT success criteria to delivery and proposes priorities 25–27.
2026-06-16 02:17:07 +02:00
implemented SLO, multi-replica, or Postgres backing (criteria documented)
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
- **Formal consumer feedback loop** for registry workflows (reliability evidence
is mostly structural: CI/tests, not production telemetry)
Add intent-scope gap analysis and REUSE-WP-0003 workplan Document gaps between INTENT.md and SCOPE.md, refresh SCOPE with current MVP capabilities, and seed the follow-up workplan for documentation alignment, registry CLI tooling, and coverage growth.
2026-06-15 01:09:53 +02:00
Complete REUSE-WP-0003: registry CLI, docs alignment, and coverage Align INTENT.md with delivered layout, add CapabilityRegistryConcept guide, extend schema with promotion_history, ship reuse-surface validate/query/export CLI, register three more helix_forge capabilities, and refresh SCOPE and gap analysis to reflect A3 tooling and D5/A3/C4/R2 self-assessment.
2026-06-15 01:12:09 +02:00
See `tools/README.md` for command reference.
Add intent-scope gap analysis and REUSE-WP-0003 workplan Document gaps between INTENT.md and SCOPE.md, refresh SCOPE with current MVP capabilities, and seed the follow-up workplan for documentation alignment, registry CLI tooling, and coverage growth.
2026-06-15 01:09:53 +02:00
Seeded intent and maturity model
2026-06-15 00:04:09 +02:00
## Current State
Finish REUSE-WP-0017: T05 approved, T07 closeout complete. Mark coverage campaign finished with 62/62 roster coverage and 61 production federated capabilities; update SCOPE.md current state and add completion milestone history.
2026-07-07 16:37:53 +02:00
- **Status:** active registry with CLI, federation, production hub, and
workstation-wide coverage campaign complete (REUSE-WP-0017 finished 2026-07-07).
WP-0015: complete compose acceptance after Gitea visibility fix Refresh federated index (20 capabilities, 0 duplicate warnings). Update workplan, SCOPE, gap analysis, and tests for 59/60 publish pass. Mark T04/T06 done; T01 remains on tegwick-control repo creation. Note: production hub whynot URLs still need REUSE_SURFACE_TOKEN update.
2026-06-16 12:35:49 +02:00
- **Capabilities (reuse-surface):** 2 helix_forge meta-registry entries in
`registry/capabilities/`.
Finish REUSE-WP-0017: T05 approved, T07 closeout complete. Mark coverage campaign finished with 62/62 roster coverage and 61 production federated capabilities; update SCOPE.md current state and add completion milestone history.
2026-07-07 16:37:53 +02:00
- **Workstation roster:** 62 local git repos at `~/<slug>/` tracked in
`registry/federation/local-repo-roster.yaml` — all **established**, **62/62**
hub-registered (inter-hub registration disabled on hub), **62/62**
publish-check pass, **62/62** capability coverage (`has` or explicit `none`).
- **Federation:** `registry/federation/sources.yaml` — **61** enabled sources;
Close REUSE-WP-0020: evidence-binder live, 64 capabilities federated evidence-binder published their repaired index at e462775 and correctly held the re-enable request until it was visible on Forgejo. Pre-checked this time before touching production: backing entries return 200, and a local compose of all 61 sources gave 64 capabilities with zero warnings and no duplicate IDs. Public endpoint now serves 61 sources / 64 capabilities, with both capability.evidence.binding and capability.evidence.rect-registry at D3 / A2 / C3 / R3. Open T09 for the gap this exposed: enabling a source does not invalidate the composed index. The endpoint kept serving a stale compose, reporting stale: false throughout, until POST /v1/federated/compose was called by hand. A repo can be correctly registered and silently invisible. SCOPE.md: refresh the federated counts, record the deployed image, and correct the multi-domain claim — member rows have begun carrying their own domain (evidence-binder publishes domain: infotech) even though the manifest is still composed under helix_forge. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-21 10:46:59 +02:00
`registry/indexes/federated.yaml` — **64** composed capability rows
Finish REUSE-WP-0017: T05 approved, T07 closeout complete. Mark coverage campaign finished with 62/62 roster coverage and 61 production federated capabilities; update SCOPE.md current state and add completion milestone history.
2026-07-07 16:37:53 +02:00
(inter-hub excluded; core-hub included; 0 duplicate-ID warnings at last compose).
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
- **CLI / service:** `reuse_surface/` — validate, query, export, overlaps,
docs: refresh SCOPE and INTENT↔SCOPE gap analysis post WP-0014 SCOPE.md reflects 60-repo rollout, federation compose metrics, and open publish/dedup blockers. IntentScopeGapAnalysis maps INTENT success criteria to delivery and proposes priorities 25–27.
2026-06-16 02:17:07 +02:00
catalog, federation, graph, hub client, establish/update/stats, `serve`
(FastAPI hub).
Finish REUSE-WP-0017: T05 approved, T07 closeout complete. Mark coverage campaign finished with 62/62 roster coverage and 61 production federated capabilities; update SCOPE.md current state and add completion milestone history.
2026-07-07 16:37:53 +02:00
- **Production hub:** `https://reuse.coulomb.social` — **61** enabled repo
Close REUSE-WP-0020: evidence-binder live, 64 capabilities federated evidence-binder published their repaired index at e462775 and correctly held the re-enable request until it was visible on Forgejo. Pre-checked this time before touching production: backing entries return 200, and a local compose of all 61 sources gave 64 capabilities with zero warnings and no duplicate IDs. Public endpoint now serves 61 sources / 64 capabilities, with both capability.evidence.binding and capability.evidence.rect-registry at D3 / A2 / C3 / R3. Open T09 for the gap this exposed: enabling a source does not invalidate the composed index. The endpoint kept serving a stale compose, reporting stale: false throughout, until POST /v1/federated/compose was called by hand. A repo can be correctly registered and silently invisible. SCOPE.md: refresh the federated counts, record the deployed image, and correct the multi-domain claim — member rows have begun carrying their own domain (evidence-binder publishes domain: infotech) even though the manifest is still composed under helix_forge. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-21 10:46:59 +02:00
registrations; `GET /v1/federated` serves **64** capabilities from published
raw URLs (compose refreshed 2026-08-21). Runs image
`forgejo.coulomb.social/coulomb/reuse-surface:main-b035664` (Helm revision 8);
`/health`, `/v1/repos`, `/v1/federated`, and `/v1/reuse-events` all answer.
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
- **Specs:** `specs/FederationHubAPI.md`, `schemas/hub-registration.schema.yaml`.
- **Docs:** `docs/CapabilityRegistryConcept.md`, `docs/RegistryFederation.md`,
`docs/IntentScopeGapAnalysis.md`, deploy guide `docs/deploy/reuse-kubernetes.md`.
REUSE-WP-0019-T03: add Forgejo Actions workflows (part 2 of prior commit) The .forgejo/workflows/ files and doc updates described in 4862ed6 didn't actually get staged there (git add silently skipped them after an earlier pathspec miss on the already-deleted .gitea file) -- committing them now. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-07 21:25:01 +02:00
- **CI:** `.forgejo/workflows/ci.yml` — validate, federation compose, catalog,
graph, pytest, informational `report cohorts`, `stats --roster`, `report gaps`
(migrated from Gitea 2026-07-07, REUSE-WP-0019-T03). Also
`.forgejo/workflows/image.yaml` (container build/push) and
`recompose-fallback.yaml` (scheduled hub recompose, webhook backstop).
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
- **Relation graph:** `docs/graph/capability-graph.mmd`, `docs/graph/index.html`.
- **Searchable catalog:** `docs/catalog/search.html`.
Finish REUSE-WP-0017: T05 approved, T07 closeout complete. Mark coverage campaign finished with 62/62 roster coverage and 61 production federated capabilities; update SCOPE.md current state and add completion milestone history.
2026-07-07 16:37:53 +02:00
- **Workplans:** REUSE-WP-0001 through REUSE-WP-0015 finished (archived);
**REUSE-WP-0017** capability coverage campaign finished (2026-07-07);
REUSE-WP-0019-T06: hub freshness monitoring, docs, close workplan reuse_surface/stats.py: _hub_summary() now reports composed_at, stale, age_days, freshness_threshold_days (REUSE_SURFACE_FRESHNESS_DAYS env, default 7), and a computed stale_warning. New hub_client.hub_federated() backs it. format_stats_markdown surfaces a STALE marker when triggered. .forgejo/workflows/ci.yml: new informational (non-failing) hub freshness check against the live production hub on every push -- prints a ::warning:: annotation when stale, never fails the build. docs/RegistryFederation.md: new section tying together the webhook (T02), scheduled fallback (T03), and freshness visibility (T06) into one explanation. docs/deploy/reuse-kubernetes.md: updated for the T03 Forgejo migration and the now-automated image.yaml build; image promotion checklist updated for the known /health ingress bug (verify via /v1/repos or /v1/federated instead). 14 new pytest cases, 173 total pass. Live-verified against production: reuse-surface stats correctly showed composed_at/age_days for the real federated index. Separately discovered and confirmed (via a live signed webhook test) that reuse-surface-env moving to ExternalSecret/OpenBao custody (railiance-apps commit 706f6c7, found while updating these docs) did not break the T02/T03 webhook -- the synced value still matches what the hub actually uses. REUSE-WP-0019 is now fully complete (T01-T06). SCOPE.md and docs/IntentScopeGapAnalysis.md updated to reflect closure. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-08 00:09:58 +02:00
**REUSE-WP-0018** plan-check consumption loop finished (2026-07-07);
**REUSE-WP-0019** Forgejo automation and reuse telemetry finished
(2026-07-08, all six tasks T01–T06).
docs: refresh SCOPE and INTENT↔SCOPE gap analysis post WP-0014 SCOPE.md reflects 60-repo rollout, federation compose metrics, and open publish/dedup blockers. IntentScopeGapAnalysis maps INTENT success criteria to delivery and proposes priorities 25–27.
2026-06-16 02:17:07 +02:00
- **Assessment history:** `history/` — intent/scope assessments, rollout
milestone, dedup plan, per-repo follow-up.
Implement REUSE-WP-0012 federation scale and intent alignment Add hub sync and report cohorts CLI commands with pytest coverage, document sibling index publish contract and hub hardening path, align INTENT layout, raise external evidence on three registry entries, and close gap priorities 19-23 (priority 18 deferred on sibling index blocks).
2026-06-16 00:42:50 +02:00
- **Self-assessed vector:** `D5 / A4 / C5 / R3` (see `docs/IntentScopeGapAnalysis.md`).
Add intent-scope gap analysis and REUSE-WP-0003 workplan Document gaps between INTENT.md and SCOPE.md, refresh SCOPE with current MVP capabilities, and seed the follow-up workplan for documentation alignment, registry CLI tooling, and coverage growth.
2026-06-15 01:09:53 +02:00
## Repository Layout
```text
reuse-surface/
├── INTENT.md
├── SCOPE.md
├── AGENTS.md
Complete REUSE-WP-0003: registry CLI, docs alignment, and coverage Align INTENT.md with delivered layout, add CapabilityRegistryConcept guide, extend schema with promotion_history, ship reuse-surface validate/query/export CLI, register three more helix_forge capabilities, and refresh SCOPE and gap analysis to reflect A3 tooling and D5/A3/C4/R2 self-assessment.
2026-06-15 01:12:09 +02:00
├── pyproject.toml
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
├── Dockerfile
├── reuse_surface/ # CLI, hub service, federation, graph, catalog
Add intent-scope gap analysis and REUSE-WP-0003 workplan Document gaps between INTENT.md and SCOPE.md, refresh SCOPE with current MVP capabilities, and seed the follow-up workplan for documentation alignment, registry CLI tooling, and coverage growth.
2026-06-15 01:09:53 +02:00
├── specs/
├── schemas/
├── templates/
├── registry/
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
│ ├── capabilities/ # per-entry Markdown
│ ├── indexes/ # capabilities.yaml, federated.yaml
docs: refresh SCOPE and INTENT↔SCOPE gap analysis post WP-0014 SCOPE.md reflects 60-repo rollout, federation compose metrics, and open publish/dedup blockers. IntentScopeGapAnalysis maps INTENT success criteria to delivery and proposes priorities 25–27.
2026-06-16 02:17:07 +02:00
│ └── federation/ # sources.yaml, local-repo-roster.yaml, cache/
Complete REUSE-WP-0003: registry CLI, docs alignment, and coverage Align INTENT.md with delivered layout, add CapabilityRegistryConcept guide, extend schema with promotion_history, ship reuse-surface validate/query/export CLI, register three more helix_forge capabilities, and refresh SCOPE and gap analysis to reflect A3 tooling and D5/A3/C4/R2 self-assessment.
2026-06-15 01:12:09 +02:00
├── docs/
Add intent-scope gap analysis and REUSE-WP-0003 workplan Document gaps between INTENT.md and SCOPE.md, refresh SCOPE with current MVP capabilities, and seed the follow-up workplan for documentation alignment, registry CLI tooling, and coverage growth.
2026-06-15 01:09:53 +02:00
├── tools/
└── workplans/
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
└── archived/
Add intent-scope gap analysis and REUSE-WP-0003 workplan Document gaps between INTENT.md and SCOPE.md, refresh SCOPE with current MVP capabilities, and seed the follow-up workplan for documentation alignment, registry CLI tooling, and coverage growth.
2026-06-15 01:09:53 +02:00
```
Seeded intent and maturity model
2026-06-15 00:04:09 +02:00
## Getting Oriented
- Start with: INTENT.md
Complete REUSE-WP-0003: registry CLI, docs alignment, and coverage Align INTENT.md with delivered layout, add CapabilityRegistryConcept guide, extend schema with promotion_history, ship reuse-surface validate/query/export CLI, register three more helix_forge capabilities, and refresh SCOPE and gap analysis to reflect A3 tooling and D5/A3/C4/R2 self-assessment.
2026-06-15 01:12:09 +02:00
- Registry concept: docs/CapabilityRegistryConcept.md
Add intent-scope gap analysis and REUSE-WP-0003 workplan Document gaps between INTENT.md and SCOPE.md, refresh SCOPE with current MVP capabilities, and seed the follow-up workplan for documentation alignment, registry CLI tooling, and coverage growth.
2026-06-15 01:09:53 +02:00
- Intent vs scope gaps: docs/IntentScopeGapAnalysis.md
Add post-WP-0011 assessment history and REUSE-WP-0012 workplan Archive INTENT↔SCOPE assessment in history/ and map gap priorities 18–23 to follow-up tasks for federation scale and intent alignment.
2026-06-16 00:33:36 +02:00
- Assessment snapshots: history/
Bootstrap and first implementation
2026-06-15 01:04:30 +02:00
- Product requirements: specs/ProductRequirementsDocument.md
- Use cases: specs/UseCaseCatalog.md
- Maturity standard: specs/CapabilityMaturityStandard.md
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
- Hub API: specs/FederationHubAPI.md
Add intent-scope gap analysis and REUSE-WP-0003 workplan Document gaps between INTENT.md and SCOPE.md, refresh SCOPE with current MVP capabilities, and seed the follow-up workplan for documentation alignment, registry CLI tooling, and coverage growth.
2026-06-15 01:09:53 +02:00
- Registry index: registry/indexes/capabilities.yaml
- Registry guidance: registry/README.md
Refresh SCOPE and INTENT gap analysis after WP-0011 SCOPE reflects 20 capabilities, production hub (A4), and current limits. Gap analysis closes historical MVP gaps and proposes priorities 18–23. Self-assessed product vector: D5 / A4 / C4 / R3.
2026-06-16 00:30:53 +02:00
- Federation guide: docs/RegistryFederation.md
- Hub deployment: docs/deploy/reuse-kubernetes.md
Complete REUSE-WP-0004: CI, overlap detection, and catalog generation Add Gitea CI workflow for registry validation, reuse-surface overlaps and catalog commands, generated catalog artifacts, and documentation updates closing gap analysis priorities 9-11.
2026-06-15 01:20:31 +02:00
- Generated catalog: docs/CapabilityCatalog.md
Complete WP-0006 through WP-0009: registry expansion, catalog, graph, tests Register six new capabilities (12 total), add searchable catalog UI and graph explorer, introduce pytest suite with CI fail-on-warnings, and close gap analysis priorities 13 and 16. WP-0010 remains backlog for network federation.
2026-06-15 02:24:20 +02:00
- Searchable catalog: docs/catalog/search.html
Complete REUSE-WP-0005: registry federation and relation graphs Add federation manifest and schema, federation compose and graph CLI commands, relation cycle/reference checks, federated index and Mermaid graph artifacts, RegistryFederation guide, and CI validation updates.
2026-06-15 01:43:02 +02:00
- Relation graph: docs/graph/capability-graph.mmd
Complete WP-0006 through WP-0009: registry expansion, catalog, graph, tests Register six new capabilities (12 total), add searchable catalog UI and graph explorer, introduce pytest suite with CI fail-on-warnings, and close gap analysis priorities 13 and 16. WP-0010 remains backlog for network federation.
2026-06-15 02:24:20 +02:00
- Graph explorer: docs/graph/index.html
Complete REUSE-WP-0003: registry CLI, docs alignment, and coverage Align INTENT.md with delivered layout, add CapabilityRegistryConcept guide, extend schema with promotion_history, ship reuse-surface validate/query/export CLI, register three more helix_forge capabilities, and refresh SCOPE and gap analysis to reflect A3 tooling and D5/A3/C4/R2 self-assessment.
2026-06-15 01:12:09 +02:00
- CLI reference: tools/README.md
Seeded intent and maturity model
2026-06-15 00:04:09 +02:00
- Agent instructions: AGENTS.md
Bootstrap and first implementation
2026-06-15 01:04:30 +02:00
- Workplans: workplans/
Reference in a new issue Copy permalink