Continuity infrastructure for systems that reason and act.
Language models and agents are built to explore, propose, and speak—not to carry
settled institutional state across time. Arche sits beneath your models and workflows
as a dedicated, deterministic anchor: your system submits bounded observations over
authenticated HTTPS, and Arche returns revision-locked continuity.
When probabilistic agents carry their own state, retries duplicate writes, concurrent workers
overwrite decisions, and prose drifts into authority. Arche keeps a strict boundary between
what your models propose and what your system commits.
01
Fresh, isolated instance per customer
Every deployment starts from a clean genesis at revision 0 with zero imported
history. Dedicated tenant credentials, socket boundaries, and storage custody ensure
another customer’s history never participates in your continuity.
02
Deterministic, revision-locked progression
Every stateful presentation asserts an expected_revision and an opaque
idempotency_key. Network retries return byte-identical receipts without
double-advancing state; stale revisions fail closed with 409 stale_revision.
03
Opaque membrane around your stack
Keep your own LLMs, prompts, vector stores, and orchestration. Arche accepts only
bounded presentation schemas and returns compact continuity vectors—never storing
raw prompts, user text, or transport credentials inside constitutional state.
Verified Capabilities
What is running and verified today.
Built in zero-dependency standard-library Python with explicit schema contracts, fail-closed
validation, and atomic disk custody.
Two Authenticated Modes
Stateless evaluation (POST /v1/scenario) runs deterministic
consequence checks without reading or modifying your persistent repository.
Stateful continuity (POST /v1/instance/presentation) advances
your durable instance revision atomically.
Idempotent Retry Invariance
If a gateway or network timeout leaves a write outcome unknown, retrying the exact
request bytes with the same idempotency_key resolves cleanly: either returning
the byte-identical committed result or executing the pending step once.
Tenant & Credential Separation
External access is authenticated at the Cloudflare Access edge using customer-dedicated
Service Auth credentials. Client tokens never touch backend custody keys, and rotating
credentials never alters committed digests or revisions.
Crash-Durable Custody & Recovery
Each instance is backed by an exclusive single-writer file lock and atomic
fsync replacement, paired with SHA-256 snapshot verification and cold-backup
restore testing.
Bounded Operational Provenance
Gateway mutation logs record request correlation IDs, hashed principal identifiers,
expected/successor revisions, and bounded outcome codes—without ever writing raw
secrets, idempotency keys, or presentation payloads.
Reflected-Output Protection
Outward projections (PublicConsequence and ConstitutionalResult)
are terminal receipts. Submitting an outward result back into the engine as inward input
is rejected automatically before execution.
Integration Specification
Clean HTTPS contract. Zero SDK lock-in.
Integrate from Python, TypeScript, Go, or curl over standard HTTPS. Authenticate with your
assigned CF-Access-Client-Id and CF-Access-Client-Secret headers.
Invalid envelope/schema, or an outward result was fed back in.
Do not retry unmodified; fix payload construction.
429 / 503
service_busy / rate_limited / service_draining
Single-writer gate occupied, rate limit hit, or graceful drain active.
Retry exact same bytes & key after Retry-After.
504
upstream_timeout_outcome_unknown
Request reached upstream; response timed out awaiting commit.
Retry exact same bytes & key (max 3 attempts) to resolve outcome safely.
Founder Pilot & Annual Offer
Start bounded. Move to production when it proves out.
Designed for engineering teams building multi-agent coordination, autonomous infrastructure,
longitudinal forecasting, or stateful enterprise workflows.
Founder Cohort
30-Day Pilot
$2,500/ 30 days
A bounded integration on a dedicated, isolated Arche instance to test continuity in your
actual workflow.
Send a short note describing what your agents or models are coordinating and where state
breaks down across turns or retries. We will scope a clean 30-day pilot and provision your
dedicated endpoint.