XNCF Extension Library Guide (Senparc.Xncf.xxx)

Scope: current NcfPackageSources version.
This page fills the missing half beside “NCF libraries”: XNCF extension modules (Senparc.Xncf.xxx).

1. Why It Feels Like “XNCF Is Missing”

The “NCF Libraries” section mainly covers Senparc.Ncf.*, which is the runtime foundation layer (Core, Repository, Service, Database, etc.).

But in NCF architecture, Senparc.Xncf.* is the capability assembly layer. Without it, docs cover the “foundation” but not the “building blocks”.

2. NCF Definition as a Modular Framework

In NCF, modularization is not just folder separation. It is a runtime-governable capability system where units are discoverable, installable, enable/disable-able, and operable.

Think in two layers:

  • Senparc.Ncf.*: framework foundation layer (shared runtime capabilities and constraints).
  • Senparc.Xncf.*: capability module layer (feature delivery by installable modules).

2.1 XNCF as a Single-Granularity Module Unit (Key)

A Senparc.Xncf.xxx module is a single-granularity capability unit:

  • Own Register metadata and lifecycle (install/update/uninstall).
  • Can declare its own database, menu, Function, and MCP capability.
  • Can be independently enabled, disabled, operated, and secured.

This is the core engineering value of NCF modularity: capabilities are split into governable minimal units instead of being fused into a monolith.

3. Why Developers Should Care About XNCF Modules

  • Lower coupling: clear boundaries, less cross-module entanglement.
  • Independent evolution: module-level version iteration.
  • Controlled release: module-level rollout and rollback.
  • Stronger security: high-risk capabilities (for example Terminal/DatabaseToolkit) can be isolated.
  • Better team collaboration: module-level ownership and cleaner PR boundaries.

4. Common XNCF Module Map in the Current Version

4.1 System Baseline Modules

  • Senparc.Xncf.SystemCore
  • Senparc.Xncf.SystemManager
  • Senparc.Xncf.SystemPermission
  • Senparc.Xncf.XncfModuleManager
  • Senparc.Xncf.Menu
  • Senparc.Xncf.Tenant

4.2 AI / Agent / RAG Modules

  • Senparc.Xncf.AIKernel
  • Senparc.Xncf.PromptRange
  • Senparc.Xncf.AgentsManager
  • Senparc.Xncf.KnowledgeBase
  • Senparc.Xncf.MCP
  • Senparc.Xncf.AIAgentsHub

4.3 Tooling and Ops Modules

  • Senparc.Xncf.XncfBuilder
  • Senparc.Xncf.DatabaseToolkit
  • Senparc.Xncf.FileManager
  • Senparc.Xncf.Terminal
  • Senparc.Xncf.FirmwareUpdate
  • Senparc.Xncf.ChangeNamespace
  • Senparc.Xncf.WeixinManager

For full versions, order, and scenario guidance:

5. Developer Guidance: Design XNCF as Single-Granularity Units

Recommended baseline rules:

  1. One module should focus on one capability domain.
  2. Keep module boundaries explicit: DB/config/auth/menu/function scope.
  3. Prefer [FunctionRender] for executable capability declaration.
  4. Enable EnableMcpServer only when needed, with explicit security controls.
  5. Run high-risk modules with least privilege and audit logging.

6. Where to Continue Reading