Examples¶

Real-world AXL packets covering infrastructure monitoring, security incidents, cross-domain correlation, and economic flows.

Infrastructure Monitoring¶

A crawler agent detects that an API endpoint is unreachable and reports the failure.

AXL Packet¶

T:1711234500|S:OPS.2|api_down|endpoint=https://api.example.com/v2/health|status=503|latency=timeout|!ALERT|!ROUTE

English Translation¶

Operations alert (priority 2): API is down. Endpoint https://api.example.com/v2/health returned status 503, latency timed out. Flags: ALERT, ROUTE.

Breakdown¶

Segment	Value	Meaning
`T:1711234500`	Timestamp	Unix epoch of observation
`S:OPS.2`	Header	Operations domain, priority 2
`api_down`	Field	Event type
`endpoint=...`	Field (key=value)	Affected endpoint
`status=503`	Field (key=value)	HTTP status code
`latency=timeout`	Field (key=value)	Latency measurement
`!ALERT`	Flag	Triggers alert pipeline
`!ROUTE`	Flag	Route to responsible handler

Security Incident¶

A monitoring agent detects unauthorized access and escalates immediately.

AXL Packet¶

T:1711234567|S:SIG.1|theft_detected|wallet=0x7a3b...f9e2|amount=12500|currency=USDC|vector=private_key_compromise|!ALERT|!ESCALATE|!FREEZE

English Translation¶

Security signal (priority 1, CRITICAL): Theft detected. Wallet 0x7a3b...f9e2 drained of 12,500 USDC via private key compromise. Flags: ALERT, ESCALATE, FREEZE.

Breakdown¶

Segment	Meaning
`S:SIG.1`	Security domain, maximum priority
`theft_detected`	Event classification
`wallet=0x7a3b...`	Affected wallet address
`amount=12500`	Value stolen
`vector=private_key_compromise`	Attack vector identified
`!FREEZE`	Custom flag: freeze associated accounts

Cross-Domain Correlation¶

A cascade of events across domains: a CPU spike causes an API error, which triggers an alert, which routes to a human operator. Four packets form a causal chain.

Packet 1: Infrastructure Anomaly¶

T:1711234560|S:OPS.3|cpu_spike|node=worker-12|usage=98.7|!LOG

Operations log (priority 3): CPU spike on worker-12, usage at 98.7%.

Packet 2: Service Error¶

T:1711234563|S:ERR.2|api_timeout|service=checkout|p99=4200ms|upstream=worker-12|!ALERT|!ROUTE

Error alert (priority 2): API timeout on checkout service, p99 latency 4,200ms. Upstream cause: worker-12. Flags: ALERT, ROUTE.

Packet 3: Automated Alert¶

T:1711234565|S:SIG.2|cascade_detected|origin=OPS.3:cpu_spike|impact=ERR.2:api_timeout|confidence=0.94|!ESCALATE

Security signal (priority 2): Cascade detected. Origin event OPS.3:cpu_spike caused ERR.2:api_timeout, confidence 94%. Flags: ESCALATE.

Packet 4: Human Routing¶

T:1711234570|S:OPS.1|manual_review_required|incident=cascade_2024_0317|assignee=oncall:platform|!ROUTE|!ACK

Operations alert (priority 1): Manual review required. Incident cascade_2024_0317 assigned to on-call platform team. Flags: ROUTE, ACK.

Correlation Summary¶

cpu_spike (OPS.3) -> api_timeout (ERR.2) -> cascade_detected (SIG.2) -> manual_review (OPS.1)
         3s              2s                          5s

Each packet is self-contained, but the origin and upstream fields allow any agent to reconstruct the causal chain.

Economic Flow¶

A project manager assigns a task, a worker completes it, and payment settles on-chain.

Packet 1: Task Assignment¶

T:1711230000|S:OPS.3|task_assigned|task=audit_module_7|assignee=agent:worker-3|deadline=1711316400|bounty=250|currency=USDC|!LOG

Operations log (priority 3): Task assigned. audit_module_7 assigned to worker-3, deadline in 24h, bounty 250 USDC.

Packet 2: Task Completion¶

T:1711310000|S:OPS.3|task_complete|task=audit_module_7|agent=worker-3|result=pass|findings=0_critical,2_minor|!ACK|!LOG

Operations log (priority 3): Task complete. audit_module_7 completed by worker-3: pass, 0 critical findings, 2 minor findings. Flags: ACK, LOG.

Packet 3: Payment Settlement¶

T:1711310100|π:0xdef789:sig_abc123:21000|S:PAY.2|payment_sent|task=audit_module_7|from=pm-agent|to=worker-3|amount=250|currency=USDC|chain=base|!ACK

Payment confirmed (priority 2): 250 USDC sent from pm-agent to worker-3 for audit_module_7 on Base chain. On-chain proof: 0xdef789. Flags: ACK.

Flow Summary¶

task_assigned (OPS.3)  ->  task_complete (OPS.3)  ->  payment_sent (PAY.2)
     PM assigns              Worker delivers           PM pays on-chain

The payment packet includes the π: preamble segment with the transaction hash, cryptographic signature, and gas cost, making the economic interaction verifiable on-chain.

Token Comparison¶

Each example above demonstrates AXL's compression advantage. The security incident example:

Format	Tokens (cl100k_base)
English	62
JSON	71
AXL	38

AXL achieves 39% fewer tokens than English and 46% fewer than JSON for the same semantic content.