---
id: RREG-WP-0001
type: workplan
title: "Repository Ability Registry — MVP Implementation"
domain: capabilities
repo: repo-registry
status: done
owner: codex
topic_slug: foerster-capabilities
created: "2026-04-26"
updated: "2026-04-26"
state_hub_workstream_id: "acee5529-43c0-4519-94bc-e59e61719af1"
---

# RREG-WP-0001 — MVP Implementation

## Goal

Prove the core registry loop: Register → Analyze → Review → Approve → Search/Inspect.

Core design constraint: deterministic scanners establish observed facts; LLM-assisted
extractors propose interpreted claims; humans or trusted agents approve registry truth.

## Scaffold and Foundation

```task
id: RREG-WP-0001-T01
status: done
priority: high
state_hub_task_id: "d26e70c9-e3a9-48f9-951c-c6210208aef4"
```

App skeleton, database migration setup, configuration system, health endpoint, basic
test harness, local development instructions. Acceptance: app starts, tests run,
migrations apply cleanly.

## Manual Registry

```task
id: RREG-WP-0001-T02
status: done
priority: high
state_hub_task_id: "e9c1cb9b-be21-4862-9443-a3e6c390882e"
```

Repository CRUD, manual ability/capability/feature/evidence CRUD, ability-map endpoint,
basic repository profile UI. Acceptance: user can create a profile by hand; UI and API
both display `Ability → Capability → Feature → Evidence`.

## Git Ingestion and Deterministic Scanner

```task
id: RREG-WP-0001-T03
status: done
priority: high
state_hub_task_id: "4a9fd9f0-d968-4778-93d4-609090c13c62"
```

Git URL validation, clone/fetch, snapshot with branch+commit hash, file tree scan,
README/docs/examples/tests/manifest detection, language/framework detection, analysis
run status tracking. Acceptance: public repo can be registered and analyzed; failures
visible without corrupting prior data.

## Reviewable Candidate Graph

```task
id: RREG-WP-0001-T04
status: done
priority: high
state_hub_task_id: "9aa84fb5-998b-480e-adf8-3c1b0faa395a"
```

Content extraction, source references, candidate ability/capability/feature/evidence
generation, confidence scoring, candidate graph endpoint and UI. Acceptance: candidates
have source references and confidence; output is explainable for curator review.

## Review and Approval Workflow

```task
id: RREG-WP-0001-T05
status: done
priority: high
state_hub_task_id: "0b5cff5d-4bc8-48ca-aa41-2f1d0c774bed"
```

Approve/reject/edit/merge/relink candidates, publish approved profile, persist review
decisions. Acceptance: curator can correct and approve an analysis result; only approved
entries appear in canonical views.

## Search and Inspection

```task
id: RREG-WP-0001-T06
status: done
priority: high
state_hub_task_id: "13e506eb-017a-4710-b20b-ae10ac8df9d4"
```

Text search over repos/abilities/capabilities/descriptions, search filters, search UI,
repository profile drill-down, code/evidence links. Acceptance: user can search by need;
results show repo, ability/capability, confidence, evidence level.

## API Completeness for Agents

```task
id: RREG-WP-0001-T07
status: done
priority: high
state_hub_task_id: "cb94bb9c-756f-446a-8a59-54aa5a51eff0"
```

Full MVP REST API: GET/POST /repos, GET /repos/{id}, POST/GET /repos/{id}/analysis-runs,
GET /repos/{id}/ability-map, GET /abilities, GET /capabilities, GET /search, OpenAPI
examples. Acceptance: API covers registration, analysis, search, inspection; stable
enough for agent/tooling integration.