Skip to content

Commit 907887e

Browse files
jgelukjgeluk
authored
feat(docs): enhance composable business page with comprehensive content (#23)
- 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)
1 parent 257a5ca commit 907887e

File tree

2 files changed

+229
-12
lines changed

2 files changed

+229
-12
lines changed

‎docs/objective/composable-business.md‎

Lines changed: 120 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -8,21 +8,129 @@ hide:
88
# B: Composable Business
99

1010
<!--summary-start-->
11-
_The Future of Business Is Composable_
11+
_Making the enterprise adaptive through modular knowledge and
12+
reusable capabilities_
1213
<!--summary-end-->
1314

15+
## Objective
1416

15-
!!! info
17+
A composable business is one that can adapt and reconfigure itself
18+
continuously — not through massive reorganisations or costly rewrites,
19+
but through modular, reusable, and semantically connected components.
1620

17-
Work in progress. Points to make:
21+
Composable Business is the organisational expression of the Enterprise
22+
Knowledge Graph (EKG) and the Use Case Tree (UCT) method. It represents
23+
the ability to assemble business capabilities dynamically from trusted,
24+
reusable building blocks: use cases, data products, stories, workflows,
25+
and ontologies — all governed within the EKG.
1826

19-
- Explain that the [Use Case Tree (UCT)](../concept/use-case-tree.md) is the ultimate way to implement
20-
what Gartner now calls "Composable Business":
21-
- https://www.gartner.com/smarterwithgartner/gartner-keynote-the-future-of-business-is-composable
22-
- Same for "Packaged Business Capabilities (PBCs)" (also called Packaged Business Components):
23-
- https://www.elasticpath.com/blog/what-are-packaged-business-capablities
24-
- https://www.elasticpath.com/blog/what-is-the-difference-between-PBCs-and-microservices
25-
- https://blog.dreamfactory.com/enterprise-it-building-blocks-the-packaged-business-capability/
26-
- Explain what's missing with the various proposed approaches in the articles above.
27-
Why Semantic Technology and in particular EKG & the UCT is key to _really_ make this fly.
27+
## Why It Matters
2828

29+
Most organisations struggle to change because their systems, data, and
30+
processes are tightly coupled and fragmented. Innovation requires
31+
coordination across dozens of silos, each with its own models and
32+
assumptions.
33+
34+
Composable Business replaces this fragility with semantic modularity —
35+
every business capability becomes a governed component that can be
36+
reused, combined, or replaced without breaking the whole.
37+
38+
The result:
39+
40+
- Faster adaptation to market or regulatory change
41+
- Continuous innovation without re-engineering core systems
42+
- Resilience through modular design
43+
- Clarity and governance through shared semantics
44+
45+
## The Role of the Use Case Tree (UCT)
46+
47+
The Use Case Tree (UCT) is the organising structure of composability.
48+
It defines how business capabilities are decomposed into modular use
49+
cases, each of which can be modelled, implemented, and run
50+
independently, yet still fit coherently into the enterprise
51+
architecture.
52+
53+
Every node in the UCT represents a reusable component — a semantic
54+
package containing:
55+
56+
- Defined outcomes and personas
57+
- Stories (tool functions or APIs)
58+
- Data products and ontologies
59+
- Workflows and policies
60+
61+
This makes the UCT the semantic package manager of the EKG — similar to
62+
how npmjs.org or pypi.org manage software packages — but at enterprise
63+
scale, spanning business, data, and knowledge assets.
64+
65+
## Composable Business vs. Reuse Enablement
66+
67+
### Two sides of the same semantic coin
68+
69+
While Composable Business and Reuse Enablement both aim to make the
70+
enterprise modular, they operate at different levels of abstraction.
71+
The table below outlines how they relate and reinforce one another
72+
within the EKGF Method.
73+
74+
| Aspect | Composable Business | Reuse Enablement |
75+
|--------|---------------------|------------------|
76+
| Focus / Orientation | _How business capabilities are composed, orchestrated, and evolved_ | _How knowledge assets and components are packaged and shared_ |
77+
| 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?" |
78+
| 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. |
79+
| 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. |
80+
| 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. |
81+
| 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. |
82+
| Primary Users | Business and solution architects; transformation leads. | Data and knowledge engineers; ontology and platform teams. |
83+
| Outcome | Composable business capabilities and adaptive workflows. | Reusable semantic components and data products. |
84+
| 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. |
85+
86+
!!! tip "Two sides of the same semantic coin"
87+
88+
**Reuse Enablement** creates the *building blocks*.
89+
90+
**Composable Business** assembles them into *living systems*.
91+
92+
Every successful technology ecosystem has a way to share reusable
93+
components — the JavaScript world has [*npm*](https://www.npmjs.com)
94+
with over 3.5 million packages, the Python world has
95+
[*PyPI*](https://pypi.org) with over 600,000 packages, and so on — each
96+
enabling developers to build upon a vast ecosystem of reusable
97+
components.
98+
99+
The **Use Case Tree (UCT)** plays the same role for the **Enterprise
100+
Knowledge Graph (EKG)**: it is the semantic package manager that makes
101+
every business capability, data product, and workflow discoverable,
102+
versioned, and ready to be reused and composed safely across the
103+
enterprise.
104+
105+
106+
107+
## Getting Started
108+
109+
To move toward a composable business:
110+
111+
1. Model your business capabilities using the UCT — define outcomes,
112+
personas, and dependencies.
113+
2. Publish reusable components (stories, data products, ontologies) to
114+
the EKG with clear provenance and semantics.
115+
3. Compose new capabilities by linking and orchestrating existing
116+
components rather than building from scratch.
117+
4. Govern the lifecycle of use cases and their subcomponents —
118+
versioning, approval, and retirement all managed within the EKG.
119+
5. Measure reuse and adaptability as key indicators of enterprise
120+
maturity.
121+
122+
## Related Objectives
123+
124+
- [Enable Reuse](enable-reuse.md)
125+
- [Capture Knowledge](capture-knowledge.md)
126+
- [Manage Modularity](modularity.md)
127+
- [Achieve Interoperability](interoperability.md)
128+
129+
## Summary
130+
131+
Composable Business is not a new methodology — it is the natural
132+
outcome of applying the EKGF Method.
133+
When business capabilities, data products, and knowledge artifacts are
134+
structured and governed through the EKG and the UCT, the enterprise
135+
itself becomes composable: a living system of reusable knowledge, ready
136+
to evolve continuously.

‎docs/stylesheets/extra.css‎

Lines changed: 109 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -251,3 +251,112 @@
251251
outline-offset: 2px;
252252
border-radius: 0.25rem;
253253
}
254+
255+
/* ChatGPT-style table styling */
256+
.md-typeset table {
257+
border-collapse: collapse;
258+
width: 100%;
259+
margin: 1.5rem 0;
260+
background: transparent;
261+
border: none !important;
262+
border-top: none !important;
263+
border-bottom: none !important;
264+
border-left: none !important;
265+
border-right: none !important;
266+
}
267+
268+
.md-typeset table thead {
269+
border: none !important;
270+
}
271+
272+
.md-typeset table thead th {
273+
border: none !important;
274+
border-top: none !important;
275+
border-bottom: 1px solid rgba(0, 0, 0, 0.1) !important;
276+
border-left: none !important;
277+
border-right: none !important;
278+
padding: 0.75rem 1rem;
279+
text-align: left;
280+
font-weight: 600;
281+
background: transparent;
282+
color: inherit;
283+
}
284+
285+
[data-md-color-scheme="slate"] .md-typeset table thead th {
286+
border-bottom-color: rgba(255, 255, 255, 0.1) !important;
287+
}
288+
289+
.md-typeset table tbody {
290+
border: none !important;
291+
}
292+
293+
.md-typeset table tbody tr {
294+
border: none !important;
295+
border-top: none !important;
296+
border-bottom: 1px solid rgba(0, 0, 0, 0.08) !important;
297+
border-left: none !important;
298+
border-right: none !important;
299+
background: transparent;
300+
}
301+
302+
[data-md-color-scheme="slate"] .md-typeset table tbody tr {
303+
border-bottom-color: rgba(255, 255, 255, 0.08) !important;
304+
}
305+
306+
.md-typeset table tbody tr:last-child {
307+
border-bottom: none !important;
308+
}
309+
310+
.md-typeset table tbody td {
311+
border: none !important;
312+
border-top: none !important;
313+
border-bottom: none !important;
314+
border-left: none !important;
315+
border-right: none !important;
316+
padding: 0.75rem 1rem;
317+
text-align: left;
318+
background: transparent;
319+
vertical-align: top;
320+
}
321+
322+
.md-typeset table tbody td:first-child {
323+
font-weight: 600;
324+
}
325+
326+
.md-typeset table tbody tr:hover {
327+
background: rgba(0, 0, 0, 0.02);
328+
}
329+
330+
[data-md-color-scheme="slate"] .md-typeset table tbody tr:hover {
331+
background: rgba(255, 255, 255, 0.02);
332+
}
333+
334+
/* Enhanced blockquote styling */
335+
.md-typeset blockquote {
336+
border-left: 4px solid var(--md-primary-fg-color);
337+
padding-left: 1.5rem;
338+
padding-right: 1rem;
339+
padding-top: 0.5rem;
340+
padding-bottom: 0.5rem;
341+
margin: 1.5rem 0;
342+
background: rgba(74, 35, 217, 0.03);
343+
border-radius: 0 0.25rem 0.25rem 0;
344+
font-style: normal;
345+
}
346+
347+
[data-md-color-scheme="slate"] .md-typeset blockquote {
348+
background: rgba(74, 35, 217, 0.08);
349+
border-left-color: var(--md-primary-fg-color--light);
350+
}
351+
352+
.md-typeset blockquote p {
353+
margin: 0.5rem 0;
354+
}
355+
356+
.md-typeset blockquote p:first-child {
357+
margin-top: 0;
358+
}
359+
360+
.md-typeset blockquote p:last-child {
361+
margin-bottom: 0;
362+
}

0 commit comments

Comments
 (0)