From 38a0f6796a5148e33c7b6708f7203c732cd16b55 Mon Sep 17 00:00:00 2001 From: Jacobus Geluk Date: Tue, 2 Dec 2025 00:28:20 +0000 Subject: [PATCH] feat(docs): enhance composable business page with comprehensive content - Add comprehensive content covering composable business concept - Add comparison table between Composable Business and Reuse Enablement - Use MkDocs Material tip admonition for key insights section - Add ChatGPT-style table styling (no vertical borders, subtle horizontal lines) - Include package statistics (npm: 3.5M+, PyPI: 600K+ packages) - Add links to npmjs.org and pypi.org - Format all content with 70-character line wrapping - Enhance blockquote styling in CSS (for future use) --- docs/objective/composable-business.md | 132 +++++++++++++++++++++++--- docs/stylesheets/extra.css | 109 +++++++++++++++++++++ 2 files changed, 229 insertions(+), 12 deletions(-) diff --git a/docs/objective/composable-business.md b/docs/objective/composable-business.md index 6a615e44..62b102dd 100644 --- a/docs/objective/composable-business.md +++ b/docs/objective/composable-business.md @@ -8,21 +8,129 @@ hide: # B: Composable Business -_The Future of Business Is Composable_ +_Making the enterprise adaptive through modular knowledge and +reusable capabilities_ +## Objective -!!! info +A composable business is one that can adapt and reconfigure itself +continuously — not through massive reorganisations or costly rewrites, +but through modular, reusable, and semantically connected components. - Work in progress. Points to make: +Composable Business is the organisational expression of the Enterprise +Knowledge Graph (EKG) and the Use Case Tree (UCT) method. It represents +the ability to assemble business capabilities dynamically from trusted, +reusable building blocks: use cases, data products, stories, workflows, +and ontologies — all governed within the EKG. - - Explain that the [Use Case Tree (UCT)](../concept/use-case-tree.md) is the ultimate way to implement - what Gartner now calls "Composable Business": - - https://www.gartner.com/smarterwithgartner/gartner-keynote-the-future-of-business-is-composable - - Same for "Packaged Business Capabilities (PBCs)" (also called Packaged Business Components): - - https://www.elasticpath.com/blog/what-are-packaged-business-capablities - - https://www.elasticpath.com/blog/what-is-the-difference-between-PBCs-and-microservices - - https://blog.dreamfactory.com/enterprise-it-building-blocks-the-packaged-business-capability/ - - Explain what's missing with the various proposed approaches in the articles above. - Why Semantic Technology and in particular EKG & the UCT is key to _really_ make this fly. +## Why It Matters +Most organisations struggle to change because their systems, data, and +processes are tightly coupled and fragmented. Innovation requires +coordination across dozens of silos, each with its own models and +assumptions. + +Composable Business replaces this fragility with semantic modularity — +every business capability becomes a governed component that can be +reused, combined, or replaced without breaking the whole. + +The result: + +- Faster adaptation to market or regulatory change +- Continuous innovation without re-engineering core systems +- Resilience through modular design +- Clarity and governance through shared semantics + +## The Role of the Use Case Tree (UCT) + +The Use Case Tree (UCT) is the organising structure of composability. +It defines how business capabilities are decomposed into modular use +cases, each of which can be modelled, implemented, and run +independently, yet still fit coherently into the enterprise +architecture. + +Every node in the UCT represents a reusable component — a semantic +package containing: + +- Defined outcomes and personas +- Stories (tool functions or APIs) +- Data products and ontologies +- Workflows and policies + +This makes the UCT the semantic package manager of the EKG — similar to +how npmjs.org or pypi.org manage software packages — but at enterprise +scale, spanning business, data, and knowledge assets. + +## Composable Business vs. Reuse Enablement + +### Two sides of the same semantic coin + +While Composable Business and Reuse Enablement both aim to make the +enterprise modular, they operate at different levels of abstraction. +The table below outlines how they relate and reinforce one another +within the EKGF Method. + +| Aspect | Composable Business | Reuse Enablement | +|--------|---------------------|------------------| +| Focus / Orientation | _How business capabilities are composed, orchestrated, and evolved_ | _How knowledge assets and components are packaged and shared_ | +| Primary Question | "How do we assemble business capabilities from reusable parts to adapt to change?" | "How do we design those reusable parts so they can be assembled safely and meaningfully?" | +| Scope | Business and operational level — orchestrating Use Cases, Personas, and Stories into composable outcomes. | Technical and semantic level — creating and governing reusable artifacts: ontologies, datasets, shapes, workflows, data products, and Stories. | +| Key Mechanism | **Use Case Tree (UCT)** as the orchestration layer: composing and aligning modular business capabilities. | **Use Case Tree (UCT)** as the packaging layer: publishing reusable components and metadata to the Enterprise Knowledge Graph (EKG) for discovery and re-use. | +| Relationship to the EKG | The EKG provides the shared semantics and service interfaces that make cross-use-case orchestration possible. | The EKG provides the shared identifiers, ontologies, and provenance that make reuse safe and traceable. | +| Value Proposition | Agility and adaptability: the ability to reconfigure the enterprise dynamically in response to change. | Efficiency and consistency: the ability to reduce duplication and accelerate delivery through reusable, versioned components. | +| Primary Users | Business and solution architects; transformation leads. | Data and knowledge engineers; ontology and platform teams. | +| Outcome | Composable business capabilities and adaptive workflows. | Reusable semantic components and data products. | +| Relationship to Each Other | Composable business **depends** on reuse. Without reusable components, there is nothing to compose. | Reuse **finds purpose** in composability. Without higher-level composition, reuse is just technical hygiene. | + +!!! tip "Two sides of the same semantic coin" + + **Reuse Enablement** creates the *building blocks*. + + **Composable Business** assembles them into *living systems*. + + Every successful technology ecosystem has a way to share reusable + components — the JavaScript world has [*npm*](https://www.npmjs.com) + with over 3.5 million packages, the Python world has + [*PyPI*](https://pypi.org) with over 600,000 packages, and so on — each + enabling developers to build upon a vast ecosystem of reusable + components. + + The **Use Case Tree (UCT)** plays the same role for the **Enterprise + Knowledge Graph (EKG)**: it is the semantic package manager that makes + every business capability, data product, and workflow discoverable, + versioned, and ready to be reused and composed safely across the + enterprise. + + + +## Getting Started + +To move toward a composable business: + +1. Model your business capabilities using the UCT — define outcomes, + personas, and dependencies. +2. Publish reusable components (stories, data products, ontologies) to + the EKG with clear provenance and semantics. +3. Compose new capabilities by linking and orchestrating existing + components rather than building from scratch. +4. Govern the lifecycle of use cases and their subcomponents — + versioning, approval, and retirement all managed within the EKG. +5. Measure reuse and adaptability as key indicators of enterprise + maturity. + +## Related Objectives + +- [Enable Reuse](enable-reuse.md) +- [Capture Knowledge](capture-knowledge.md) +- [Manage Modularity](modularity.md) +- [Achieve Interoperability](interoperability.md) + +## Summary + +Composable Business is not a new methodology — it is the natural +outcome of applying the EKGF Method. +When business capabilities, data products, and knowledge artifacts are +structured and governed through the EKG and the UCT, the enterprise +itself becomes composable: a living system of reusable knowledge, ready +to evolve continuously. diff --git a/docs/stylesheets/extra.css b/docs/stylesheets/extra.css index 7f2bbb54..9bc560d2 100644 --- a/docs/stylesheets/extra.css +++ b/docs/stylesheets/extra.css @@ -251,3 +251,112 @@ outline-offset: 2px; border-radius: 0.25rem; } + +/* ChatGPT-style table styling */ +.md-typeset table { + border-collapse: collapse; + width: 100%; + margin: 1.5rem 0; + background: transparent; + border: none !important; + border-top: none !important; + border-bottom: none !important; + border-left: none !important; + border-right: none !important; +} + +.md-typeset table thead { + border: none !important; +} + +.md-typeset table thead th { + border: none !important; + border-top: none !important; + border-bottom: 1px solid rgba(0, 0, 0, 0.1) !important; + border-left: none !important; + border-right: none !important; + padding: 0.75rem 1rem; + text-align: left; + font-weight: 600; + background: transparent; + color: inherit; +} + +[data-md-color-scheme="slate"] .md-typeset table thead th { + border-bottom-color: rgba(255, 255, 255, 0.1) !important; +} + +.md-typeset table tbody { + border: none !important; +} + +.md-typeset table tbody tr { + border: none !important; + border-top: none !important; + border-bottom: 1px solid rgba(0, 0, 0, 0.08) !important; + border-left: none !important; + border-right: none !important; + background: transparent; +} + +[data-md-color-scheme="slate"] .md-typeset table tbody tr { + border-bottom-color: rgba(255, 255, 255, 0.08) !important; +} + +.md-typeset table tbody tr:last-child { + border-bottom: none !important; +} + +.md-typeset table tbody td { + border: none !important; + border-top: none !important; + border-bottom: none !important; + border-left: none !important; + border-right: none !important; + padding: 0.75rem 1rem; + text-align: left; + background: transparent; + vertical-align: top; +} + +.md-typeset table tbody td:first-child { + font-weight: 600; +} + +.md-typeset table tbody tr:hover { + background: rgba(0, 0, 0, 0.02); +} + +[data-md-color-scheme="slate"] .md-typeset table tbody tr:hover { + background: rgba(255, 255, 255, 0.02); +} + +/* Enhanced blockquote styling */ +.md-typeset blockquote { + border-left: 4px solid var(--md-primary-fg-color); + padding-left: 1.5rem; + padding-right: 1rem; + padding-top: 0.5rem; + padding-bottom: 0.5rem; + margin: 1.5rem 0; + background: rgba(74, 35, 217, 0.03); + border-radius: 0 0.25rem 0.25rem 0; + font-style: normal; +} + +[data-md-color-scheme="slate"] .md-typeset blockquote { + background: rgba(74, 35, 217, 0.08); + border-left-color: var(--md-primary-fg-color--light); +} + +.md-typeset blockquote p { + margin: 0.5rem 0; +} + +.md-typeset blockquote p:first-child { + margin-top: 0; +} + +.md-typeset blockquote p:last-child { + margin-bottom: 0; +}