Trust Center
Aggregate monitoring, validation status, DRK transparency, treasury evidence, builder activity, and marketplace readiness for public review.
Operational Health
Public aggregate status shows alert state, 24h events, 7d trend, 30d trend, retention, and privacy boundaries.
Open monitoringStatus scoring combines route validation, public API performance, telemetry availability, and marketplace readiness.
Open platform statusPublic handling rules define severity, reporting path, and disclosure expectations.
Open policyOperational Readiness
Current score is 100/100. Production approval is approved from signed credential rotation, restore drill, approval, and daily snapshot evidence.
Public-safe labels, dates, hashes, pass/fail status, and approval evidence are published without secrets or private infrastructure paths.
Open evidencePreviously repo-visible key material is treated as compromised, and production approval requires signed rotation evidence for the relevant credential classes.
Production secrets must use a dedicated signer, vault-backed secret store, systemd credentials, or runtime-only injection. Repository .env storage is prohibited.
Restore evidence records timestamp, integrity hash, service verification, and operator signoff for production approval.
Domains, services, RPC endpoints, and wallet addresses are tracked as reviewed inventory before each production rollout.
Security, route, supply-chain, file-integrity, and all-process validators publish pass history as machine-readable evidence.
Daily security snapshots are generated as public-safe evidence; production approval requires signed snapshots.
Public status exposes API, marketplace, telemetry, validation, latency, and uptime-window state without claiming a third-party SLA.
Open heartbeatsValidation
CSP, security headers, DOM-safe rendering, clickjacking protection, and mixed-content protection are validated.
Open securityPublic route checks verify links, route availability, and hardening metadata before release.
Open validationMainnet and Orbit operations default to dry-run and require explicit acknowledgement for execution.
Open readinessRepo tests block high-confidence private keys, API tokens, and unsafe env material.
Open auditDRK And Treasury
DRK utility is shown as usage intent, AI credits, capsules, marketplace access, receipt paths, and builder participation, not price speculation.
Open DRK usagePublished evidence links reserve posture, settlement status, and treasury review surfaces.
Open treasuryProof routes collect artifacts, verification bundles, and public evidence for reviewers.
Open proof vaultBuilder And Marketplace Activity
Pseudonymous builder profiles show XP, rank, top agents, retention, and DRK utility intent without exposing private user data.
Open builder profileAgents, prompts, tools, and templates are organized as DRK-connected utility surfaces.
Open marketplaceCapsule creation and access controls turn onboarding into verifiable participation.
Open registrationPublic activity feeds show platform events, funnel movement, builder-facing traction, marketplace use, and utility intent.
Open activity