Who it is for
People using or building Thirteenfold applications that need consistent, explicit controls.
Shared foundation
Thirteenfold Core
A shared foundation for application lifecycle, permissions, policy checks, and common runtime services.
Shared foundation, shown separately from the 13 application plans.
Why it is planned
A practical role in the family.
Example use
An application requests an operation. Core is intended to verify its scope and permission before the responsible product performs the work.
Intended benefit
Designed to keep authorization consistent across the family while each application owns its own purpose and data.
Intended workflow
How the work would flow.
This describes the planned experience. It does not establish that these capabilities are available.
Receive a request that identifies the user, application, target, and intended operation.
Check the applicable permissions, policy, and operation limits.
Allow the bounded handoff or reject it with an observable outcome.
Scope and relationships
Clear ownership of the work.
Data and authority boundaries
Core is intended to verify application authority. It is not a shared store for every product’s private data or an independent product-release authority.
How it fits with the family
Suite is the catalog and launcher experience. Core supplies the shared control and runtime foundation beneath it.
Explore Thirteenfold Suite