---
title: Repos — Reference
---

# Repos — Reference

The Repos page shows every repository registered in the Custodian ecosystem,
their **classification** (category, market domain, capabilities, business stake),
SBOM ingestion status, and a domain-grouped coverage map.

---

## What is a managed repo?

A managed repo is a git repository registered with State Hub. Registration is
**classification-driven**:

1. Commit `.repo-classification.yaml` per the Repo Classification Standard.
2. Run `make register-from-classification REPO=<slug>` (or use the MCP tool
   `register_repo_from_classification`).

The file is the source of truth; the hub stores a validated copy on
`managed_repos` (category, domain, capability_tags, business_stake, provenance).

Legacy `custodian register-project` still works for agent onboarding but should
be followed by classification registration.

For the full onboarding journey see **[Repo Integration](/docs/repo-integration)**.

---

## KPI row

| Card | Meaning |
|------|---------|
| **Registered Repos** | Active repos only (status = active) |
| **Market Domains** | Distinct primary domains across registered repos |
| **Categories** | Distinct work categories (experimental, tooling, product, …) |
| **SBOM Ingested** | Repos with at least one SBOM snapshot |
| **SBOM Gaps** | Repos with no ingested SBOM — red border when > 0 |

---

## Portfolio by Category

Groups repos by `category` (experimental, research, project, tooling, product,
business). Each block shows domain, capabilities, business stake, and who
classified the repo (`human` vs `migration`).

---

## Coverage Map

Groups repos by **market domain**. Each domain block shows SBOM, EP, and TD
chips plus per-repo classification columns.

---

## Filters (All Repos Table)

| Filter | Effect |
|--------|--------|
| **Market domain** | Primary domain slug |
| **Category** | Repo work category |
| **Capability** | Repos tagged with a capability |
| **Business stake** | Repos affecting a business responsibility area |
| **DoI tier** | Definition of Integrated tier |
| **Gaps only** | Repos without ingested SBOM |

---

## Consistency (C-24)

The ADR-001 consistency checker warns when a registered repo lacks a valid
`.repo-classification.yaml` on disk. Migration-derived rows (`classified_by:
migration`) get an explanatory note until a human-reviewed file is committed.

---

## Onboarding a new repo

Use the **Add Repo** form or:

```bash
# 1. Author classification file in the repo
# 2. Register / reclassify
make register-from-classification PATH=/path/to/repo
statehub fix-consistency
```