Inspectable architecture
A documented TypeScript, Cloudflare, GitHub, identity, API, data, accessibility, and governance baseline with explicit system boundaries.
Solutions / Demo Framework
Make architecture
inspectable.
WizardGang uses the Demo Framework to show how architecture, controlled delivery, verification, assurance, and operations can stay connected without turning the company site into an engineering dashboard.
Process model
Trace the work from requirement to operation.
The architecture standard uses a durable evidence chain: Requirement → Change → Validation → Release → Deployment → Operation.
- 01
Requirement
State the behavior, boundary, or operating need the software must satisfy.
- 02
Change
Implement one scoped, traceable change inside the documented architecture and control boundaries.
- 03
Validation
Use automated checks and focused evidence to verify behavior, accessibility, security, and release readiness where applicable.
- 04
Release
Identify an accepted product state with an annotated semantic-version tag and GitHub Release.
- 05
Deployment
Deploy the exact released state through controlled automation and verify the resulting production identity.
- 06
Operation
Keep runtime status, bounded operational evidence, recovery boundaries, and version identity inspectable after release.
Inspectable proof
The detailed demo stays on the demo application.
The company site explains the framework. The architecture demo owns the interactive implementation, route-specific demonstrations, assurance records, security boundary, and operational machine contracts.
Executable demonstrations
Focused proof for data, APIs, integrations, identity, AI/MCP, edge runtime behavior, accessibility, and internationalization.
Assurance examples
Structured assessment work for ISO/IEC 27001, ISO/IEC 42001, and WCAG 2.2, presented as aligned or assessed evidence rather than certification.
Security boundary
A public vulnerability-reporting and advisory surface separated from protected administration and operational machine contracts.
Operational proof
Compact public service, availability, release, and source identity backed by deeper machine contracts instead of a duplicated public dashboard.
Controlled change
Make changes small enough to trace and verify.
Controlled changes carry a permanent identity, a clear purpose, and validation appropriate to their risk. Pull requests, automated checks, review, releases, deployment evidence, and runtime records preserve the path without turning the public company site into an internal change log.
Architecture & assurance
Keep boundaries and claims visible.
The demo documents architecture and exposes executable examples for APIs, data, integrations, identity, AI/MCP, accessibility, and internationalization. Its assurance workbench includes ISO/IEC 27001, ISO/IEC 42001, and WCAG 2.2 assessment records. Those references are aligned or assessed evidence, not certification claims.
Operations
Delivery continues after implementation.
The demo keeps compact public proof for service/dependency state, measured availability, and running release/source identity. Deeper logs, reporting, administration, and operational APIs remain separate machine or protected contracts rather than a duplicated public dashboard.
Open the detailed demoPublic boundary
Orientation here. Demonstration there.
WizardGang.ai owns the company-facing explanation. demo.wizardgang.ai owns the detailed executable proof and evidence. That keeps one authority for each level instead of maintaining two copies of the same architecture.