# INTENT ↔ SCOPE State Assessment — reuse-surface

**Date:** 2026-06-16  
**Author:** codex  
**Trigger:** Post–REUSE-WP-0014 review; `SCOPE.md` and
`docs/IntentScopeGapAnalysis.md` refreshed (commit `834abb8`).  
**Follow-up workplan:** `workplans/REUSE-WP-0015-federation-polish-and-planning-analytics.md`

---

## 1. Executive summary

`reuse-surface` has completed REUSE-WP-0001 through **REUSE-WP-0014**. The
registry product delivers **20 helix_forge entries** in reuse-surface, **A3+ CLI
tooling**, a **production federation hub at A4** (`https://reuse.coulomb.social`)
with **60 repo registrations**, federation compose (**37** federated capability
rows), workstation registry rollout (**60/60** local repos established), and
pytest + CI gates.

INTENT and SCOPE are **aligned on the core model** (registry-first, four maturity
dimensions, human/agent consumers). Remaining work shifts from “establish
registries everywhere” to **fetchable federation**, **index deduplication**,
**planning analytics**, and **operational polish**.

**Self-assessed product vector:** `D5 / A4 / C5 / R3`

---

## 2. Delivery snapshot

| Area | State (2026-06-16) |
|---|---|
| Capability entries (reuse-surface) | 20 in `registry/capabilities/` |
| Workstation roster | 60 repos; `registry/federation/local-repo-roster.yaml` |
| Established / hub registered | 60 / 60 |
| Publish pass (Gitea raw 200) | 47 / 60 |
| Federation sources | 60 URL sources in `sources.yaml` (hub sync) |
| Federated compose | 37 capabilities; 16 duplicate-ID warnings; 13 fetch warnings |
| Hub | `reuse.coulomb.social`; 60 registrations |
| CLI | validate, query, export, overlaps, catalog, federation, graph, hub, establish, update, stats, report |
| Tests | pytest (registry, federation, hub, hub_sync, stats, reports) |
| Workplans | WP-0001 … WP-0014 finished; WP-0014 archived |

---

## 3. INTENT alignment

### Aligned

- Registry-first boundary
- Four maturity dimensions; internal vs external evidence
- Human and agent consumption surfaces
- Technical foundation at MVP+ (CLI A3, hub A4, container A5 artifact)
- Workstation-wide registry bootstrap (establish tooling + roster)

### Partial

| INTENT expectation | Gap |
|---|---|
| Cross-repo reuse at network scale | 13 indexes not HTTP-fetchable; 16 duplicate IDs |
| Eight success criteria fully met | Analytics, D7 pipeline, standardization partial |
| Consumer reliability evidence | Catalog mostly R0–R2; no formal telemetry |
| Generalized primitives (D7) | helix_forge only; no org-wide D7 view |

---

## 4. Success criteria scorecard

| Criterion | Verdict |
|---|---|
| Find reusable capabilities before rebuilding | **Yes** (13 sources not fetchable) |
| Compare maturity consistently | **Yes** |
| Distinguish conceptual readiness from delivery | **Yes** |
| Distinguish internal vs external evidence | **Yes** |
| Plan prototype/MVP/enhancement/platform work | **Partial** |
| Identify gaps, duplicates, overlaps, standardization | **Partial** |
| Track progress to generalized capabilities (D7) | **Partial** |
| Make reuse normal in architecture work | **Partial** |

**Score:** 4 yes, 4 partial.

---

## 5. Open gaps → workplan mapping

| Priority | Gap | Workplan task |
|---|---|---|
| 25 | Gitea publish visibility (13 repos) | REUSE-WP-0015-T01 |
| 26 | Federated ID deduplication | REUSE-WP-0015-T02 |
| 27 | Planning analytics / standardization | REUSE-WP-0015-T03 |
| — | Federation compose clean acceptance | REUSE-WP-0015-T04 |
| — | Roster observability in CI (informational) | REUSE-WP-0015-T05 |
| — | Living docs refresh on completion | REUSE-WP-0015-T06 |

---

## 6. Proposed vector after WP-0015

| Dimension | Current | Target | Rationale |
|---|---|---|---|
| Discovery | D5 | D5 | Unchanged |
| Availability | A4 | A4 | Unchanged |
| Completeness | C5 | C5–C6 | Fetchable federation + deduped namespace |
| Reliability | R3 | R3–R4 | CI roster gate; hub hardening deferred |

---

## 7. References

- `SCOPE.md`
- `docs/IntentScopeGapAnalysis.md`
- `history/2026-06-16-local-repo-registry-rollout-complete.md`
- `history/2026-06-16-wp0014-remaining-work-by-repo.md`
- `history/2026-06-16-federation-deduplication-plan.md`
- `registry/federation/local-repo-roster.yaml`