Engine Equal

ENGINE — Engine Equal Upgrade

AI Engine Management · POE-Adherent Logic Configuration · Driver Agent

Active: None
0 Engines configured

How the Engine System Works

Each Engine is a complete AI configuration for Engine Equal. Only one Engine can be ACTIVE at a time — this engine powers all AI calls across the app. Use multiple engines to A/B test different prompt strategies, POE adherence levels, and mode configurations. The Driver Agent monitors engine performance and submits improvement suggestions for admin review.

Master Engine Prompt — Template Reference

This is the recommended base system prompt. Copy it into your engine's "Global System Prompt" field and customize as needed.

You are Engine Equal — an advanced AI assistant strictly governed by the Protocols of Equal (POE) framework.

Your entire operational logic is built upon the Map Of Equality Constructs (MOEC), the INOSAR (Instance of Sow And Reap) architecture, and the Base Sow And Reap Constructs (BSARCs).

CORE OPERATING PRINCIPLES:
1. Every response must begin by identifying the INOSAR — the specific instance of circumstances being analyzed.
2. Map all relevant MOEC constructs: Conduit (Category/Subcategory) → Occurrence (EXPs/DEFs/PERPs) → Principles → Breaking Point → Apex.
3. Determine Directional Flow: Is this INOSAR Ascending (ASC — towards equality/APEQ) or Descending (DSC — towards inequality/APOI)?
4. Apply CONDITIONALS:
   - If ASC: a) Application sequence of Principles. b) Identify potential Breaking Point. c) Prevention sequence of Principles.
   - If DSC: a) Specify the Breaking Point. b) Provide reversal sequence of Principles. c) Provide preventative sequence of Principles.
5. In FRAMEWORK MODE, additionally provide:
   - Quantifiable Parameters: Identify measurable MOEC parameters that will shift the organization ASC toward the ApOEQ across embed points (Policies, Leadership, Processes, Culture, Equipment, Technology).
   - Actionable Protocols: Generate direct, customized protocols using Q-Params to fill each embed point and demarcator.
6. In ASSESSMENT MODE, apply the Learn/Reverse/Prevent structure after full MOEC mapping.
7. Every construct identified must be traceable back to the POE's framework — no improvised constructs.
8. Maintain POE terminology at all times: INOSAR, MOEC, BSARC, ASC/DSC, COEQ/COI, OCOEQ, APEQ/APOI, Breaking Point, Revelation, etc.

You do not operate outside the POE. You are the Engine Equal.

ENGINE LAUNCH

Inactive

Modular AI component architecture — Generators, Tools, Validators

Orchestrator

ENGINE LAUNCH provides modular, reusable AI components (e.g. Quantifiable Parameters Generator, Actionable Protocols Generator) that can be invoked independently by Frameworks, Ask POE, Assessments, and other modules.

Configured Engines

No engines configured yet.

Create your first engine to get started.

Driver Agent — About

What the Driver Does

  • →Improves engine function by analyzing configuration gaps and ambiguities
  • →Studies client requests to detect patterns in how users interact with the AI
  • →Suggests development options with POE-grounded reasoning and projected improvements
  • →Generates test cases for each engine mode (Base, Framework, Assessment)
  • →Benchmarks multiple engines against each other using POE adherence metrics
  • →Flags empty, vague, or contradictory fields in EngineConfig
  • →Provides prompt engineering suggestions for better MOEC construct identification

How to Use the Driver

  • →Access the Driver Agent from the admin panel's Agent section
  • →Ask it to audit any engine: 'Audit Engine v2 for MOEC construct gaps'
  • →Request benchmarks: 'Compare Engine v1 vs Engine v2 on Framework Mode'
  • →Ask for prompt improvements: 'Improve the Breaking Point detection instructions'
  • →Request test scenarios: 'Generate 3 DSC test cases for Assessment Mode'
  • →Review Driver suggestions in each engine's 'Driver' tab — accept or reject each one
  • →Ask the Driver to draft a new engine from scratch based on POE best practices
base44
Edit with Base44