Aethel Node // Workbench
Live middleware: POST /api/v1/telemetry with predicted and observed. Non-converged runs return review_flag: "DRIFT_EXCEEDED". Optional auto_proof stores the result.
Routes are force-dynamic. Suspense boundary is in the workbench layout.
Production persistence
Active. Experience records are append-only and integrity-checked: each write stores a sha256 of the record, and every read recomputes it and rejects a mismatch. Records persist across restarts on the local file store; on Vercel they live in /tmp and do not outlast the instance unless AETHEL_HF_MEMORY_ROOT points at durable storage.
Deterministic proof
Active. With an integer seed, /api/v1/telemetry runs 8 seeded drift transformations and checks two expected relations (anchor held, Φ stable within 0.05). The same seed and inputs reproduce the same PASS or FAIL verdict. No seed or non-evaluable inputs return INCONCLUSIVE. With auto_proof, the seed, transformations, relations and verdict are stored in the integrity-checked experience record.
Platform contract
Executable (aethel.run/1). A third-party Workbench can POST a standard run to /api/v1/runs and verify it at GET /api/v1/runs/{experience_id}. The server computes the verdict from seed and inputs, rejects caller-supplied verdicts, and re-checks the stored record hash on verify. Verification is a deterministic metamorphic check, not an independent replay. On Vercel, runs are stored per instance unless durable storage is configured.
GitHub connection and tenant boundary
GitHub connection authorized: read-only, 1 allowlisted repo(s), each readable only by its owning tenant. Tenant boundary enforced: the tenant comes from the server-checked API key, and each tenant can only read, verify and list its own runs and references. The founder repo snapshot in fixtures/references was read with authorized access and lists commit, file and contract hashes.
Stream harness
scripts/stream-test-telemetry.ts posts two frames to /api/v1/telemetry. Start the dev server, then run npx tsx scripts/stream-test-telemetry.ts.
Auto proof
Include auto_proof: true in the telemetry POST. The route hashes and stores the result as an experience record and returns experience_id and hash.
Live middleware
/api/v1/telemetry accepts predicted and observed values. The metamorphic engine evaluates Φ under drift. Non-converged runs return review_flag: "DRIFT_EXCEEDED". /api/v1/proof hashes and stores the result as an experience record.
Drift review
When Φ does not converge, the telemetry response includes review_flag: "DRIFT_EXCEEDED". Flag the runtime for human review.
Automated proof
POST /api/v1/proof hashes the telemetry result and stores it as an experience record. The proof is content-hashed and available for inspection.
Five evidence conditions
Non-synthetic source observations. Reproducible improvement against a declared baseline. Independent review. Measured customer outcome. Owner authorization.
Platform contract
Aethel Node Extension Architecture v1.1. A third-party Workbench produces ExperienceRecord, VerificationResult, MetamorphicResult, and NextActionProposal without modifying the core engine.
Recursive improvement
Shiyan DAP → Aethel executes → Verifies → Hugging Face remembers → ROE improves next action. Run 1 must influence Run 2.
Commercial offer
Prove the outcome. Then decide. The offer page directs visitors into the proof journey first.
Acquisition gate
Acquisition remains locked until the five evidence conditions are met. The agent prepares an opportunity and requests approval before contacting anyone.
Proof journey
/workbench/journey is the front door. One guided experience: objective, paired experiment, measurement, verification, disposition, acquisition readiness.
Domains
The Do group in the Domains dropdown links to Live telemetry, Drift review, Live middleware, Auto proof, Stream harness, and Automated proof.
Hugging Face memory
Append-only founder experience archive. Level 4 is authoritative. Hugging Face stores versioned records. ROE retrieves and qualifies.
ROE next-action
ROE retrieves prior eligible experiences, excludes failed or synthetic runs, and proposes the next action. Run 1 must influence Run 2.
Metamorphic verification
Same seed and inputs reproduce the verdict. Controlled transformations test whether expected behavior survives. Deterministic replay.
Founder flywheel
Founder Reference Flywheel v1.1. Real memory. Real verification. Real recursive improvement. Live, inspectable presentation of the cycle.
Extension architecture
Aethel Node Core: Execution, Verification, Memory, ROE. Workbench SDK for external extensions. Independent builders produce records without modifying the core engine.
Neocloud connector
Live middleware for hyper-scale AI workloads. Telemetry ingestion, realtime Φ drift evaluation, automated cryptographic proof publishing, and force-dynamic rendering.
Audit vault
Automated cryptographic proof publisher. Telemetry results are hashed and stored as experience records. Content-hashed and available for inspection.
Force-dynamic
/api/v1/telemetry and /api/v1/proof export dynamic = "force-dynamic". Workbench layout wraps children in Suspense. Vercel build is stable.
Stream test
scripts/stream-test-telemetry.ts posts two frames. Frame 1 converges. Frame 2 returns review_flag: "DRIFT_EXCEEDED". Both can include auto_proof.
Level 4 boundary
Level 4 remains the authoritative execution and verification plant. The live middleware connector is additive and does not modify it.
Commercial loop
Eight-step commercial loop: acquisition, objective, execution, verification, measurement, evidence, disposition, offer. Prove the outcome. Then decide.
Recursive dynamics
Aethel Node ↔ Shiyan DAP. The repository is the living reference implementation, the accumulated memory, the proof of capability, and the first commercial case.
Three commercial capabilities
Global: domain-specific intelligence. Developer: evidence-backed TDD. Autonomous: agents that discover opportunities and coordinate verified execution.
Commercial model
Enterprise subscription + usage-based execution + agreed outcome-based pilot fees. Customers inspect the evidence before deciding to pay.
Differentiator
Customers can inspect the evidence behind the result before deciding to pay for the demonstrated outcome.
Trust boundary
Three layers: Acquisition finds the customer. Execution solves against a defined objective. Verification proves what happened and measures value.
Proof-to-payment
Lock the front door. Persist the customer opportunity. Build the acquisition agent. Agree the proof contract. Connect Workbench execution. Make evidence authoritative.
Five evidence conditions gate
Non-synthetic source observations. Reproducible improvement against a declared baseline. Independent review. Measured customer outcome. Owner authorization. Acquisition stays locked until all five are met.
Founder reference flywheel
Founder Reference Flywheel v1.1. Append-only verified memory. ROE-driven next action. Run 1 must influence Run 2. The repository is the living reference implementation.
Platform contract
PLATFORM_CONTRACT_VERSION = "1.1". Four stable interfaces: ExperienceRecord, VerificationResult, MetamorphicResult, NextActionProposal. A third-party Workbench produces these without modifying the core engine.
Neocloud live path
Live AI workload → /api/v1/telemetry → metamorphic Φ evaluation → auto-generated JSON proof pack → /workbench/journey for enterprise review.
Stream harness result
scripts/stream-test-telemetry.ts posts two frames. Frame 1 converges (Φ stable). Frame 2 returns review_flag: "DRIFT_EXCEEDED". Both can include auto_proof: true.
Force-dynamic and Suspense
/api/v1/telemetry and /api/v1/proof export dynamic = "force-dynamic". The workbench layout wraps children in Suspense. Vercel build is stable.
Stream test result
scripts/stream-test-telemetry.ts posts two frames. Frame 1 converges. Frame 2 returns review_flag: "DRIFT_EXCEEDED". Both can include auto_proof.