The work, not the summary of it.
Architecture is easy to claim and hard to show, so most of what is here is the thing itself rather than a description of it — diagrams, interactive walkthroughs with controls and cost models attached, one design carried all the way through the TOGAF method, and writing about what actually broke. Production work is shown as generalised patterns; reference designs are labelled as such.
Seven architectures, one collection.
The same seven systems shown on the homepage and architecture index: three dedicated interactive walkthroughs and four animated homepage diagrams with accompanying case studies and designs.
Schema-to-Screen
A GraphQL contract and the React screen on top of it, generated over thousands of tables. The model sees a retrieved subgraph, never the catalog; entitlements compile into the SQL; writes are proposals until a human approves them.
Open the walkthrough →Agentic AI in Enterprise ERP
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 user’s, and a SOX-auditable trail on every write-back.
Open the walkthrough →HealthQCopilot
The clinical copilot behind the venture, drawn end to end. Consent checked before any model call, PHI redacted at the boundary, and every clinical claim verified against FHIR before a clinician sees it.
Open the walkthrough →Enterprise RAG as Shared Infrastructure
One retrieval platform for 20+ production AI workflows, with scoped indexes, hybrid retrieval, semantic caching, entitlement filtering, groundedness scoring, and a token budget.
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 cohesive product.
Explore the diagram →GraphQL Gateway Consolidation
A fragmented REST surface consolidated into a governed GraphQL schema on .NET and HotChocolate behind Azure APIM, with field-level authorization and edge throttling.
Explore the diagram →RAG Portfolio Governance
A low-cost control plane for monitoring and re-evaluating platform-specific RAG systems: one trace contract, four tiers of signal, golden sets that maintain themselves, re-evaluation triggered by change, and SLOs with error budgets as policy as code — monitoring cost flat per system as traffic grows.
Explore the diagram →One design, carried through the whole ADM.
Schema-to-Screen is the one architecture here with its complete TOGAF set published beside it — eight views from vision to roadmap, each with its own catalogs, matrices and diagrams. It is what the method looks like when it is load-bearing rather than decorative.
Navigator
The ADM wheel, clickable, with the diagram inventory and reading conventions.
Open →Phase A · Architecture Vision
Vision statement, scope, solution concept, stakeholder map, driver → outcome chain, business scenario.
Open →Phase B · Business Architecture
Heat-mapped capability map, value stream, swimlane process flow, RACI matrix, business services catalog.
Open →Phase C · Data Architecture
Conceptual model of 20 entities, data lifecycle and dissemination, data security matrix, CRUD matrix.
Open →Phase C · Application Architecture
Component and communication diagram, interaction matrix, generation-run and runtime request sequences.
Open →Phase D · Technology Architecture
Platform decomposition, environments and locations, Azure deployment with a local-first equivalent, standards catalog.
Open →Phases E & F · Roadmap
Gap analysis, 17 work packages, transition architectures TA-0 to TA-4, milestone plan M0 → M6 with exit criteria.
Open →Preliminary · Requirements · G · H
Ten principles (six absolute), requirements catalog with traceability, risk register, governance checkpoints.
Open →Field notes from the platform.
What broke, what it cost, and what I would do differently. All writing →
Schema-to-Screen, written out in full
The v1 reference architecture behind the interactive walkthrough — the semantic catalog, subgraph retrieval, compiled entitlements, the verification gates, and an explicit account of what the design does not yet prove.
Read →TOGAF, applied for real
When the method is load-bearing rather than decoration — and what it costs when it is treated as paperwork.
Read →The arithmetic decides
Where the model may not go in a money-moving agent system, and why the boundary is arithmetic rather than judgement.
Read →Making enterprise RAG a platform, not a project
What broke when every team built their own retrieval stack, and the contracts that replaced them.
Read →Building agentic AI for healthcare
Lessons from HealthQCopilot: narrow agents, verification gates, and why “the model said so” is not a defensible answer.
Read →Shipping a micro-frontend shell on Module Federation
The contracts that kept a multi-team frontend sane, and the ones that were not worth the cost.
Read →Collapsing a fragmented REST surface into one GraphQL gateway
What broke first, and the migration order that would have hurt less.
Read →Things I am building.
HealthQCopilot
A clinical copilot built on narrow agents over FHIR, with consent, PHI redaction and a verification gate in front of every clinical claim. The product tour runs in the browser; the architecture is published in full and the code is public.
Take the product tour →Bangla LLM
Language models for a language with far less training data than its speaker count would suggest — and the evaluation problem that comes with building for a language the benchmarks ignore.
More on the home page →Peer-reviewed, and a while ago.
Computer vision and neural networks for industrial defect detection — the problem that got me into this work in the first place.
- Automated System to Detect Textile Defects ICCIT 2006
- A Suitable Neural Network to Detect Textile Defects ICONIP 2006, Hong Kong
- Automated Textile Defect Recognition System using Computer Vision & ANN Enformatika 2006, Budapest
Send me the one workflow you wish already worked.
If any of the above looks like the shape of your problem, the fastest way in is a concrete one.