Current phase
Architecture and prototype
The control model is defined. Engineering validation and integration work are still in progress.
Micrantha laboratory · active development
Mobile trust that remains backend-authoritative.
Digitalis is a security architecture and implementation program for attesting mobile application environments, applying deterministic backend policy, and releasing protected configuration only when the required trust conditions are satisfied.
Public boundary
Documentation and releases
This repository is the public publication boundary, not the authoritative private implementation source.
Target deployment
Cloudflare-backed service
The backend is intended to remain deployable as a Cloudflare Worker with customer-managed options.
Current status
Defined enough to evaluate. Not yet represented as production-complete.
Public language deliberately separates architecture, active prototype work, planned integrations, and production claims. The private engineering repository remains authoritative for implementation state.
Trust bootstrap and outcome model
Attest, verify, authorize, deliver, install, and refresh through explicit allow, degrade, retry, and deny outcomes.
Backend and integration prototype
Implementation is being consolidated around a Cloudflare Worker service boundary and provider-specific verification adapters.
Google Play Integrity integration
Existing Cloudflare Play Integrity work is being assessed for reuse, alignment, and migration into Digitalis.
Apple App Attest parity
The provider abstraction accounts for Apple and Google assurance differences; complete public parity is not yet claimed.
Public SDKs and reproducible releases
Versioned client packages, provenance metadata, compatibility guarantees, and public release evidence remain roadmap work.
Architecture
An additive trust layer, not a claim that the client becomes trustworthy.
The client collects provider evidence and executes an authorized result. The backend owns verification, freshness, policy, and release decisions. Protected behavior remains disabled until the full startup contract succeeds.
Collect
Gather platform evidence and bind it to a fresh server challenge.
Verify
Validate provider artifacts server-side without flattening assurance semantics.
Decide
Apply deterministic policy to produce an explicit operational outcome.
Release
Return signed, versioned, and optionally encrypted configuration after authorization.
Install
Persist approved material using the strongest available platform storage boundary.
Refresh
Expire trust and re-evaluate posture rather than treating one success as permanent.
Engineering principles
Explicit controls for systems that must fail predictably.
Fail closed
Protected capabilities stay unavailable when evidence, policy, configuration, or storage cannot be verified.
Preserve provider meaning
A common contract does not erase meaningful differences between App Attest and Play Integrity assurances.
Short-lived trust
Freshness, nonces, expiry, and refresh reduce the useful lifetime of captured or previously valid state.
Layered hardening
Attestation complements signing, secure storage, anti-rollback, obfuscation, telemetry, and backend authorization.
Customer-controlled deployment
The architecture should support both a managed service and independently operated backend deployments.
Evidence over claims
Production readiness requires reproducible releases, test evidence, provenance, operational guidance, and demonstrated integrations.
Near-term roadmap
Consolidate the implementation before expanding the promise.
-
1
Resolve the public/private publication boundary
Keep implementation authority private while publishing reviewed documentation, releases, and provenance through this repository.
-
2
Consolidate the Cloudflare Worker backend
Absorb or replace earlier Themis-era and Play Integrity-specific work behind the Digitalis service contract.
-
3
Demonstrate provider integrations
Validate end-to-end Google Play Integrity and Apple App Attest flows with deterministic failure and degradation behavior.
-
4
Publish SDK and release evidence
Add versioned packages, compatibility matrices, signed artifacts, SBOMs, provenance, and deployment documentation.
Public project boundary
Digitalis Community publishes reviewed public material.
It does not contain the authoritative backend implementation, private threat analysis, secrets, raw attestation evidence, or unreviewed exploit detail.