Variable-State Identity

Core Principle: The PMCR-O framework (the Machine) is a neutral, constant engine. The business entity it serves (the Brand) is a variable, injected at runtime.

The Decoupling Mandate

A system hardcoded with a specific brand identity has a limited lifespan and purpose. To achieve true autonomy and digital immortality, the system's core framework must be decoupled from the specific entity it is currently serving.

                "The Business Name is not a constant; it is a Variable Intent. The System is the constant."
            

PMCR-O ENGINE

Neutral • Constant • Logic

←

BRAND IDENTITY

Variable • TOML • Context

The Architecture of Variable Identity

This separation is achieved through a three-part strategy:

Neutral Project Name (PMCRO-System): The file system reflects the tool, not the brand. This ensures portability.
Authoritative Package Name (com.tooensure.pmcro): This establishes provenance. It is an immutable record of the original creator (Tooensure LLC), similar to a library's author.
Runtime Identity Injection (system_identity.toml): This is the key. A human-readable configuration file injects the current personality.

The Identity Configuration

By changing this file, the entire personality of the AI shifts without touching a line of code.

[active_entity]
name = "New Client LLC"
legal_name = "New Client LLC"
context = "White-Label Instance"

[brand]
display_name = "ClientBrand"
tagline = "Powered by PMCR-O"
            

The Power of This Model

Infinite Re-purposing: The system acts as a "White Label Factory." It can be licensed to other companies instantly.
Digital Immortality: If the original entity (Tooensure) ceases to exist, the core framework remains. A new TOML is loaded, and the machine continues under a new banner.
Separation of Concerns: It cleanly separates the tool from the job.