Repository navigation
Home
James Daley edited this page Jun 20, 2026
·
5 revisions
Forsetti Framework - Windows is a proprietary C++20 modular runtime framework for Windows 11 applications. It provides compatibility-governed module activation, entitlement checks, capability-scoped service access, registration confirmation, and framework-owned UI surface composition.
The current main repository builds:
-
ForsettiCore- pure C++20 runtime authority with no platform dependencies. -
ForsettiPlatform- Windows SDK adapters for networking, storage, secure storage, file export, module registration storage, view factories, and telemetry. -
ForsettiHostTemplate- sealed host composition layer that bootstraps runtime dependencies and exposes host control state. -
ForsettiExampleServiceModule,ForsettiExampleUIModule, andForsettiExampleAppModule- isolated reference modules with owned manifests. -
samples/ForsettiDemo- downstream composition root for the host template and example modules. - Native test suites for core, platform, and architecture guardrails.
flowchart TB
Forsetti["Forsetti Framework - Windows"]
Runtime["Runtime\nmanifest discovery, registration, compatibility, entitlements, restore"]
Modules["Modules\nservice, UI, app"]
Capabilities["Capabilities\nservice access, UI checks, default roles"]
Platform["Platform\nWinHTTP, Registry, DPAPI, local export, registration, view factories"]
Host["HostTemplate\nboot, activation, state snapshots"]
Governance["Governance\nlocal guardrails, repository surface checks, evidence"]
Forsetti --> Runtime
Forsetti --> Modules
Forsetti --> Capabilities
Forsetti --> Platform
Forsetti --> Host
Forsetti --> Governance
| Page | Use It For |
|---|---|
| Architecture | Layering, dependency flow, component ownership, and repository layout. |
| Runtime-Lifecycle | Boot, discovery, registration confirmation, activation, deactivation, persistence, restore, and entitlement reconciliation. |
| Module-System | Module types, manifest schema 1.1, runtime requirements, registry factories, compatibility checks, and examples. |
| Capabilities-and-Security | Capability policy, scoped services, source identity, message rules, default roles, and reserved UI policy. |
| UI-Surface-Model | UI/app activation, toolbar items, view injections, overlays, declared UI IDs, and theme mask handling. |
| Platform-Services | Windows platform adapters, module registration persistence, and view factory registration. |
| Build-and-Testing | Toolchain setup, CMake presets, tests, guardrail scripts, hosted checks, and validation evidence. |
| API-Reference | Public interfaces, value types, enums, runtime components, host template contracts, and platform services. |
| Coding-Policy | Engineering rules and behavioral invariants. |
| Governance-and-Operations | Pull request workflow, discussion automation, evidence policy, and documentation upkeep. |
| Roadmap-and-Risks | Native validation blockers, remote build/test parity, dependency pinning, and future hardening. |
flowchart LR
Manifest["Module manifest\nschema 1.1, requirements, capabilities"]
Registration["ModuleRegistrationService\ncanonical manifest confirmation"]
Registry["ModuleRegistry\nentryPoint factory"]
Checker["CompatibilityChecker\nplatform, version, policy"]
Requirements["ModuleRequirementValidator\nI/O, UI, data isolation"]
Manager["ModuleManager\nactivation authority"]
Context["IForsettiModuleContext\nscoped module API"]
Module["Module instance\nstart and stop"]
Surface["UISurfaceManager\ncurrent UI surface"]
Store["ActivationStore\npersisted state"]
Manifest --> Registration
Manifest --> Checker
Manifest --> Requirements
Manifest --> Registry
Registration --> Manager
Checker --> Manager
Requirements --> Manager
Registry --> Manager
Manager --> Context
Context --> Module
Manager --> Module
Manager --> Surface
Manager --> Store
Runtime-boundary alignment is merged into main. Evidence now lives under .forsetti/alignment.
| Area | Current State |
|---|---|
| Source implementation | Manifest schema/template 1.1, registration confirmation, runtime requirements, scoped module context, default roles, HostTemplate, split examples, templates, and demo are present in main. |
| Local static validation | JSON parsing, manifest validation, script compilation/config validation, repository surface scanning, and diff checks passed during alignment. |
| Hosted validation |
Repository Surface Check passed for the merged pull request. |
| Native Windows validation | Debug/Release CMake, CTest, MSVC, PowerShell guardrail wrapper, and vcpkg validation remain blocked until run on a Windows/MSVC machine with VCPKG_ROOT configured. |
cmake --preset debug
cmake --build --preset debug
ctest --preset debug --output-on-failure
.\Scripts\verify-forsetti-guardrails.ps1If CMake is not on PATH, use the Visual Studio bundled CMake and set VCPKG_ROOT before running the commands.
Forsetti Framework - Windows. Proprietary. Patent Pending. Repository: https://github.com/flynn33/Forsetti-Framework-Windows