Profile Library and profile sets

Profile Library and profile sets

The Profile Library in Settings → Profiles is Holaryn's local catalog of optional,
versioned specialist profiles. A fresh installation starts with Base configuration only. You
choose which specialists to install; catalog entries do not appear in chat, workflow routing, or
other profile selectors until they are installed and enabled.

Profile Library entries are not provider accounts and do not contain a model. They shape how a
configured model is used. You still need an eligible configured model and any required external
accounts. Installing a profile never grants credentials, network access, production authority, or
an approval-policy exception.

Four states that are intentionally separate

• Available means the profile is described in the built-in local catalog.
• Installed means an exact immutable profile version and digest are recorded locally.
• Enabled means that installed version may appear in selectors and satisfy new specialist
  workflow routes. Disable hides it without deleting retained version evidence.
• Active means a chat or run actually selected the profile. Installation and enablement never
  change the active chat or the default profile.

The default profile for new chats is a separate setting. Existing chats apply a selected profile
at the next message. See Config profiles for switching behavior.

Install an individual profile or a set

1. Open Settings → Profiles → Profile library.
2. Search or filter by All available, Installed, or Profile sets.
3. Choose Install… for one profile, or Install set… for a coordinated set.
4. Review the exact profiles, workflows, declared capabilities, dependencies, and safety notes.
5. Choose Confirm change.

Declared capabilities are review information, not grants. At runtime, the installed profile is
still narrowed by organization policy, the current autonomy posture, account scope, available
tools, model eligibility, and ordinary approvals.

Profiles installed individually and through a set use ownership tracking. If a profile is both a
direct install and a member of an installed set, removing the set preserves the direct install. A
profile owned only by a set must be removed with the set or disabled individually. Uninstalling
prevents new selection while retaining immutable definitions and prior run evidence.

Accessibility set

The optional Accessibility set installs four profiles that can work together:

• Accessibility Auditor
• Accessibility Website Remediator
• Accessibility Document Remediator
• Accessibility Independent Verifier

It also installs the exact-profile-bound accessibility-audit-remediation workflow. Automated
results do not claim WCAG, legal, or manual screen-reader conformance; manual testing and known
limitations remain explicit.

Software Development set

The optional Software Development set installs:

• Software Planner — repository analysis, bounded plans, risks, acceptance criteria, tests,
  and rollback without editing files.
• Software Implementer — focused changes in the assigned workspace; it cannot approve or
  integrate its own work.
• Test Engineer — regression, edge-case, and failure-mode tests with honest unverified states.
• Code Reviewer — independent, read-only review with precise findings.
• Release Validator — revision-bound validation evidence.
• DevOps Engineer — CI/CD, packaging, infrastructure-as-code, health, observability, and
  rollback planning under explicit authorization.

The set's software-development workflow proceeds through plan review, implementation, testing,
independent review, release validation, and integration review. The DevOps stage runs only when it
is explicitly requested. It prepares a staged release plan but does not deploy by itself. A
separate critical deployment approval names the target and required authority; any later tools or
connectors still go through their normal account, policy, and approval gates.

You may install only DevOps Engineer, or any other member, when you do not need the whole set.
The coordinated workflow becomes available for new runs only when every set member is installed
and enabled, so its exact role bindings cannot silently fall back to another profile.

Updates, migration, and recovery

An update preview shows changed exact versions and newly declared capabilities. Updating installs a
new immutable version; existing runs retain their pinned references. A stale preview is rejected if
library state changes before confirmation.

Upgrades from releases that automatically installed the Accessibility profiles are migrated
non-destructively: Holaryn recognizes the existing curated exact versions, records the Accessibility
set as installed, and preserves previous definitions and workflow evidence. A partial legacy set is
recorded as individual installs rather than inventing missing members.

Library state is local in <state dir>/profile-library.json; immutable definitions remain in
<state dir>/agent-profiles.json, and workflows remain in the workflow store. If the installation
ledger is malformed, Holaryn fails closed instead of exposing every catalog profile. Restore the
file from a trusted backup or move the malformed file aside only after reviewing which profiles
should be installed again.