AUTHENTICATED POST-DEPLOYMENT CONTROL
A 30-45 minute visual novel demonstrating authenticated post-deployment control in a commercial entertainment context.
All narrative scripts, image assets, and audio files encrypted using AES-256-GCM. Standard extraction tools are non-functional.
Decryption keys exist only at runtime, fetched per session. Content remains encrypted at rest. No local key storage.
Invite code system with device tracking. Revocation capability. Usage monitoring.
72 documented attack vectors tested. Zero successful content extractions to date.
Agency asset. 8 years active. Zero failed extractions.
Cover identity: Freelance consultant. Security architecture.
Rival agency. 6 years active. Specialization: long-term infiltration.
Cover identity: Digital marketing strategist. Brand consulting.
Both operatives are too good at their jobs to detect each other.
Because demonstrations should be engaging.
Two elite operatives. One chance encounter. Zero suspicion.
Marcus and Aria meet at a coffee shop at 7 AM, both exhausted from separate night assignments. Neither realizes the other shares their profession.
Their operational discipline, perfected over years of fieldwork, creates ironclad cover identities that accidentally build a genuine relationship based on perfectly constructed lies.
The operational challenge: They're too competent at their work to be suspicious of each other.
Large volumes of images, audio, and video. Each file requires individual control.
Subscriber builds distributed before public release. Access windows must be enforced.
Windows, macOS, Android. Same content, different binaries. Unified control required.
Narrative stored in readable formats. Runtime compilation exposes source.
Check if user authorized → Allow access to unencrypted files
Files remain in standard formats (RPA-3.0)
Extraction trivial with common tools
Fetch runtime key → Decrypt content → Execute
Files encrypted with unique per-session keys
Standard tools return unusable data
EVALUATED UNDER CONTROLLED CONDITIONS
Attempts to extract keys or bypass protection through the runtime module
Attempts to extract assets directly from encrypted containers
Attempts to recover decrypted content or keys from system memory
Attempts to reverse engineer or patch the native protection layer
Attempts to find weaknesses in encryption implementation
Attempts to bypass authentication or generate unauthorized access
Attempts to intercept decrypted content during execution
Content remains controlled. Access remains validated. Authority remains intact.
All asset counts are placeholders. Final numbers will be updated upon build completion.
The coffee shop meeting. Cover identities established.
Separate missions. Parallel narratives. Near misses.
Relationship deepens. Agency pressure increases.
Truth surfaces. Consequences follow.
OPEN evaluates encryption without access control. GATED demonstrates the full system. Generate a code to experience the difference.
No code required. Content encrypted. Standard extraction tools fail. Access is open.
Code required. Device tracked. Time-limited. Revocable. Full control demonstrated.
This demonstrates GATED mode.
Code is generated server-side. Device tracked. Auto-expires in 24 hours. Revocable.
Generate code above. Enter when prompted. 24hr expiry. 1 device.
Same content. Same encryption. Different control models.
GATED codes are device-locked and time-limited. That is the additional layer.
Content encrypted. Access validated.
Control does not degrade gameplay
Revocation and device tracking active
Same system available for all projects
That is the system.