author > prove > enforce > deliver > lock

One closed loop from a prompt to a proven, enforced, peer-delivered desired state.

DSCForge authors and proves DSC v3 configs. ConfigFabric assigns and enforces them by Entra device group. RepoFabric delivers the apps those configs need over LAN peers. One sign-in, one ledger, one store, one docker compose.

scroll to ride the loop
01

DSCForge authors and proves

Plain language AI chat, GPResults, and automated configuration extract converge in the forge. Schema-validated DSC v3 YAML comes out, compared across a pool of models with a QA gate, then proven on real Hyper-V, Proxmox, UNRAID, or physical targets that revert clean.

02

ConfigFabric assigns and enforces

A proven config publishes straight into the desired-state layer. Entra device groups decide where it lands, phase and prerequisites order the manifest, and endpoints apply it with dsc config set in Detect or Apply mode. No service to install.

03

RepoFabric delivers

The apps those configs need arrive from a private winget source that serves only vetted builds. One pull crosses the WAN, then PeerDist hashes let BranchCache and Delivery Optimization hand the installer peer to peer across the subnet.

The config you followed out of the forge is now enforced across the whole field. Underneath all three fabrics: one Entra sign-in, one UPN-attributed audit trail, one Gitea store, one docker compose - and a version-lock ledger that fails closed, so delivery never breaks a live policy.

Three layers, one control plane,
one closed loop.

the forge

DSCForge

Turn natural language, GPO exports, and live system scans into schema-validated DSC v3 YAML across local or cloud models with failover and a side-by-side QA gate. Prove drafts on real targets that revert clean, then publish on the schema version you pin.

the desired-state layer

ConfigFabric

Assign proven configs by transitive Entra device-group membership. Configs declare phase and prerequisites, the service emits a topologically ordered manifest, and endpoints apply in Detect or Apply mode via Intune, scheduled task, or interactive SYSTEM.

the delivery fabric

RepoFabric

A private winget source that serves only vetted builds and advertises PeerDist hashes so installers travel the LAN, not the WAN. Curated auto-update, one-click Intune policy export, and a savings dashboard over 7 / 30 / 90 days.

the substrate

One control plane

One Entra sign-in, one UPN-attributed audit ledger stamped by source fabric, one Gitea store, one docker compose deployment. A version-lock ledger guards the builds enforced state depends on. Run all three together, or stand one up at a time.

What the integration buys you

The suite versus a stitched toolchain. marks capabilities only possible because the three share one fabric.

one compose. one identity. one loop.

Author it. Prove it.
Enforce it. Deliver it.

Deploy the Fabric Suite