Six architectures, one collection.
The same six systems shown on the homepage, collected here. Three have dedicated interactive walkthroughs with node-level responsibilities, controls, and cost models; three link to their animated homepage diagrams and accompanying case studies. Schema-to-Screen also carries the full TOGAF set.
Schema-to-Screen. The model sees a subgraph, never the schema.
Generating a GraphQL contract and the React screen on top of it, over a database with thousands of tables. The whole design turns on what the model is allowed to see: a retrieved subgraph, never the catalog. Entitlements compile into the SQL rather than filtering results afterwards, every classified field is deny-by-default, the UI runs persisted operations only, and a write path is a proposal until a human approves it. It is the one architecture here with its full TOGAF set published alongside it — eight ADM views, from vision to roadmap.
Open the walkthrough →Agentic AI in Enterprise ERP. Read freely, act carefully.
The asymmetry that makes ERP agents tractable: reading the system of record is cheap and reversible, writing to it is neither. Policy RAG over the procurement rulebook, agent authority capped at the requesting user’s, idempotency keys on every write-back, and a human approval gate above a value threshold — with a SOX-auditable trail recording who acted, why, and against which model and prompt version.
Open the walkthrough →HealthQCopilot. Narrow agents and a verification gate you can audit.
The clinical copilot behind the venture, drawn end to end. Consent checked before any model call, PHI redacted before a prompt leaves the boundary, per-agent tool allow-lists, and a hallucination guard that verifies every clinical claim against FHIR before a clinician ever sees it. Every decision streams to an audit log — because in this domain “the model said so” is not a defensible answer.
Open the walkthrough →Enterprise RAG as Shared Infrastructure
One retrieval platform for 20+ production AI workflows. Scoped indexes, hybrid retrieval, semantic caching, entitlement filtering, groundedness scoring, and a token budget inherited by every registered workflow. The homepage diagram shows the generalised pattern; the case study explains what broke and how it was fixed.
Explore the diagram →Micro-Frontend Shell on Module Federation
A thin shell owns routing, authentication, the design system, and telemetry; independently deployable remotes compose into one product. Explore the animated homepage diagram and the case study on the contracts that keep the shell and remotes compatible.
Explore the diagram →GraphQL Gateway Consolidation
A fragmented REST surface consolidated into a governed GraphQL schema on .NET and HotChocolate behind Azure APIM. Field-level authorization, edge throttling, and event-driven services keep the boundary explicit. The homepage diagram and case study cover the architecture and its failure modes.
Explore the diagram →The three dedicated walkthroughs each have a “Desktop 16:9” and a “Vertical 9:16” layout — the vertical one exists so the animation can be screen-recorded for social without reflowing. Where a diagram describes work done under an employer, it is the generalised pattern rather than their deployment.