Skip to content

feat: TechNeHub Labs portfolio navigation (CR-TNH-README-01 through 07) - #8

Merged
emmanuel-a-otchere merged 3 commits into
mainfrom
feature/portfolio-navigation
Aug 31, 2026
Merged

feat: TechNeHub Labs portfolio navigation (CR-TNH-README-01 through 07)#8
emmanuel-a-otchere merged 3 commits into
mainfrom
feature/portfolio-navigation

Conversation

@emmanuel-a-otchere

Copy link
Copy Markdown
Contributor

Summary

Transforms the TechNeHub Labs organization profile from a repository inventory into a portfolio-oriented navigation layer, implementing the CR-TNH-README-01 through CR-TNH-README-07 programme (source documents: review, plan and CR set delivered 2026-08-31).

Before: profile/README.md carried a 56-row repository table as the primary navigation mechanism.
After: three-level navigation: Organization README (orientation) → Portfolio Index (classification and navigation) → Repository READMEs (implementation).

Deliverables by CR

CR Deliverable Where
01 Navigation architecture Three-level model, portfolio-centric presentation whole change
02 Portfolio taxonomy 8 families, lifecycle + canonical vocabularies, classification rules, 5 recorded anomalies registry/taxonomy.md
03 Portfolio registry 63/63 repositories classified; entity, layer and class alias harvested from live metamodel-pointer.yaml files registry/repositories.yaml
04 Portfolio index Landing page + 8 family pages; catalogs grouped by OpenDEAM layer L1-L5 portfolio/
05 Visual navigation Architecture, portfolio and dependency views; Mermaid with .mmd sources portfolio/diagrams/
06 Organization README Concise 8-section profile; prior README archived verbatim with banner profile/README.md, archive/
07 Automation Registry validation against live org + generation of portfolio pages; nightly CI with drift issue management scripts/, .github/workflows/portfolio-check.yml

Superseded

  • scripts/check_repo_drift.py and .github/workflows/repo-drift-check.yml are removed: the README repository table they checked no longer exists. portfolio-check.yml carries forward the same contract (nightly validation, portfolio-drift tracking issue, auto-close on resolution) against the registry instead of the table.
  • validate_registry.py preserves the degraded-visibility behaviour: without ORG_REPOS_TOKEN, private records are skipped with a warning rather than reported as broken links.

Verification

  • validate_registry.py --check-only with full-visibility token: IN SYNC: 63 registry records == 63 org repos; schema valid; 1 warning (warning is the known DI class-alias collision, recorded as anomaly A1 in registry/taxonomy.md).
  • Degraded mode (public-only listing) simulated: no false errors, 19 private records skipped with warning.
  • generate_portfolio.py --check: all 11 generated regions current.
  • All repository links in generated pages resolve against the live org list; all internal links resolve; referenced GitHub Projects 3-7 confirmed open.

Flagged, not fixed (outside scope)

  • Pinned repositories (web UI, org owner): recommended set to match Featured: dea-architecture-framework, dea-metaframework, dea-concepts-model, dea-metamodel, dea-catalog-business-capabilities, dea-web-viewer. Current pins include archived ea-foundation.
  • Org profile description still reads "Digital Enterprise Architecture: open reference framework..."; update in organization settings if the OpenDEAM positioning is preferred.
  • Catalog metamodel-pointer.yaml files pin an old root-model generation (v0.2.1 era); pointers are auto-generated, regeneration belongs to the root-model release process.
  • Classification anomalies A1-A5 recorded in registry/taxonomy.md for governance decision (not silently resolved).
  • Quick Start section removed from the profile README: dea-cli and dea-code-gen are private, so public install instructions were not accurate. Revisit when tooling is public.

Notes

  • Generated regions in portfolio pages sit between GENERATED:START/END markers; authored narrative is outside them.
  • Registry description fields mirror GitHub descriptions verbatim; generated pages normalize en/em dashes to colons per organization language conventions.
  • Registry location is .github for now; splitting to a dedicated portfolio repository later remains possible without changing the model.

…ling

CR-TNH-README-02 (portfolio taxonomy), CR-TNH-README-03 (portfolio
registry), CR-TNH-README-07 (portfolio automation).

- registry/repositories.yaml: 63 classified records; GitHub stays
  authoritative for existence, registry for classification
- registry/taxonomy.md: family/lifecycle/canonical vocabularies,
  classification rules, 5 recorded anomalies
- scripts/validate_registry.py: schema + live-org cross-check with
  degraded-visibility handling; supersedes scripts/check_repo_drift.py
- scripts/generate_portfolio.py: regenerates GENERATED marker regions
- .github/workflows/portfolio-check.yml: nightly CI; supersedes
  repo-drift-check.yml (README repo table retired by CR-06)
CR-TNH-README-04 (portfolio index), CR-TNH-README-05 (visual
navigation). Family pages with generated tables; catalogs grouped by
OpenDEAM architecture layer; three Mermaid views with .mmd sources.
CR-TNH-README-06. The 56-row repository table is retired as the
primary navigation mechanism; the profile README now provides
orientation, architecture, portfolio families, featured repositories
and entry points. Previous README archived verbatim at
archive/profile-README-v1-2026-08-31.md.
@bolt-new-by-stackblitz

Copy link
Copy Markdown

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@emmanuel-a-otchere
emmanuel-a-otchere merged commit 7400238 into main Aug 31, 2026
2 checks passed
@emmanuel-a-otchere
emmanuel-a-otchere deleted the feature/portfolio-navigation branch August 31, 2026 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant