--- name: Arco modules version: 0.10.0 status: draft owner: Stoirm Arnold last_updated: 15-Sep-2026 --- # Arco modules ## Purpose This is the lightweight working catalogue of Arco modules while the operating system is evolving quickly. It records which components are currently treated as modules and their maturity. It does not define module behaviour; each module's canonical operating file owns that behaviour. ## Boundary An Arco module is a separable body of maintained system knowledge or behaviour that can be deployed or enabled where useful without becoming a universal rule for every deployment. This catalogue should not turn every Arco concern or function into a module. Universal operating layers, deployment mechanics, validation functions, architectural memory and Governance components remain outside the module catalogue unless deliberately promoted into modules later. All modules listed here inherit the universal module contract from `arco-module-manual.md`. This catalogue records existence and maturity only; it does not restate that standard. ## Status definitions **Live** — in active use as a working Arco module. **Early** — exists and is usable, but its structure or operating model is still developing. A module can be Early without being enabled in the current deployment. **Ideation** — a potential module direction is established, but the boundary is not resolved enough to treat it as a canonical module. ## Live ### Skills Repeatable maintained capabilities. Core source: `/Arco/modules/skills/arco-skills.md`. Deployments receive `readme-skills.md`; deployment-specific paths and Register identifiers belong in `readme-skills-local.md` where required. Stoirm Ltd is live on this structure. ### Personas Reusable perspectives or modes of thinking. Core source: `/Arco/modules/personas/arco-personas.md`. Deployments receive `readme-personas.md`; deployment-specific storage and Persona inventory belong in `readme-personas-local.md` where required. Stoirm Ltd is live on this structure. ## Early ### Context Durable personal and organisational context that reduces repeated explanation and gives Arco a maintained understanding of the people, organisations and environments it operates within. Core source: `/Arco/modules/context/arco-context.md`. The Core → deployed → local structure has been proven, but Context remains Early because the operating model and deployment prerequisites are still developing. It is not currently enabled in Stoirm Ltd routing. ## Ideation ### Decisions Optional durable organisational decision memory and live decision-management capability. Decisions has a clear emerging boundary and is now treated as a module candidate, but it has not yet been promoted into a canonical Core module. Decisions is expected to consume Governance for permissions and approvals rather than own those mechanisms itself. ### Policies Maintained organisational policy knowledge and operating guidance. Policies is now an emerging module candidate because organisations need a governed way for AI to use and maintain policy while allowing deployment-specific ownership and approval settings. Policies is expected to consume Governance/Approvals rather than define its own approval mechanics. Its exact source-of-truth and deployment model remain unresolved. ## Non-module boundary The Module Manual (`arco-module-manual.md`) is the universal contract inherited by modules and future Module Builder work; it is not itself a module. The System Manual is a universal Core operating layer, not a module. Dry Runs are a validation function beneath the System Manual, not a module. Design (`arco-design.md`) is Arco's architectural-memory layer. It explains why architectural choices were made and meaningful alternatives rejected; it is not an optional module and does not govern runtime behaviour. Deployment is a Core operating concern that determines how Arco is installed and configured, not currently a module. Governance is a foundational Arco subsystem for organisational deployments, not an optional module. Its Core definition is `arco-governance.md`. Roles, Permissions and Approvals are Governance components. Their Core drafts are `arco-roles.md`, `arco-permissions.md` and `arco-approvals.md`; they are not separate optional modules. Defrag is a live Core maintenance function defined by `arco-defrag.md`; it is deliberately not a module. Arcopsy remains an emerging deployment-review function under Development and is also not currently a module. System Governor is a required Arco Role within Governance, not a standalone module. Champion is an optional Arco Role. VIP remains an emerging Role concept in Development and has not yet been promoted into the Core Roles definition. ## Maintenance Move modules between maturity sections as their state changes. Add a component here only when there is a deliberate architectural decision that it is, or is becoming, an Arco module. When development work changes module existence, scope, lifecycle state or module relationships, reconcile this catalogue in the same change. Do not duplicate the universal module contract from `arco-module-manual.md`, detailed operating rules from module READMEs, rationale from `arco-design.md`, or unresolved design detail from `arco-development.md`. ## Changelog | Date | Version | Change | Approved by | Changed by | |---|---|---|---|---| | 15-Sep-2026 | 0.10.0 | Recorded Defrag as a live non-module Core maintenance function owned by `arco-defrag.md`, while retaining Arcopsy as an emerging non-module function under Development. | Stoirm Arnold | GPT-5.6 Sol | | 15-Sep-2026 | 0.9.1 | Updated live catalogue pointers and terminology to the renamed canonical module contract `arco-module-manual.md`; historical changelog references remain unchanged. | Stoirm Arnold | GPT-5.6 Sol | | 15-Sep-2026 | 0.9.0 | Added `arco-module-standard.md` as the single inherited contract for all modules and clarified that the module catalogue records existence/maturity rather than duplicating universal module rules. | Stoirm Arnold | GPT-5.6 Sol | | 15-Sep-2026 | 0.8.0 | Added Policies as an Ideation-stage module candidate and recorded that it should consume shared Governance/Approvals rather than create module-specific approval mechanics. | Stoirm Arnold | GPT-5.6 Sol | | 15-Sep-2026 | 0.7.1 | Recorded `arco-design.md` as a Core architectural-memory layer outside the module catalogue and clarified that module catalogue maintenance must not duplicate Design rationale. | Stoirm Arnold | GPT-5.6 Sol | | 15-Sep-2026 | 0.7.0 | Reconciled Governance promotion: recorded Governance as a foundational non-module subsystem; Roles, Permissions and Approvals as Governance components; System Governor and Champion as Roles; VIP as an unpromoted emerging Role concept; and Decisions as the current optional module candidate that will consume Governance. | Stoirm Arnold | GPT-5.6 Sol | | 15-Sep-2026 | 0.6.0 | Reconciled the module catalogue with the current Arco architecture: retained Skills and Personas as Live and Context as Early; removed the implication that Roles, Approvals or Deployment are established modules; added Permissions, Decisions and Governance to the unresolved boundary; clarified System Manual, Dry Runs, Deployment, Arcopsy, Defrag and System Governor as non-module or unresolved concerns. | Stoirm Arnold | GPT-5.6 Sol | | 14-Sep-2026 | 0.5.0 | Recorded Context Core extraction and Stoirm local split while retaining Context as Early/draft and explicitly unrouted until local deployment prerequisites are configured. | Stoirm Arnold | GPT-5.6 Sol (Medium) | | 14-Sep-2026 | 0.4.0 | Promoted Personas from Early to Live after successful Core → deployed → local extraction and Stoirm Ltd deployment. | Stoirm Arnold | GPT-5.6 Sol (Medium) | | 14-Sep-2026 | 0.3.0 | Updated Skills to reflect its completed Core → deployed → local promotion and its role as the first fully promoted live Arco module. | Stoirm Arnold | GPT-5.6 Sol (Medium) | | 11-Sep-2026 | 0.2.0 | Brought the module catalogue into line with current development: moved Context to Early while keeping it explicitly non-live in Stoirm Ltd, added Roles and promoted Deployment configuration to Ideation, clarified System Governor as a Role rather than a module, and added the requirement to keep this catalogue synchronized with development changes. | Stoirm Arnold | GPT-5.6 Sol (Medium) | | 11-Sep-2026 | 0.1.0 | Created the initial lightweight Arco module catalogue, separated into Live, Early, Ideation and Concept. | Stoirm Arnold | GPT-5.6 Sol (Medium) |