Open systems · verified work

Build openly. Prove the work.

ALOS Public is the clean public surface for projects, engineering evidence, agent E2E proof, webhooks and system architecture. Private credentials, internal state and privileged controls stay isolated.

Public proofSanitized evidence only
Private controlSeparated and fail-closed
5Public project lanes
E2EAgent + integration evidence
LiveHealth and public AI surfaces
GatedEvidence before acceptance
Watch ALOS Work

Public proof, checked live.

Checking…
RequestBounded objective
GovernancePolicy boundary
OrchestrationRoute the work
ExecutionTool / compute lane
VerificationCheck outcome
EvidenceExpose proof
Verifying /health and /e2e.jsonOpen live proof panel →
Evidence & proofs

Proof surfaces, not marketing claims.

Each public proof surface is deliberately sanitized. It can show system structure and verification targets without exposing private data or secrets.

01

Public edge health

Confirms that the ALOS public Worker is reachable at the edge.

Open /health →
02

Proof manifest

Machine-readable index of public/private isolation and evidence controls.

Open /proof.json →
03

Agents + E2E

Sanitized contract index for agent, integration, Kaggle and result-consumer proof.

Open /e2e.json →
04

Webhook architecture

Public map of webhook/callback responsibilities with secrets and private targets removed.

Open /webhooks.json →
Public/private route isolationImplementedPublic Worker refuses private operational surfaces and does not expose private state bindings.
Source-aware executionContractedCloudflare-to-compute work is designed around source identity and bounded execution receipts.
Agent and integration E2EIndexedThe public proof manifest points to sanitized E2E contract families without exposing credentials.
Evidence acceptanceGatedReturned results are treated as evidence-bearing outputs rather than self-reported completion.
Agents & E2E

What the public proof can show.

ALOS Public exposes a compact evidence index, while actual agent controls and private execution state remain off the public surface.

E2E proof families

Sanitized references to the contracts that define the end-to-end path.

Integration sweepIndexed
Master E2E runnerIndexed
Kaggle CPU/GPU laneIndexed
Cloudflare result consumerIndexed
Pigeon public runtimeLive surface
Read E2E manifest

Webhook and callback map

Responsibilities are public; destinations, tokens, signatures and provider secrets are not.

Provider result callbackPrivate target
Compute completion receiptEvidence path
Agent execution receiptAudit path
External relay boundaryIsolated
Verification gateFail-closed
Read webhook manifest
Architecture

Intent to evidence, end to end.

The public diagram shows the operating pattern without disclosing privileged infrastructure or credentials.

1IntentProject objective and bounded scope.
2GovernancePolicy, approval and safety checks.
3QueueControlled work packet and routing.
4ExecutionBrowser, CPU, GPU or model lane.
5EvidenceReceipts, artifacts and acceptance checks.