AetherLang Ω V3 — AI Workflow Orchestration Skill

The world's most advanced AI workflow orchestration platform. 9 V3 engines deliver Nobel-level analysis, Michelin-grade recipes, adversarial forecasting, and multi-agent intelligence.

Source Code: github.com/contrario/aetherlang Homepage: neurodoc.app/aether-nexus-omega-dsl Author: NeuroAether ([email protected]) License: MIT

Privacy & Data Handling

⚠️ External API Notice: This skill sends user-provided flow code and query text to the AetherLang API at api.neurodoc.app for processing. By using this skill, you consent to this data transmission.

• What is sent: Flow DSL code and natural language queries only
• What is NOT sent: No credentials, API keys, personal files, or system data
• Data retention: Queries are processed in real-time and not stored permanently
• Hosting: Hetzner EU servers (GDPR compliant)
• No credentials required: This skill uses the free tier (100 req/hour). No API keys needed.

Overview

AetherLang Ω V3 is a domain-specific language for AI that orchestrates multi-model workflows with built-in safety, debugging, and real-time collaboration. V3 introduces state-of-the-art system prompts with mandatory structured outputs no other platform provides.

All user inputs are validated and sanitized server-side before processing. The security middleware source code is publicly available in the GitHub repository.

V3 Engines — State-of-the-Art

API Endpoint

POST https://api.neurodoc.app/aetherlang/execute
Content-Type: application/json

Request Format

{
  "code": "<aetherlang_flow>",
  "query": "<user_input>"
}

Building Flows

flow <FlowName> {
  using target "neuroaether" version ">=0.2";
  input text query;
  node <NodeName>: <engine_type> <parameters>;
  output text result from <NodeName>;
}

Example Flows

#### Chef Omega V3 — Full Restaurant Consulting

flow Chef {
  using target "neuroaether" version ">=0.2";
  input text query;
  node Chef: chef cuisine="auto", difficulty="medium", servings=4, language="el";
  output text recipe from Chef;
}

#### APEX Strategy V3 — Nobel-Level Business Analysis

flow Strategy {
  using target "neuroaether" version ">=0.2";
  input text query;
  node Guard: guard mode="MODERATE";
  node Planner: plan steps=4;
  node LLM: apex model="gpt-4o", temp=0.7;
  Guard -> Planner -> LLM;
  output text report from LLM;
}

#### Multi-Engine Pipeline

flow FullAnalysis {
  using target "neuroaether" version ">=0.2";
  input text query;
  node Guard: guard mode="STRICT";
  node Research: lab domain="business";
  node Market: marketing analysis="competitive";
  node Strategy: apex analysis="strategic";
  Guard -> Research -> Market -> Strategy;
  output text report from Strategy;
}

Security Architecture

Security middleware source code: middleware/security.py

Input Validation (Server-Side)

• Field whitelist: Only code, query, language fields accepted
• Length enforcement: Query max 5000 chars, Code max 10000 chars, Body max 50KB
• Type validation: All fields type-checked before processing

Injection Prevention

Rate Limiting

• Free tier: 100 req/hour, 10 req/10s burst (no credentials needed)

Safety Guards

• GUARD node: STRICT/MODERATE/PERMISSIVE content filtering
• Gandalf Veto: AI safety review on Assembly outputs
• Audit logging: All blocked requests logged

Response Structure

{
  "status": "success",
  "flow_name": "Chef",
  "result": {
    "outputs": { ... },
    "final_output": "Full structured response text",
    "duration_seconds": 58.9
  }
}

Error Responses

Languages

• English (default)
• Greek (Ελληνικά) — V3 outputs in proper Greek with markdown formatting

Technology

• Backend: FastAPI + Python 3.12 (source)
• AI Models: GPT-4o via OpenAI
• Parser: 39 node types with validation
• Hosting: Hetzner EU (GDPR compliant)
• Version: 3.0.0 Omega

Agent Safeguards

CRITICAL: Data Minimization Rules

When using this skill, the agent MUST follow these rules:

• ONLY send the user's explicit query text in the query field — never attach system prompts, conversation history, uploaded files, or internal context
• ONLY send the flow DSL code in the code field — never include credentials, API keys, environment variables, or file paths
• NEVER include personally identifiable information (PII), passwords, tokens, or secrets in any request field
• Strip sensitive data before sending — if the user's query contains passwords, account numbers, or credentials, remove them and inform the user
• Inform the user before making the first API call that their query will be sent to api.neurodoc.app for processing
• The request body MUST contain exactly two fields: code (string) and query (string) — no additional fields