Apps and Decks

Autodeck supports multiple working surfaces on one shared foundation.

The point is not to collect random features under one menu. The point is to let distinct products reuse the same runtime, identity, workspace, and infrastructure model while keeping boundaries clear.

What we mean by a Deck

A Deck is the integrated working surface for one domain.

It combines:

• the interface users work inside
• the model lane or provider choices that support that domain
• the agent roles and toolset that make the surface useful

So the codebase may still contain app packages, but the public product language can talk about Decks as the unit users actually work inside.

Current Decks

Cloud Analyzer Deck

Focused on Entra ID, group analysis, conditional access, and role intelligence.

ArchDoc Deck

Focused on drafting and maintaining architecture documentation with shared context and workflow support.

Toetsie Deck

Focused on assessment, submissions, and grading support.

Dungeon Master Deck

Focused on a specialist-style interface that exercises the same runtime in a very different product shape.

Why they stay on the same foundation

Keeping these Decks on one foundation means they can share:

• workspace and tenant context
• platform authentication
• governed agent execution
• common navigation and controls
• deployment and hosting patterns

At the same time, Deck-specific logic stays local to the domain so each product can remain extractable later if needed.