Portfolio Portal
Capability maturity: operational living owner: Azwaan reviewed: 2026-07-05

Architecture & Docs Governance — Capability

Purpose

Document the system of systems and govern its architecture: repository digests, capability architecture, layered model, ADRs, principles, and diagrams — the portal you are reading. It turns a scattered set of repos into an architectural source of truth.

At a glance

Field Value
Slug cap-architecture-governance
Maturity ✅ operational
Owning repo(s) portfolio-portal + shared-skills (doc skills)
Layer(s) Docs / Governance
Last reviewed 2026-07-05

Business value

A single onboarding guide, AI-context source, and architectural reference — and, later, a public showcase of the ecosystem’s scale and sophistication.

Technical responsibilities

  • Maintain digests, capability registry, layered architecture, ADRs, principles, current-state, and llms.txt.
  • Enforce evidence-first, honestly-labelled documentation (Principle 8).
  • Not responsible for building the systems it documents.

Owning repository or repositories

Repo Role
portfolio-portal The portal itself
shared-skills documentation-writer, senior-architect, site-architecture, create-llms, knowledge-ops

Consuming repositories / consumers

  • Every repo & venture is a subject; humans and AI agents (Claude, ChatGPT) are the consumers of the docs.

Consuming ventures

  • All — as onboarding and architectural reference.

Inputs

  • Source repos’ docs (CLAUDE.md, READMEs, ADRs), evidence hunts, and architectural decisions.

Outputs

  • Repo/venture/capability digests, architecture diagrams, ADRs, principles, llms.txt, the future showcase.

Dependencies

Capability relationships

graph LR
    PORTAL[portfolio-portal] -->|provides| CAP[[Architecture & Docs Governance]]
    SS[Reusable AI Skills] -.underpins.-> CAP
    CAP -.documents.-> ALL[All capabilities & repos]
    CAP -.will be automated by.-> ORCH[[portfolio-portal-orchestrator]]

Current maturity

✅ Operational. The portal actively documents 4 systems across 4 layers with capability architecture, diagrams, principles, and ADRs. Automation (portfolio-portal-orchestrator) is spec-only.

Planned evolution

Implement the orchestrator (Phase D) to auto-generate digests/diagrams; build the public showcase (Phase C).