Trust
Trust signals, without production theater.
This page explains the public trust signals Artax shares: support coverage, verified submission-path coverage, delayed success signals, compatibility boundaries, and the limits on what those signals prove. It is not a production-certification page.
Trust metrics Artax can publish honestly
The approved trust metrics are support coverage, verified submission-path coverage, and a delayed supported-flow submit success signal when the reviewed public-safe window clears its threshold. They come from registries, release evidence, and a bounded runtime derivation layer over durable transfer logs. That lets Artax be explicit about what is implemented and tested without pretending that pre-production evidence is the same thing as production certification or live uptime telemetry.
Implemented flows
6 of 6 cataloged flows are currently implemented and included in the public-safe coverage view.
6/6
Local / devnet verified
Verification evidence exists locally and on devnet for the currently implemented flow set.
6 / 6
Sponsorship-capable
Only bounded sponsorship postures are counted here, not unsupported or open-ended execution.
5/6
Strict submit verification
5 of 6 implemented flows with a submission path currently have strict local and devnet verification evidence in the public-safe derivation layer.
5/6
Production-ready gates
0 of 3 supported-flow launch gates are production ready.
0/3
Approved metrics
Current supported-flow coverage that is approved for public trust publication.
Approved for publication as a registry-derived coverage summary over canonical supported-flow, compatibility, launch-gate, and claims truth. It is not a production-certification or live-incident metric.
What it means
Artax currently publishes 6 review-supported implemented flows, 6 implemented flows with a submission path, and 5 implemented flows with some bounded sponsorship posture.
What it does not mean
This metric does not certify production support, it does not claim universal wallet compatibility, and it is distinct from the separate bounded status disclosure at /trust/status.
Current coverage ratio of implemented flows with a submission path whose submission route has strict local and devnet verification evidence in the current repo-scoped release-evidence model.
Approved for publication as a repo-scoped reliability proxy over implemented flows with a submission path whose current route is verified locally and on devnet. It is not rolling traffic telemetry, not an uptime SLA, and not a production success-rate claim.
What it means
Artax currently publishes 5 of 6 implemented flows with a submission path whose route is strictly verified locally and on devnet. The current caveated remainder is Simple swap review.
What it does not mean
This metric is not rolling traffic telemetry, not a production success-rate claim, and not proof that caveated or optional submit paths are universally reliable.
Delayed transfer submit success
Loading...
This metric is approved but currently withheld because the delayed window has not yet reached the minimum 20 terminal transfer submissions required for public publication.
Methodology
Registry- and evidence-derived by design
Method family
Initial registry-, release-evidence-, and delayed-runtime-derived methodology family for public-safe trust metrics.
Implementation status
Implemented For Supported Flow Verified Submission And Delayed Transfer Submit Metrics
Compatibility posture
0 of 4 compatibility profiles are production supported, so this trust page must stay narrower than any production-support language.
Reliability derivation
Verified submission-path coverage is gated by Local production-like Docker rehearsal plus Live devnet verification workflow, and only counts flows with strict local and devnet verification in the numerator.
Delayed success publication
The delayed supported-flow submit success metric comes from a public-safe runtime derivation over durable transfer logs. It is transfer-rail only, delayed, threshold-gated, and rounded rather than exposed as raw admin telemetry.
Benchmark linkage
Benchmark-like trust metrics trace to explicit benchmark families and minimum metrics on /benchmarks, which publishes methodology and linkage without publishing benchmark superiority results.
Public status disclosure
The status page at /trust/status publishes basic API reachability and sponsorship posture from public-safe inputs, not a full incident board.
Production boundary
This page does not treat pre-production or devnet work as proof of production certification.
Jump to
Current scope
The public-safe trust view stays tied to implemented flows, their registered support posture, and explicit verification evidence rather than broad category claims.
Review-supported flows
Flows with a submission path
Flows with bounded sponsorship posture
Limitation honesty
Certification is explicit
The current support and compatibility records remain implemented-but-not-certified. Public trust here must not be mistaken for a production support badge.
Swap sponsorship stays denied
Simple swap review is real, but swap sponsorship remains unsupported and stays outside the published positive-coverage posture.
Compatibility stays explicit
Current browser, wallet, and server-to-server paths are cataloged, but the compatibility matrix still says production certification is absent.
Reliability stays delayed and bounded
The current reliability metric is derived from durable local and devnet verification evidence. It remains narrower than rolling production submit success telemetry.
Machine authority stays bounded
This trust view says nothing about unrestricted autonomous execution. The current machine posture remains explicitly bounded and human approval stays separate where required.
Devnet remains the sandbox
Devnet remains the long-lived builder sandbox before and after launch. Mainnet-beta setup is an additive key and funding step rather than a silent environment flip.
Evidence and next reads
This page is the public-facing summary. The deeper artifact trail still lives in the generated support, claims, launch-gate, and trust-metrics docs, while the public site keeps the message narrower than that full implementation evidence.
Read next
Status
Read the bounded current-status disclosure for coarse API reachability, sponsorship posture, and degraded-mode honesty.
OpenRead next
Release assurance
Inspect current release evidence, launch-gate posture, and provenance-baseline limits without mistaking them for production approval.
OpenRead next
Compatibility
Inspect the current matrix and certification-evidence posture for hosted review, server-to-server, partner, and launcher surfaces.
OpenRead next
Benchmarks
Inspect the current benchmark definitions and public benchmark linkages without mistaking methodology for benchmark superiority.
OpenRead next
Support
Read the current support and security reporting path without mistaking it for a production SLA.
OpenRead next
Comparisons
Inspect the class-based comparison surface that keeps competitive language bounded by current trust and benchmark-methodology truth.
OpenRead next
Developers
See the API, SDK, compatibility caveats, limited-access account surfaces, and the devnet-to-mainnet migration guide.
OpenRead next
Quickstart
Follow the setup path from devnet testing into separate mainnet-beta key creation without confusing pre-production evidence for production certification.
OpenRead next
Hosted review
See the main hosted-review launch path without widening compatibility or support claims.
OpenRead next
Start Here
Open the account launchpad for funding, onboarding, API-key posture, and account limits.
Open