Concept Ownership Registry
For every major architectural concept: its owner, the owning repository, the capability it belongs to, its lifecycle, its consumers, and its source of truth. This surfaces concepts with ambiguous ownership — the biggest operating risk as the ecosystem grows. Evidence-first; concepts the portal cannot yet substantiate are marked ⚠ uncertain, not invented.
Registry
| Concept | Owner | Repository | Capability | Lifecycle | Consumers | Source of truth |
|---|---|---|---|---|---|---|
| Skills | shared-skills library | shared-skills |
Reusable AI Skills | operational | all repos, agents | SKILL.md files |
| Knowledge Assets | FIP | personalops |
Knowledge Intelligence | early-dev | retrieval, builders | knowledge_assets (Supabase) |
| Findings | assessment engine (rules from pack) | inexisstudios |
Website Assessment | active-dev | recommendations, COP | engine assessment_findings (derived from pack rules) |
| Recommendations | ⚠ ambiguous — engine rules + pack library + COP action | inexisstudios + intelproducts + outreachagent |
Website Assessment / Commercial Opportunity | mixed | outreach, proposals | should be the pack (recommendation-library REC-001…015) — currently three layers |
| Packs | intelproducts | intelproducts |
Intelligence Productization | operational | engine, apps | immutable versioned pack dirs |
| Intelligence Products | intelproducts | intelproducts |
Intelligence Productization | operational | ventures | intelproducts repo (= Packs) |
| Opportunity Scores | ⚠ ambiguous — pack score vs leadplatform’s own | intelproducts + leadplatform |
Website Assessment / (leadplatform) | mixed | outreach, CRM | two competing — recommend pack as single source (R2) |
| Website Assessments | ⚠ diffuse — 4 co-owners | inexisstudios (engine) + intelproducts (pack) + personalops (authoring) + website-intelligence-lab (harness) |
Website Assessment | mixed | outreach, leadplatform | engine result contract (/api/assessments/:slug); scoring truth = pack |
| Journey Intelligence | intelproducts (cinnamon-stories) | intelproducts |
(travel/Inbound Lanka) | operational (pack) | Inbound Lanka | sri-lanka-journey-architecture-pack-v1 |
| Signals | intelproducts (travel signal catalogue) / FIP authoring | intelproducts + personalops |
Website Assessment (travel) | operational (pack) | rule packs, engine | travel signal catalogue (WP-48B); 159 signals |
| Observations | ⚠ maps to WIL observed assets | website-intelligence-lab |
Reproducible Evaluation | early-dev (capture_pending) |
cases, runs | corpus/businesses/<id>/observed/ manifests |
| Domain Briefs | ⚠ not directly evidenced | uncertain (possibly relates to industry packs / opportunity-briefs route) | uncertain | uncertain | uncertain | ⚠ term not substantiated in processed docs |
| Review Packages | ⚠ not directly evidenced as a named concept | uncertain (FIP review queue / lab review gate) | uncertain | uncertain | uncertain | ⚠ term not substantiated in processed docs |
| Capabilities | Capability Registry | portfolio-portal |
(all) | mixed | ventures | Capability Registry |
| Runs | website-intelligence-lab | website-intelligence-lab |
Reproducible Evaluation | early-dev | evaluation | immutable runs/<business>/<case>/<run>/ |
| Cases / Businesses / Reference assets / Benchmarks | website-intelligence-lab | website-intelligence-lab |
Reproducible Evaluation | early-dev | runs, evaluation | WIL corpus/ + contracts |
| Commercial Opportunity Profile (COP) | outreachagent | outreachagent |
Commercial Opportunity | operational (mock) | CRM, email, proposal | COP schema v2 (frozen) |
| Maturity levels | ⚠ two definitions — pack (1–5 site maturity) vs FIP (working/ready/proven/archived asset maturity) | intelproducts + personalops |
Website Assessment / Knowledge Intelligence | operational | scoring / asset promotion | two distinct, both valid in context — standardise naming |
| Digests / ADRs / Principles | portfolio-portal | portfolio-portal |
Architecture & Docs Governance | operational | humans, agents | this portal |
Concepts with ambiguous or diffuse ownership (priority)
| Concept | Problem | Recommendation |
|---|---|---|
| Recommendations | Logic in 3 layers (engine / pack / COP) | Make the pack the single source; engine & COP pin to it |
| Opportunity Scores | Two competing scores (pack vs leadplatform) | Single source (pack/COP); retire leadplatform’s parallel score |
| Website Assessments | 4 co-owners, no single accountable owner | Assign capability ownership: pack = scoring truth, engine = execution (see ADR 0005) |
| Maturity levels | Same word, two meanings (site maturity vs asset maturity) | Standardise names: “site maturity level” vs “asset maturity state” (see Glossary) |
| Domain Briefs / Review Packages | Named in the brief but not evidenced in processed docs | Do not model until evidenced; confirm whether these exist or are aliases |
Evidence discipline: “Domain Briefs” and “Review Packages” were requested for review but are not substantiated in the documentation processed so far. They are recorded here as unresolved rather than given invented owners. Confirm against
PersonalOps(opportunity-briefs / review queue) before modelling.