Portfolio Portal
Health

Work Queue

Every item is a concrete gap the graph can prove — missing owners, unmapped repositories, capabilities without a consumer, and so on. These are facts, not recommendations: fixing the source markdown clears the item on the next build.

0 high
1 medium
18 low
19 total

Medium priority1

Low priority18

  • technology-single-useTechnology is referenced by only one repositoryCloudflare Pages
  • technology-single-useTechnology is referenced by only one repositoryCloudflare Worker
  • technology-single-useTechnology is referenced by only one repositoryDocker
  • technology-single-useTechnology is referenced by only one repositoryJS
  • technology-single-useTechnology is referenced by only one repositoryMarkdown
  • technology-single-useTechnology is referenced by only one repositoryMarkdown (packs)
  • technology-single-useTechnology is referenced by only one repositoryNext.js 16
  • technology-single-useTechnology is referenced by only one repositoryNode ESM
  • technology-single-useTechnology is referenced by only one repositoryPHP (WP)
  • technology-single-useTechnology is referenced by only one repositoryPlaywright
  • technology-single-useTechnology is referenced by only one repositoryPython
  • technology-single-useTechnology is referenced by only one repositoryR2
  • technology-single-useTechnology is referenced by only one repositorySKILL.md
  • technology-single-useTechnology is referenced by only one repositorySQL (Supabase)
  • technology-single-useTechnology is referenced by only one repositorySupabase
  • technology-single-useTechnology is referenced by only one repositoryTanStack Start
  • technology-single-useTechnology is referenced by only one repositoryTypeScript
  • technology-single-useTechnology is referenced by only one repositoryYAML
How this is calculated. The engine walks every repository, capability, technology and ADR and emits a task wherever a deterministic check fails (e.g. a repository with no owner, a capability with no consumer, a technology used by only one repository, an ADR with no relationships). Severity is fixed per task type. No task is a generated recommendation — each is a verifiable missing fact. Order: severity, then type, then entity.