TheSingularityWorkshop.FSM_COS 0.1.0-alpha.6

✳️ 00 The Singularity Workshop — FSM_COS

FSM_COS composes requested capabilities into a RuntimeAssembly. It is a composition boundary—not an application, GUI, engine, repository, or execution loop.

🟦 01 — What is FSM_COS?

A RuntimeManifest identifies the MicroBundles and versions a caller wants. FSM_COS resolves their dependencies, loads the composition, performs bounded arbitration, and returns a RuntimeAssembly for the host to use.

🟣 02 — Why does it exist?

Hosts should not need to duplicate the same composition and dependency logic for every experience. FSM_COS gives that responsibility a focused home while leaving application behavior and presentation to the host.

Compatibility is not automatic: the selected bundles, their contracts, and the host must work together.

🩵 03 — How does it work?

RuntimeManifest → FSM_COS → RuntimeAssembly → Host
                    │
                    ├─ resolve MicroBundles and dependencies
                    ├─ load the composition
                    └─ arbitrate toward convergence

• MicroBundleDomain owns the MicroBundle contract.
• The host or repository supplies the catalog used to resolve bundles.
• FSM_COS composes the requested capabilities.
• The host owns execution, lifecycle, UI, and presentation.

🟢 04 — See it in a minute

To install FSM_COS, choose an available version from the NuGet package page. If you intend to use a prerelease, request prerelease versions explicitly:

dotnet add package TheSingularityWorkshop.FSM_COS --prerelease

Installation adds a composition library; it does not create an application. FSM_COS needs a catalog supplied by the host. To see the composition behavior running, clone the source repository and run its minimal consumer sample:

git clone https://github.com/TrentBest/TheSingularityWorkshop.FSM_COS.git
cd TheSingularityWorkshop.FSM_COS
dotnet run --project samples/FSM_COS.MinimalConsumer/FSM_COS.MinimalConsumer.csproj

The sample creates a report bundle that depends on a data-source bundle. The expected result is Assembly order: 2 -> 1, proving the dependency is loaded before the requested bundle. It defines its own catalog and example bundles; these are not built-in FSM_COS types. The sample references the local source project so it can be verified before a candidate version is published.

For a complete consumer guide, see Consuming MicroBundles. The package targets .NET 8 and its direct dependencies are:

• FSM_API — state/context primitives.
• MicroBundleDomain — the MicroBundle contract.
• FSM_UserIO — the platform-neutral SemanticIntent boundary.

This source candidate declares version 0.1.0-alpha.6; a source version declaration alone does not establish publication status. Check the NuGet package page for the version actually available.

If that page still lists 0.1.0-alpha.5 as the latest version, do not assume it has the same API as this alpha.6 source: alpha.6 uses explicit versioned MicroBundleManifestEntry roots and an external configuration-source contract. The source-repository sample demonstrates the candidate contract without pretending the newer package is already published.

🟪 05 — Available documentation and theory

• Project overview — the bigger picture and quick proof.
• What Is FSM_COS? — a plain-language introduction for readers new to software composition.
• Theory — why composition is a distinct operation.
• Architecture — ownership and runtime flow.
• Runtime Manifest — the composition request.
• RuntimeAssembly — the host handoff.
• Arbitration — reconciliation and convergence.
• Documentation Index — all focused guides.
• Alpha.6 release notes — included contracts and explicit limitations.
• Development — build and verification.
• Source and issues

GitHub · Coder Legion · Patreon · PayPal · FSM_API · FSM_Serialization · WebPage

The Singularity Workshop — Tools for the curious, the bold, and the systemically inclined.

Because state shouldn't be a mess.

And because static boundaries are invitations to cause trouble.