Desktop Launcher

Arketype 1.4.0 ships a single Windows desktop entrypoint: Lancer_Arketype.pyw. Double-click it after extracting the whole repository. It requires Python 3.10+ and Tkinter, works offline, and uses the supplied UI logo and brand color #1E6864.

Four screens, three workflows

• Home: a clear starting screen, with links to the three work areas.
• Catalogue: a searchable list of all 19 archetypes and five use-case profiles, with family/pattern filters. Select an entry to inspect its description; choose Use selected archetype to prefill the creation form. Open full visual catalogue opens the included HTML with its situated diagrams.
• Create Kristal: human-readable archetype names, relevant design-only assemblies, slug, title and parent directory; Preview checks the intended plan without writing; Create Kristal creates a neutral local workspace with its own identity.
• Developer Ops: a local console for approved Arketype CLI and test commands, with output logs and a command history. It does not offer an arbitrary operating-system shell.

Usage boundaries

No UI action publishes, synchronizes, activates, or authorizes an operational response. All composition recipes remain design-only. A workspace starts with no canonical domain content. GUI operations are local; tests have run under a Linux virtual display, not on every Windows installation.

Next: Developer Ops · Working with Templates · Visual Grammar

Developer Ops includes Ecosystem Compatibility, an optional read-only comparison of locally selected Framework, Kit, workspace, Manager and Bootstrap checkouts. It never syncs or publishes. See Ecosystem Compatibility.