BundleFolder class

The twelve reserved folder names in a bundle's .mbd/ tree.

Each name maps 1:1 to a sub-directory under the bundle root. Consumer adapters interpret the folder's contents in domain-specific ways (UI rendering for ui/, asset resolution for assets/, …); the folder names themselves are part of the bundle format.

Properties

hashCode → int

The hash code for this object.

no setter, inherited

name → String

On-disk folder name (e.g. 'ui').

final

runtimeType → Type

A representation of the runtime type of the object.

no setter, inherited

Methods

noSuchMethod(Invocation invocation) → dynamic

Invoked when a nonexistent method or property is accessed.

inherited

toString() → String

A string representation of this object.

override

Operators

operator ==(Object other) → bool

The equality operator.

inherited

Constants

agents → const BundleFolder

Agent definitions (4-axis bindings + runtime config).

assets → const BundleFolder

Binary or text assets (icons, splash, fonts, …).

facts → const BundleFolder

Atomic subject-predicate-object fact records (typically newline- delimited or per-fact JSON files). Companion to the inline manifest.facts[] carry — large-volume facts live here.

knowledge → const BundleFolder

Knowledge sources, retriever configs.

philosophy → const BundleFolder

Philosophy / ethos definitions.

pipelines → const BundleFolder

Pipeline definitions — ordered stage sequences for data / build / deploy flows. Companion to the inline manifest.pipelines[] carry.

profiles → const BundleFolder

Profile definitions.

runbooks → const BundleFolder

Runbook definitions — ordered procedure sequences for operational tasks (incident response, recovery, routine maintenance). Companion to the inline manifest.runbooks[] carry.

skills → const BundleFolder

Skill / capability module definitions.

tools → const BundleFolder

Tool definitions — host-callable tool entries (host builtin / MCP server / cloud endpoint / bundled JS). Companion to the inline manifest.tools[] carry — large schemas or bundled JS sources live here as standalone files.

ui → const BundleFolder

UI definition files (mcp_ui_dsl JSON).

values → const List<BundleFolder>

All reserved folder names, in declaration order.

workflows → const BundleFolder

Workflow definitions — ordered step sequences. Companion to the inline manifest.workflows[] carry — large or generated workflow definitions live here as standalone files.