IMPERIAL Execution Accelerator
Purpose: standardize and accelerate governed IMPERIAL Core execution without weakening evidence or cost controls.
Mandatory execution pipeline
- Resolve exact target and version.
- Enforce FREE_ONLY before provisioning. Reject card-required, paid-only, trial-conversion, pay-as-you-go, or automatic-billing paths.
- Install/register the capability.
- Run smoke test.
- Run functional test.
- Perform independent read-back/evidence verification.
- Classify truthfully: LIVE_VERIFIED only after functional test + read-back; otherwise INSTALLED_BLOCKED, FAILED, PENDING, or UNVERIFIED.
- Roll out only after the component-specific gate passes.
- Write action/evidence to task_journal. The IMPERIAL operating rule requires mirrored journaling on all three canonical runtime servers.
- Never expand wallet, signing, trading, spending, external-business, or security authority merely because a skill was installed.
Canonical servers for mirrored action journal
- oromaskevic23/imperial-morgan-runtime
- oromaskevic23/imperial-nca-runtime-recovery
- oromaskevic23/imperial-nca-31day-runtime
PASS/LIVE/TESTED/DEPLOYED requires machine-verifiable evidence. Registry presence, heartbeat, source fetch, or install binding alone is not functional proof.
FREE_ONLY is fail-closed. No credit card, no paid API, no trial that converts to paid, no automatic billing, and no silent paid fallback.
Use runtime.ts for provider admission, evidence classification, deterministic action-envelope hashing, local task-journal writes, and self-test.