TheSingularityWorkshop.MicroBundleDomain 1.0.0

TheSingularityWorkshop.MicroBundleDomain

Domain-side foundation for MicroBundle definitions.

A MicroBundle is a loadable semantic capability.

This repository provides the small, reusable domain-side descriptors needed to identify a MicroBundle and declare its composition surface without teaching the hosting ecosystem what the capability means.

What belongs here

The first contract is deliberately narrow:

MicroBundleDescriptor
    ├── identity
    ├── version
    ├── dependencies
    └── providers

The descriptor records composition facts. It does not implement a domain such as atoms, thermal properties, meshes, logic gates, or AEC.

Dependencies

A dependency declares that another MicroBundle is part of the capability's composition.

Providers

A provider is identified but not interpreted here.

For example, a domain package may choose to expose providers named preview, mesh, or something completely different. This package does not assign semantics to those names.

That keeps the ecosystem blind to domain meaning.

Code-derived MicroBundles

A domain package may define executable behavior in code and expose its composition metadata through this foundation.

Code defines the capability.
MicroBundleDomain describes the capability.
FSM_COS composes the capability.
Forge authors the composition.
Hosting persists and distributes it.
GUI manifests it.

The layers remain separate.

Demand-driven composition

Optional capabilities remain optional.

A bundle that declares no dependencies or providers can stand alone. A richer bundle can declare only the capabilities it needs. The runtime can then resolve and load the resulting composition rather than pulling an entire domain into memory.

Geometry as a compatibility surface

The Forge metaphor makes compatibility visible: a state shell exposes a transition surface, while a condition supplies the shape that can fit it.

The geometry is not the runtime itself. It is a manifestation of the contracts that determine whether a capability can compose.

Relationship to FSM_COS

FSM_COS owns runtime composition. This package owns domain-side description.

Domain MicroBundle
       |
       v
MicroBundleDomain
       |
       v
    FSM_COS
       |
       v
 RuntimeAssembly

The descriptor is not a replacement for IMicroBundle. It is metadata that a domain package can use while implementing or generating runtime MicroBundles.

Packaging

Package: TheSingularityWorkshop.MicroBundleDomain
Version: 0.1.0-alpha.2
Target: .NET 8
License: MIT

Concrete domain families should remain separately owned and publishable.

Status

This is an alpha foundation. The contract is intentionally small so that WebPage can consume domain packages without the hosting layer accumulating domain-specific assumptions.

See MicroBundle Domain Theory.

🔗 Resources & Support

📦 Get FSM_API

• Unity Asset Store: FSM_API for Unity
• Core NuGet: TheSingularityWorkshop.FSM_API
• Source Code: TheSingularityWorkshop.MicroBundleDomain on GitHub
• This Package: TheSingularityWorkshop.MicroBundleDomain

💖 Support The Singularity Workshop

• Patreon: Support us on Patreon
• PayPal: Make a donation

<p align="center"> <a href="https://github.com/TrentBest/FSM_API"> <img src="https://raw.githubusercontent.com/TrentBest/FSM_API/master/Documentation/Branding/TheSingularityWorkshop.png" alt="The Singularity Workshop" height="200"> </a> </p>

<p align="center"> <em>The Singularity Workshop — Tools for the curious, the bold, and the systemically inclined.</em><br> <strong>Because state shouldn't be a mess.</strong> </p>