img-blur-shadow-blog-2
Component-Based Development

Observability in CNCF

In AI-driven development, one of the central questions is how to achieve non-functional requirements such as Security and Observability. Even observability alone requires many cross-cutting concerns such as distributed tracing, metrics, structured diagnostics, payload protection, and integration with external observability platforms. Delegating these concerns to individually generated implementations rapidly increases generation, review, and operational costs while also destabilizing quality assurance. For this reason, once sufficient structural information is described in the Literate Model, the CML&CNCF model compiler and execution framework establish Security and Observability as cross-cutting runtime behavior. Read More

2026-05-18

img-blur-shadow-blog-2
Component-Based Development

CNCF Authorization Model

CNCF authorization evaluates both operation entry points and resource access. Roles, permissions, relations, and ABAC are normalized into capabilities and guards, and evaluated through a unified decision model. Read More

2026-05-04

CBD Understanding the CNCF Execution Model Through HelloWorld

SimpleModeling is a development methodology based on component-oriented principles. To make component-oriented development viable, an execution system for components is required in addition to the definition of conceptual models. For this purpose, the Cloud Native Component Framework has been developed as a component framework for cloud applications that run on cloud platforms. In this article, we will explore the execution model of the Cloud Native Component Framework through a HelloWorld example.

2026-01-26

CBD Cloud Native Component Framework:HelloWorld

Cloud Native Component Framework is a component framework that serves as the execution foundation for literate model-driven development. The shortest path to understanding CNCF is to actually run it first. By starting with command execution and proceeding to server, client, and custom components, you can confirm that the internal execution model does not change even when the execution form does.

2026-01-19

CBD AI-Era Executable Specification

A executable specification is neither merely a test nor simply TDD that drives implementation. It connects written specifications, analysis and design models, and implementation code, serving as a core artifact through which humans and AI agree—by execution—on what the correct specification is. By placing executable specifications at the center, analysis models become grounded in implementation, and implementation gains semantic justification.

2026-01-12