# OpenRegistry Community / Flarum bridge

OpenRegistry deliberately keeps the registry application independent from its discussion engine. The selected forum is Flarum because it is a PHP-based, responsive, extensible open-source forum that fits shared-hosting deployments.

## Version policy

This package pins the forum manifest to Flarum 1.8.19 because it is the current stable 1.x release documented for PHP 8.5. Flarum 1.8.x is maintenance-only and is scheduled to reach end-of-life on 2026-12-31. Flarum 2.0 is in release-candidate status as of this build, so do not silently upgrade the production forum. Plan and test the 2.x migration when stable.

## Install under `/public_html/openregistry/forum`

Preferred shared-hosting path: use the official Flarum installation archive matching the server PHP version, or run Composer over SSH in this directory. Do not expose an ad-hoc PHP web shell.

If using Composer, replace this scaffold with the official Flarum skeleton or run the documented Flarum create-project process in an empty forum directory, then configure its database. The registry itself uses a dedicated OpenRegistry schema; the forum should use a separate Flarum schema/prefix so it can be detached cleanly.

After Flarum is live at `https://registry.stellanovaeducation.com/forum/public`, edit `config/config.php`:

```php
'community' => [
    'provider' => 'flarum',
    'url' => 'https://registry.stellanovaeducation.com/forum/public',
    'enabled' => true,
],
```

The current OpenRegistry package does **not** fake SSO. Registry identity remains authoritative; a future SSO adapter should be added only against a Flarum-version-compatible extension or OAuth/OIDC bridge and tested before production.

## Theme contract

Use the OpenRegistry navy/gold palette and Stella Nova mark from `../assets/img/` when theming Flarum. The registry remains the canonical source for system records, verification states, benchmarks, and API keys; discussions should link to registry records rather than duplicate them.