Phase 4 · Node Layer 21 · Systems & Proof

Every claim backed by evidence.
Every endpoint, every trace, every event — live.

Integration claims without evidence are marketing. This page turns every integration claim into visible proof: real endpoints with real request/response shapes, real traces with full causal chains, real reconciliation events with timestamps. The trace explorer below shows a single order's complete path from intake to retention scheduling — seven hops, every one timestamped, every one preserved.

Real endpoints Full causal traces Zero drift OpenTelemetry-compatible Append-only audit log
TRC
Traces Retained
90 days
Full causal chains preserved
LAT
Endpoint Latency p95
1.42s
Across all instrumented spans
DRF
Reconciliation Drift
0
Continuous lockstep
COV
Contract Coverage
100%
Every endpoint documented
The Trace Explorer

One order. Seven hops. Every one preserved.

Click any span in the tree to inspect it. Every hop carries the same trace ID. Every span is preserved for 90 days. The trace is OpenTelemetry-compatible and externally consumable at activation.

Trace Explorer · Order PM-847291 · Live
Trace ID · 4a8f2c1e9d3b7a6f5e4d3c2b1a0f9e8d 7 spans
IN layer.intake Order received at edge +0.000s
ADP layer.adapter.translate Payload → BAPI mapping +0.086s
SAP layer.sap.bapi_write BAPI_SALESORDER_CREATEFROMDAT2 +0.982s
VAL layer.response.validate Schema + ETag captured +1.281s
REC layer.reconcile.compare Drift check against SAP +1.412s
ACK layer.reconcile.ack Order closed · event fired +1.420s
RET layer.retention.schedule AutoShip renewal queued +1.514s

layer.intake

Order received at the edge. Initial validation passed. Order ID assigned.

OK
Span ID
span-a41c
Duration
86ms
Service
layer-edge
Kind
SERVER
Payload
{
  "order_id": "PM-847291",
  "customer_id": "C-48210",
  "line_items": [
    { "sku": "NEXGARD-3MO-60-121", "qty": 2 }
  ],
  "autoShip": true,
  "total": 118.39
}
The Endpoints

Six endpoints. Every one documented.

Every endpoint on this page is documented with its method, path, request shape, and response shape. Every one is externally consumable at activation. Nothing is proprietary. Nothing is hidden.

POST Verified

/layer/v1/orders

Direct order intake. Standard JSON. Idempotency-Key required. Authenticated via OAuth 2.0. Returns 201 Created with the order ID.

GET Verified

/layer/v1/orders/{id}/status

Read current order state. Returns the full state machine state including which gates have passed and current stage. Cached at the edge.

SSE Verified

/layer/v1/events/stream

Real-time server-sent event stream. Every order event, signal update, and reconciliation result flows through here. Consumed by dashboards, Pro-Panel, and external monitoring.

BAPI Verified

BAPI_SALESORDER_CREATEFROMDAT2

Standard SAP BAPI for sales order creation. Idempotency-Key prevents double-writes. Every write reflected in the layer event log within milliseconds.

OData Verified

/sap/odata/v4/Orders({id})

Standard OData v4 read path. ETag-based optimistic concurrency. Used by reconciliation to detect state divergence.

WEBHOOK Verified

reconcile.drift.detected

Webhook fired when reconciliation detects divergence. Signature-verified payload. Retries on non-2xx with exponential backoff.

Live Stream

Integration proof · live

The proof stream is the raw output of the integration surface. Every OData read, every BAPI write, every IDoc emission, every reconciliation event. Live, timestamped, preserved.

Integration Proof Stream · Live 12 events
16:48:31.042 TRACE Trace 4a8f2c1e · span layer.intake · 86ms
16:48:31.128 TRACE Span layer.adapter.translate · idempotency_key set
16:48:32.011 BAPI BAPI_SALESORDER_CREATEFROMDAT2 · 201 Created
16:48:32.298 TRACE Span layer.response.validate · schema OK · ETag captured
16:48:32.402 ODATA GET /sap/odata/v4/Orders('PM-847291')/Status · 200 OK
16:48:32.514 RECONCILE Drift check · 0 divergence · lockstep maintained
16:48:32.614 IDOC IDoc ORDRSP fired · order.placed · ack received
16:48:33.042 TRACE Span layer.retention.schedule · order closed · total 1.42s
16:49:04.417 TRACE New trace 8b2f14e7 · span layer.intake · order PM-847292
16:49:05.108 BAPI BAPI_SALESORDER_CREATEFROMDAT2 · 201 Created
16:50:03.211 ODATA Master data read · supplier lookup complete
16:51:47.445 RECONCILE Hourly job Z_RECONCILE_LAYER_ORDERS · 0 divergences
Metrics

Proof metrics. Continuous.

Four primary proof metrics: traces retained, endpoint latency p95, reconciliation drift, and contract coverage. All continuously measured. Click any tile for detail.

Traces Retained
90 days
Full causal chains preserved
Endpoint Latency p95
1.42s
Across all instrumented spans
Reconciliation Drift
0
Continuous lockstep
Contract Coverage
100%
Every endpoint documented
Questions

Integration proof, answered.

The integration proof surface shows every endpoint, every trace, and every reconciliation event the node produces in real operation. It is the working evidence behind the integration claims made on the integration node. Nothing here is marketing — everything is a working demonstration.

The endpoints and interfaces shown are the standard endpoints the node exposes. The traces shown represent the shape and cadence of real operation. The live demo state on this page is a working simulation running on the same protocol and contract structure the production node uses. Full API access is granted at activation.

Live endpoint access requires activation. The demonstration endpoints are shown here for architectural review. Full API access is granted at activation, along with credentials and documentation. Activation includes integration support for your first three connections.

A trace shows the full causal chain of a single order from intake to reconciliation ack. Every hop is timestamped, every system is named, and every span is preserved. Traces are OpenTelemetry-compatible — any OTLP backend can consume them. The trace explorer above shows seven hops for a single order.

Every event is logged to an append-only log that is externally consumable via standard observability interfaces. Full audit access is granted at activation. Every event includes trace ID, request ID, timestamp, and the systems notified.

The proof is on the page.

Seven spans per trace. Six endpoints verified. Zero unverified integration claims. Now the security page — the final Systems & Proof layer.