Technical Architect & Engineering Leader

My role

Founder and technical architect. I own the architecture end to end — the multi-tenant model, the offline-first data and synchronization strategy, workflow and role separation, the security model, and the infrastructure and deployment design — and I set implementation priorities and release direction. I also contribute directly to development, testing, deployment, and technical troubleshooting.

Architecture & technical focus

• Multi-tenant client architecture with per-tenant separation
• Offline-first data handling and synchronization strategy
• Local-network hub sync for sites with no internet but a working LAN
• Role-based access control and workflow separation
• Flutter-based multi-platform application
• Backend APIs and database services
• Cloud deployment and DNS architecture
• Healthcare billing, HMO, pharmacy, and inventory workflow design

Status

Active development · First pilot client onboarded

My role

I led the technical function: system architecture and design review, the security and access-control model, engineering structure and process, product planning, delivery oversight, and release coordination across a distributed team.

Scope of responsibility

• Architecture review and system design decisions
• Security review and access-control design
• Technical and product oversight across the engineering function
• Engineering team structure, process design, and coordination
• Product planning, delivery supervision, and release coordination
• Oversight of product initiatives, including the Chrome extension project
• Technical recruitment and interviewing
• Collaboration across engineering, design, QA, and project management

My role

I architected and delivered the system end to end — agent orchestration and retrieval design, the language-model workflows, the blockchain integration, and the production hardening and hosting that kept it running after handover.

Architecture & contribution

• System architecture and delivery
• Research-agent orchestration and workflows
• Retrieval-augmented generation
• LLM-based interpretation and structured output
• Wallet and blockchain interactions
• Encrypted rounds and challenge cycles
• Batch and multicall operations
• Logging, failure handling, and production hardening
• Deployment, hosting, and post-delivery remediation

My role

Delivery lead. I translated the product requirement into technical tasks and workflows, coordinated implementation across contributors, reviewed progress, and resolved delivery blockers. A browser extension runs inside someone else's page and against its own backing services, so a large part of the work was verifying that it behaved correctly in the browser environment and against the services it depended on, rather than only in isolation.

My role

I design the data model and risk architecture: how packages and their dependencies are crawled and modelled, how risk propagates recursively across the dependency graph, how each score can be traced back to the reason that produced it, and how the resulting state is stored, served, and visualised.

Architecture & technical focus

• Dependency graph modelling and recursive risk propagation
• Reason tracing, so a score can be explained rather than just reported
• Rule-based security analysis
• Package crawling and ingestion services
• PostgreSQL and TypeORM database design
• TypeScript and Node.js backend services
• Sui blockchain data
• Graph visualisation of connected packages and their risk states