generated from coulomb/repo-seed
Implement REUSE-WP-0012 federation scale and intent alignment
Some checks failed
ci / validate-registry (push) Has been cancelled
Some checks failed
ci / validate-registry (push) Has been cancelled
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).
This commit is contained in:
@@ -143,6 +143,34 @@ Outputs:
|
||||
- `docs/graph/capability-graph.mmd` — Mermaid source
|
||||
- `docs/graph/index.html` — in-browser explorer (also regenerated by `catalog`)
|
||||
|
||||
## External evidence checklist (R1 → R3)
|
||||
|
||||
Use this when promoting **reliability** from **R1 Fragile** or **R2 Tolerable**
|
||||
to **R3 Usable** (normal use with known limitations).
|
||||
|
||||
### Minimum evidence for R3
|
||||
|
||||
- [ ] At least one **repeatable** quality signal (CI gate, smoke test, or
|
||||
documented production check) cited under `evidence.tests` or `evidence.documentation`
|
||||
- [ ] `known_reliability_risks` lists bounded, current limitations (not empty
|
||||
unless risks are genuinely absent)
|
||||
- [ ] At least one `evidence.consumer_feedback` string or resolved-risk note when
|
||||
real consumers exist; otherwise document why feedback is not yet available
|
||||
- [ ] Optional `external_evidence.reliability.evidence.satisfied_signals` for CI
|
||||
or smoke-test citations
|
||||
- [ ] `confidence` is `medium` or `high` when citing CI/production evidence
|
||||
- [ ] `promotion_history` records the R dimension change with rationale
|
||||
|
||||
### Signals that support R3 for registry tooling
|
||||
|
||||
- `reuse-surface validate` in CI with `--fail-on-warnings`
|
||||
- `pytest` coverage for the capability's consumption path
|
||||
- Production hub smoke (`GET /health`, `GET /v1/federated`) for API-backed flows
|
||||
- Operator deploy verification documented in `docs/deploy/reuse-kubernetes.md`
|
||||
|
||||
R4+ requires broader consumer evidence (incidents, adoption, SLO) per
|
||||
`specs/CapabilityMaturityStandard.md`.
|
||||
|
||||
## Promote a capability
|
||||
|
||||
1. Attach evidence appropriate to the target level in
|
||||
|
||||
@@ -47,14 +47,19 @@ external_evidence:
|
||||
- hosting registered capabilities
|
||||
- enforcing implementation architecture
|
||||
reliability:
|
||||
level: R2
|
||||
name: Tolerable
|
||||
level: R3
|
||||
name: Usable
|
||||
confidence: medium
|
||||
basis: consumer_quality_signals
|
||||
known_reliability_risks:
|
||||
- index drift still possible if authors skip validate
|
||||
- CLI requires local venv install
|
||||
- schema ID pattern required a fix during WP-0003 dogfooding
|
||||
- sibling repos cannot register until indexes publish raw URLs
|
||||
evidence:
|
||||
satisfied_signals:
|
||||
- CI validate with fail-on-warnings on every push
|
||||
- hub register/list/federated smoke on production reuse.coulomb.social
|
||||
- pytest coverage for hub API and federation compose paths
|
||||
|
||||
discovery:
|
||||
intent: >
|
||||
@@ -112,7 +117,13 @@ evidence:
|
||||
- docs/deploy/reuse-kubernetes.md
|
||||
tests:
|
||||
- tests/test_hub.py
|
||||
consumer_feedback: []
|
||||
- tests/test_hub_sync.py
|
||||
- .gitea/workflows/ci.yml
|
||||
consumer_feedback:
|
||||
- >
|
||||
reuse-surface dogfood (REUSE-WP-0011): production hub registration and
|
||||
/v1/federated compose succeeded on Railiance01 without write-path
|
||||
regressions after WP-0011 deploy.
|
||||
bug_reports: []
|
||||
incidents: []
|
||||
|
||||
@@ -154,6 +165,14 @@ promotion_history:
|
||||
Hosted federation hub live at reuse.coulomb.social; hub register/update
|
||||
via HTTP API and reuse-surface hub CLI; production deploy on Railiance01.
|
||||
author: reuse-surface
|
||||
- date: "2026-06-16"
|
||||
dimension: reliability
|
||||
from: R2
|
||||
to: R3
|
||||
rationale: >
|
||||
CI gates, pytest hub/federation coverage, and production hub smoke support
|
||||
normal registration workflows with documented limitations.
|
||||
author: reuse-surface
|
||||
---
|
||||
|
||||
# Capability Registration
|
||||
|
||||
@@ -33,12 +33,17 @@ external_evidence:
|
||||
out_of_scope_expectations:
|
||||
- runtime validation of registered capability implementations
|
||||
reliability:
|
||||
level: R2
|
||||
name: Tolerable
|
||||
level: R3
|
||||
name: Usable
|
||||
confidence: medium
|
||||
basis: consumer_quality_signals
|
||||
known_reliability_risks:
|
||||
- requires local venv install
|
||||
- relation warnings require explicit --relations flag
|
||||
evidence:
|
||||
satisfied_signals:
|
||||
- validate --relations --fail-on-warnings in CI
|
||||
- tests/test_registry.py schema and drift coverage
|
||||
|
||||
discovery:
|
||||
intent: Keep registry data structurally sound so agents and humans can trust discovery metadata.
|
||||
@@ -72,7 +77,13 @@ relations:
|
||||
evidence:
|
||||
documentation:
|
||||
- tools/README.md
|
||||
tests: []
|
||||
- .gitea/workflows/ci.yml
|
||||
tests:
|
||||
- tests/test_registry.py
|
||||
consumer_feedback:
|
||||
- >
|
||||
reuse-surface CI: registry changes fail when schema validation or relation
|
||||
checks warn with --fail-on-warnings, giving agents a dependable pre-merge gate.
|
||||
|
||||
consumer_guidance:
|
||||
recommended_for:
|
||||
@@ -81,6 +92,14 @@ consumer_guidance:
|
||||
- certifying business correctness of capability claims
|
||||
known_limitations:
|
||||
- warnings do not fail CI unless --fail-on-warnings is set
|
||||
|
||||
promotion_history:
|
||||
- date: "2026-06-16"
|
||||
dimension: reliability
|
||||
from: R2
|
||||
to: R3
|
||||
rationale: CI fail-on-warnings and pytest registry coverage support dependable validation.
|
||||
author: reuse-surface
|
||||
---
|
||||
|
||||
# Registry Entry Validation
|
||||
|
||||
@@ -32,11 +32,16 @@ external_evidence:
|
||||
out_of_scope_expectations:
|
||||
- replacing git commit history
|
||||
reliability:
|
||||
level: R2
|
||||
confidence: low
|
||||
level: R3
|
||||
name: Usable
|
||||
confidence: medium
|
||||
basis: consumer_quality_signals
|
||||
known_reliability_risks:
|
||||
- depends on hub availability
|
||||
- depends on hub availability and tunnel health for remote agents
|
||||
evidence:
|
||||
satisfied_signals:
|
||||
- reuse-surface AGENTS.md session-close protocol cites POST /progress/
|
||||
- cross-repo agents log progress with workstream_id linkage
|
||||
|
||||
discovery:
|
||||
intent: Provide auditable progress memory for cross-repo agent and operator work.
|
||||
@@ -63,6 +68,14 @@ relations:
|
||||
related_to:
|
||||
- capability.statehub.workstream-coordinate
|
||||
|
||||
evidence:
|
||||
documentation:
|
||||
- AGENTS.md
|
||||
consumer_feedback:
|
||||
- >
|
||||
reuse-surface agents (REUSE-WP-0012): session-close progress posts to State
|
||||
Hub succeeded for workstream fb0b6067 during federation workplan work.
|
||||
|
||||
consumer_guidance:
|
||||
recommended_for:
|
||||
- closing agent sessions with hub progress notes
|
||||
|
||||
@@ -94,7 +94,7 @@ capabilities:
|
||||
- id: capability.registry.register
|
||||
name: Capability Registration
|
||||
summary: Register a new capability so it becomes visible for planning and implementation reuse.
|
||||
vector: D3 / A4 / C2 / R2
|
||||
vector: D3 / A4 / C2 / R3
|
||||
domain: helix_forge
|
||||
status: draft
|
||||
owner: reuse-surface
|
||||
@@ -105,7 +105,7 @@ capabilities:
|
||||
- id: capability.registry.validate
|
||||
name: Registry Entry Validation
|
||||
summary: Validate capability registry entries against schema, index consistency, and relation integrity.
|
||||
vector: D4 / A3 / C3 / R2
|
||||
vector: D4 / A3 / C3 / R3
|
||||
domain: helix_forge
|
||||
status: draft
|
||||
owner: reuse-surface
|
||||
@@ -116,7 +116,7 @@ capabilities:
|
||||
- id: capability.statehub.progress-log
|
||||
name: Work Progress Logging
|
||||
summary: Record progress events, decisions, and session notes against workstreams and tasks in State Hub.
|
||||
vector: D4 / A4 / C3 / R2
|
||||
vector: D4 / A4 / C3 / R3
|
||||
domain: helix_forge
|
||||
status: draft
|
||||
owner: state-hub
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
# Composed federated capability index. Regenerate with:
|
||||
# reuse-surface federation compose
|
||||
version: 1
|
||||
updated: '2026-06-15'
|
||||
updated: '2026-06-16'
|
||||
domain: helix_forge
|
||||
collision_policy: warn
|
||||
sources:
|
||||
@@ -150,7 +150,7 @@ capabilities:
|
||||
name: Capability Registration
|
||||
summary: Register a new capability so it becomes visible for planning and implementation
|
||||
reuse.
|
||||
vector: D3 / A4 / C2 / R2
|
||||
vector: D3 / A4 / C2 / R3
|
||||
domain: helix_forge
|
||||
status: draft
|
||||
owner: reuse-surface
|
||||
@@ -170,7 +170,7 @@ capabilities:
|
||||
name: Registry Entry Validation
|
||||
summary: Validate capability registry entries against schema, index consistency,
|
||||
and relation integrity.
|
||||
vector: D4 / A3 / C3 / R2
|
||||
vector: D4 / A3 / C3 / R3
|
||||
domain: helix_forge
|
||||
status: draft
|
||||
owner: reuse-surface
|
||||
@@ -187,7 +187,7 @@ capabilities:
|
||||
name: Work Progress Logging
|
||||
summary: Record progress events, decisions, and session notes against workstreams
|
||||
and tasks in State Hub.
|
||||
vector: D4 / A4 / C3 / R2
|
||||
vector: D4 / A4 / C3 / R3
|
||||
domain: helix_forge
|
||||
status: draft
|
||||
owner: state-hub
|
||||
|
||||
Reference in New Issue
Block a user