Capability Registry
The capability-architecture view of the ecosystem: the reusable business and technical capabilities that exist, who owns them, who consumes them, and how they work together — documented independently from repositories. Where the Repo Registry answers “which repos exist”, this answers “which capabilities exist and how they are reused.”
This registry is a primary navigation entry point. Every capability has a page following
templates/capability.template.md. Maturity is evidence-based and
honestly labelled (✅ operational · 🔶 partial/under-development · ⏳ planned · 🧭 vision).
Registry
| Capability | Purpose (short) | Owning repo(s) | Consumers | Maturity | Page |
|---|---|---|---|---|---|
| Reusable AI Skills | Standardized, invocable AI competence as infrastructure | shared-skills |
all layers | ✅ operational | page |
| Knowledge Intelligence | Capture → structure → retrieve founder intelligence | personalops (FIP) |
FIP dashboard, agents, ventures | 🔶 early-development | page |
| Intelligence Productization | Publish versioned, immutable intelligence packs | intelproducts (+ FIP builders) |
leadplatform, outreachagent |
✅ operational (contract) | page |
| Reproducible Evaluation | Immutable, provenanced experiment & benchmark harness | website-intelligence-lab |
external engines | 🔶 early-development | page |
| Website Assessment | Assess a website → findings → scored gap analysis → recommendations | inexisstudios, intelproducts (pack), website-intelligence-lab |
outreachagent, leadplatform, Inexis Digital |
🔶 mixed | page |
| Commercial Opportunity & Outreach | Turn assessment findings into COPs + outreach messaging | outreachagent (+ intelproducts skills) |
Inexis Digital sales | 🔶 operational (per Phase-B evidence) | page |
| Architecture & Docs Governance | Document the system of systems; govern architecture | portfolio-portal (+ shared-skills doc skills) |
whole ecosystem | ✅ operational | page |
Column contract
| Column | Meaning | Allowed values |
|---|---|---|
| Capability | Human name | — |
| Owning repo(s) | Provider(s) | must match portal/repos/* or a registered repo |
| Consumers | Consuming repos/ventures | — |
| Maturity | Assessment | concept / early-development / active-development / operational / production (+ honesty marker) |
| Page | Capability page | cap-<slug>.md |
How capabilities relate
graph TD
SKILLS[[Reusable AI Skills]] -.underpins.-> KI[[Knowledge Intelligence]]
SKILLS -.underpins.-> IPZ[[Intelligence Productization]]
SKILLS -.underpins.-> EVAL[[Reproducible Evaluation]]
SKILLS -.underpins.-> WA[[Website Assessment]]
SKILLS -.underpins.-> GOV[[Architecture & Docs Governance]]
KI --> IPZ
IPZ -->|packs feed| WA
EVAL -->|evaluates engines for| WA
WA -->|findings feed| CO[[Commercial Opportunity & Outreach]]
IPZ -->|messaging packs| CO
See also
- Capability Reuse Map — providers, consumers, shared assets, duplication risks.
- Repo Registry · Portfolio Overview · Architecture Principles
Adding a capability
Copy templates/capability.template.md → cap-<slug>.md, add a
registry row, and link it from the relevant repo digests and the Reuse Map.