RcmEmailAutomation / mu-plugins /sa-orch-spec-root.php
NujacsaintS's picture
Pre-stage mu-plugin for spec_root override; ONBOARDING references file not snippet
93528c6
Raw
History Blame Contribute Delete
1.68 kB
<?php
/**
* SA-Orchestration β€” Asterion spec_root override
*
* Type: mu-plugin (must-use plugin) β€” auto-loaded by WordPress;
* no activation needed; survives plugin deactivation.
*
* Purpose: Point the SA-Orchestration Asterion canonical corpus root at
* the deployed `wp-content/sa-asterion/` directory.
*
* Why it exists: The SA-Orchestration plugin's `SA_Orch_Asterion_Explorer::DEFAULT_SPEC_ROOT`
* is hardcoded to a path that exists on the source-author's machine
* (`F:/SleeperAgents/SA-orchestration/Archvie/sa-core/docs/specs`).
* On every other WordPress install β€” WPE, client deployments, leaf
* installs β€” that path doesn't exist. Without this filter, every
* Asterion query returns
* "no canonical reference found in the spec corpus (corpus root unreachable)".
*
* Deploy path: Copy this file to `<wp-install>/wp-content/mu-plugins/sa-orch-spec-root.php`.
* No `mu-plugins/` directory? Create it. WordPress auto-discovers it.
*
* Companion: The Asterion corpus directory itself must exist at
* `<wp-install>/wp-content/sa-asterion/` and contain the canonical
* spec files (`01-ontology.md`, `02-invariants.md`, `concepts/`, etc.).
* Source of those files: `F:\SleeperAgents\SA-orchestration\asterion\`
* (committed at v1.1, commit 848ee70).
*
* One file per WP install. Idempotent. No DB writes. No state.
*/
defined( 'ABSPATH' ) || exit;
add_filter( 'sa_orch_asterion_spec_root', function () {
return WP_CONTENT_DIR . '/sa-asterion';
}, 5 );