Skip to content

Architecture Decision Records

ADRs for the Ansible Automation Portal and its plugins. They are public by default. An ADR stays unpublished only if it is labeled confidential or still contains secrets, internal hostnames, or customer data after a scrub.

Numbers are global (001, 002, …). Folders are the audience, not a second number space.

Folder Audience Third-party authors
common Every factory plugin, in-tree or out-of-tree Required
third-party Extra obligations for plugins that live in other repositories Required
host Portal host, first-party plugins, installer, SDLC Optional; skip unless you are changing the host

Index

ADR Title Audience Status
001 Configuration Storage and Precedence host Proposed
002 Configuration Boundary Rule host Proposed
003 Admin Experience — Wizard and Settings Pages host Proposed
004 Authentication and Restart Lifecycle host Proposed
005 Deployment Architecture — Plugins and Database host Proposed
006 SDLC Document Structure host Accepted
007 Agent Skills Location host Accepted
010 Plugin Composability and Independence common Accepted
011 Portal Plugin Configuration Namespace common Accepted
012 Plugin Factory Preview Labeling common Accepted
013 Preview Plugin Enablement Defaults common Accepted
015 Catalog-First Placement and Host Surface Slots common Accepted
016 Software Template vs Factory Backstage Plugin common Accepted
017 Preview Chip Placement common Accepted
018 Factory Shared UI Primitives common Accepted
019 Factory Capability Delivery Lifecycle common Accepted
020 Multi-Org Namespace Isolation common Accepted
021 Template Type Taxonomy host Accepted
022 Multi-Org RBAC and Auth common Accepted
023 Per-Template RBAC Visibility Filtering host Accepted
024 Sync UX — Backstage Signals host Accepted
026 Multi-Org Architecture Overview common Accepted
027 Catalog Entity Naming and Namespaces common Accepted
028 Out-of-Tree Plugin Obligations third-party Accepted

Some common ADRs still mention packages/app or in-tree paths. Those location sentences are host details. The rules (zero footprint, config namespace, no cross-plugin implementation deps) still bind out-of-tree plugins. See ADR-028.