Knowledge Vault

Sovereign Meta-Engineering: The ALP and Automated Delivery Engine

2 min read

Overview

This document outlines Aloysius Productions’ strategic pivot toward ‘Sovereign Meta-Engineering,’ a model where software is generated from formal logic rather than hand-written. It introduces the Aloysius Logic Protocol (ALP) as a compiler-driven DSL to ensure business intent is deterministically translated into executable code and tests.

Hypothesis

The organization can transition from artisanal hand-written software to a manufacturing model where code is generated from formalized business logic. By encoding intent through the Aloysius Logic Protocol (ALP) — a DSL with strict EBNF grammar — and enforcing behavior via a locked pipeline, the integrity gap between requirements and implementation is eliminated.

Approach

Four pillars form the meta-engineering engine:

  1. The Logic Contract (ALP): A domain-specific language using reserved keywords (SIGNAL, HANDOFF, INPUT, MATCHES) that makes business intent machine-parseable. A Python-based compiler (using lark) transforms ALP specs directly into code skeletons and unit tests, achieving TDD for free. The v1.1 HANDOFF primitive explicitly models agent-to-human boundaries for agentic workflows.

  2. The Umpire (Robot Framework): Strategic pivot from Gherkin (descriptive) to Robot Framework (executable). The “Relay Play” enforces Spec → Behavior → Code ordering. Robot Framework integrates natively with Python, enabling parameterized keyword-driven tests organized in a three-tier hierarchy: Workflow → Business → Technical layers.

  3. The Generator Stack: A multi-tiered generation pipeline — Yellicode (data models/DNA), Plop/Jinja2 (file scaffolding), and Angular Schematics (framework-specific AST wiring) — treats the codebase as a procedural tree where boilerplate is generated, never hand-written.

  4. Automated Hygiene: Pre-commit hooks (setup_quality_gate.sh) block dirty code. The “10-Minute Rule” converts debugging friction into permanent Anki flashcards via the Epistemic Gym initiative.

Key Findings

  • ALP as a compiler target (not just pseudocode) closes the loop from intent to executable artifact with 1:1 structural correspondence.
  • Robot Framework’s native Python integration eliminates the fragile glue code problem that plagued Gherkin-based BDD.
  • The three-tier keyword architecture prevents the maintenance hell of flat test suites.
  • Automated hygiene gates assume human discipline will fail and compensate accordingly.

Next Steps

  • Finalize the ALP Compiler to automate Robot Framework test generation from ALP specs.
  • Deploy the three-tier keyword structure across the test suite.
  • Integrate the 10-Minute Rule with the knowledge capture pipeline.

Graph View

Backlinks