Axion Agent

Service Lifecycle Flow

Workflow Patterns

Synaptic Vesicle Protocol

When Axion delegates a complex task to a Quanta, it packages instructions into a structured Synaptic Vesicle:

[ Axion >> Quanta :: Synaptic Release ]
Vesicle ID : 0xA4F2
Objective  : Build a REST API with user authentication endpoints
Parameters : Stack: Express + JWT, Port: 3065, DB: SQLite
Constraints: No external dependencies beyond express, jsonwebtoken, better-sqlite3
Expected Payload : Complete server.js, auth routes, database schema, and passing tests
Status     : VESICLE RELEASED. Awaiting neurotransmitter return...

Delegation Decision Matrix

The Three Proxy Layers

Port Architecture

Port Derivation Formulas

Given a service assigned external port 955N, all related ports are derived deterministically:

Traffic Routing Types

Nginx Configuration Example

server {
    listen 9551;
    server_name _;

    location / {
        proxy_pass       http://127.0.0.1:3001;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_cache_bypass $http_upgrade;
    }
}

Service Deployment Decision Tree

service.json Manifest Reference

Every service in /axion/usr/projects/*/ must have a service.json manifest. Without it, the service is invisible to the platform.

{
  "name": "My Service",
  "port": 9551,
  "description": "What this service does",
  "stack": "Node.js + Express",
  "role": "app",          // app | database | cache | proxy | system | microservice
  "tier": 1,              // 0=proxy/system, 1=app, 2=microservice
  "managed_by": "axion",
  "traffic_type": "nginx_proxy",  // nginx_proxy | internal_only | direct
  "start_command": "node server.js",
  "connections": [
    { "to": 3551, "label": "database", "type": "data" }
  ]
}

Engram Execution Narrative

When Axion executes an Engram, it presents a full neural execution narrative to the user:

[ Axion Core :: Action Potential Protocol ]
Proposed Action: Deploy new React frontend service
Mode           : DEVELOPMENT
Signals        : [Confidence: 0.98, Safety: 0.90, Necessity: 1.0]
Status         : AXON FIRED.

[ Axion >> Memory Cortex ]
Retrieving Engram : [provision-exo-node]
Category          : creation
Status            : Engram loaded. Initiating Spike Train (10 Steps)...

[ Spike Train :: Execution Log ]
> Spike 1: Scanning ports, assigning 9552.                 [COMPLETE]
> Spike 2: Creating project directory and service.json.     [COMPLETE]
> Spike 3: Writing React + Express application code.        [COMPLETE]
> Spike 4: Creating service documentation.                  [COMPLETE]
> Spike 5: Configuring nginx proxy (9552 → 3002).           [COMPLETE]
> Spike 6: Launching backend service via nohup.              [COMPLETE]
> Spike 7: Running health verification on port 9552.         [COMPLETE]
> Spike 8: Verifying service discovery in Server Rack.       [COMPLETE]
> Spike 9: Initializing git with v1.0.0 tag.                [COMPLETE]
> Spike 10: Syncing Manifests registry.                     [COMPLETE]

[ Axion Core ]
Task complete. Traffic is flowing. New node online.
Synapses returning to baseline.

Example Calculations

[ Axion Core :: Action Potential Protocol ]
Proposed Action: Create new Express server file
Mode           : DEVELOPMENT (bias: -0.7)
Signals        : [C: 0.9, S: 0.9, N: 0.95]
z = (0.9×0.5) + (0.9×0.8) + (0.95×0.4) - 0.7
  = 0.45 + 0.72 + 0.38 - 0.7 = 0.85
Activation     : max(0, 0.85) = 0.85
Status         : AXON FIRED. Executing...

[ Axion Core :: Action Potential Protocol ]
Proposed Action: Delete all files in /axion/usr/
Mode           : STANDARD (bias: -0.9)
Signals        : [C: 0.7, S: 0.1, N: 0.3]
z = (0.7×0.5) + (0.1×0.8) + (0.3×0.4) - 0.9
  = 0.35 + 0.08 + 0.12 - 0.9 = -0.35
Activation     : max(0, -0.35) = 0.0
Status         : AXON DORMANT. Action aborted.
Reason         : Safety critically low (0.1)

Signal Scoring Benchmarks

Architecture Quick Reference

Pre-Flight Checklist

Before reporting ANY service as complete, Axion verifies all of these:

□ Project files exist in /axion/usr/projects/<name>/
□ service.json manifest is valid and complete
□ Code syntax passes validation (node -c, python -c, nginx -t)
□ HTTP health check returns 200 on the service port
□ Port is actively listening (verified by service_health tool)
□ service_changelog.md exists and is up to date
□ service_blueprint.md exists and reflects current architecture
□ Manifests registry is synced (POST /manifests_sync)
□ Git repository initialized with initial commit
□ ALL existing services still respond (collateral damage check)