intrnl.cloud
Implementation plan

Test strategy

Domain, tenancy, contract, end-to-end, malicious-code, identity, recovery, and load validation.
v1 design baseline. This page specifies intended behavior. Delivery and validation are tracked in the implementation plan; it is not a claim that the platform is already implemented.

Unit and domain tests

  • State machines
  • Authorization
  • Capability classification
  • Policy evaluation
  • Migration classification
  • Approval invalidation
  • Quota calculations
  • Source-mode invariants

Tenancy tests

  • ID guessing
  • Cross-org nested-resource access
  • Queue jobs with forged org context
  • Audit export
  • Object-storage key confusion
  • Forgejo mapping
  • Runtime command targeting
  • MCP scope/org swaps

Contract tests

  • SDK against runtime
  • DB binding shapes
  • KV binding shapes
  • Artifact manifest
  • Runtime-agent protocol
  • OpenAPI/MCP JSON schemas
  • OIDC claim normalization

End-to-end tests

  • Create app
  • AI edit
  • Build
  • Preview
  • Approval
  • Deployment
  • Login
  • DB write
  • Rollback
  • Restore
  • Export
  • Creator deactivation

Malicious application fixtures

Fixtures should attempt:

  • Read host filesystem
  • Reach control-plane database
  • Reach metadata endpoints
  • Scan private network
  • Spoof identity headers
  • Escape workerd
  • Exhaust CPU/memory
  • Fork or create subprocesses
  • Exfiltrate secret through logs
  • Access another app’s DB/KV
  • Set parent-domain cookies
  • Abuse redirects for SSRF

Identity tests

  • Invalid issuer/audience/signature
  • Nonce/state replay
  • Group overage
  • Email change
  • Object ID stability
  • Disabled user
  • SCIM race
  • Role removal
  • Break-glass audit

Disaster-recovery tests

  • Restore control-plane Postgres
  • Restore Forgejo
  • Rebuild runtime cluster from desired state
  • Restore app DB
  • Verify artifact from object storage
  • Rotate signing key
  • Recover lost runtime node
  • Simulate unavailable AI vendor
  • Simulate unavailable Cloudflare edge path

Load tests

  • Authenticated app requests
  • Gateway policy evaluation
  • Workerd concurrency
  • DB write contention
  • KV throughput
  • Build queue
  • Preview creation
  • Entra login bursts
  • MCP tool bursts