For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt, and this page is available as Markdown at /compatibility/index.md.

Themelio compatibility and parallel operation

The retained application lives under compat/themelio and runs as themelio-compat. The new service scaffold lives under services/themelio. Both can appear in the same environment. Their deployment names and responsibilities must remain explicit in operational instructions.

The retained web footer and sidebar open the current documentation through /documentation. The server resolves its destination from the configured THEMELIO_URL at request time: local development uses https://docs.localtest.me/, and staging uses https://docs.staging.pharosfactory.ai/. The Contribute link opens /contributing/ on the same documentation host.

Set the runtime THEMELIO_DOCUMENTATION_URL to an HTTP(S) base URL for other installations or to override these defaults. A base path is supported. An unrecognised environment without an explicit URL returns an unavailable response. These links use runtime configuration and require no environment-specific image build.

Shared infrastructure and separate authority

The applications can share AAI, GitLab and Waldur. Each operation needs one active writer and an explicit handover when ownership changes. Their databases and runtime credentials follow their own documented boundaries. Read the compatibility decision, its implementation guide and the current architecture together.

CapabilityCurrent documentation ownerQualification to check
Retained Themelio web and actorsCompatibility implementation guideEnabled routes, provider credentials and environment restrictions
Canonical Party authenticationBeto Party GovernanceEnrolled authentication edge, verified bindings and real AAI qualification
Source-managed Project and membershipBeto ProjectSource enrolment, freshness, access checks and published contract version
New Themelio serviceService scaffoldExplicit context registration before claiming a business capability
Workload executionOwning Metallo contextConnected owner ports, paused processes and native runtime qualification

The Party and Project READMEs distinguish the current slices from their planned evolution. This table identifies where to look; an environment's rollout and tests establish what is running.

Retained documentation

The original pages retain their routes and Git history. Each carries a compatibility notice. Their historical requirements, examples and deployment assumptions need review before use in a new platform feature.

The current decision catalogue remains the authority for platform decisions. Historical copies preserve the original record; their presence does not accept an old proposal for the new architecture.

Handover checklist

For each capability, record its current writer, replacement owner, transferred state and identifier bindings, enrolment conditions, recovery behaviour and tested cutover/rollback procedure. Qualify the replacement with its real providers before enabling writes. Update the owning context and operational guide at the same time.

Page source

Source snapshot ยท Revision f928834c8.