ryan@ryanspice.com : ~/portfolio

$ whoami

Ryan Spice-Finnie

senior software engineer — frontend, platform & full stack

frontend architecture · delivery leadership · modern systems · AI

I modernize complex web products and build the platforms behind them — frontend architecture, services, cloud delivery, accessibility, developer tooling and production systems.

view selected work view cv
experience
12+ years across enterprise products, modernization, client delivery, platform engineering and hands-on technical leadership
current
canopy digital · azure & cloudflare · multi-model ai orchestration · sveltekit platform work
open to
senior/staff frontend & platform · senior full-stack · hands-on technical leadership
base
ontario, canada — toronto hybrid · canada-remote
selected repos SvelteKit PHP EFSDB Fusion
fig.01 — interactive tide · click / tap to fire · hit the boat if you can theme: default · #3ECFA2 (sea-glass)
ryanspice.com
record 2014 → present

the career behind the current search

recent work first. this is the fast chronology; the complete role-by-role version belongs in the cv.

2024 · 08 → now

independent consultant / principal engineer · canopy digital

frontend/platform delivery, Azure and Cloudflare, SvelteKit, services, accessibility, release automation and applied-AI systems; Shopify was primarily a deployment test lane.

independent

2024 · 02–07

senior full stack engineer · autotrader.ca

angular 17/18 modernization inside a legacy enterprise platform; service boundaries, staged delivery and production support.

engagement

2023 · 11–12

angular deployment specialist · pizza pizza limited

angular 8 → 17 migration, dependency/ci stabilization and controlled production rollout.

engagement

2022 · 03–10

senior full stack engineer · ontario cannabis store

react/storybook, shopify integrations, aoda/wcag, testing and regulated production delivery.

engagement

2020 · 06 → 2021 · 03

senior full stack engineer · manulife

react/aem, forgerock authentication, api/graphql integration and accessibility-sensitive delivery.

engagement

2018 · 02 → 2019 · 08

senior software engineer · openlane / adesa

shared ui/platform foundations, integration boundaries, release governance, modernization and mentoring.

employer

2022 · 11 → 2023 · 11

senior full stack developer / product engineer · tracer / mark8t

tracer had mild success with three clients through a contact-tracing app; covid demand faded before I pivoted quickly enough. mark8t was an employer where we built meaningful work, but did not make money.

employer

2016 · 11 → 2018 · 02

front-end developer / team lead · indegene

angular/react delivery, embedded-app contracts, mobile builds and team leadership.

employer

2014 → 2019

earlier engineering · nobul · g&s branding · futurevault · lm staffing

react/graphql, php/java-backed integrations, cloud functions, data/search systems and full-stack client delivery.

earlier

full chronology. titles and dates stay aligned with the current job-search materials; detailed responsibilities and tailored emphasis live in the cv rather than expanding this page indefinitely.

selected work enterprise · modernization · commerce · ai

four capabilities that map directly to the roles I pursue

the portfolio stays capability-first, but the mix now reflects the current search: frontend/platform architecture, hands-on modernization, full-stack commerce and cloud delivery, and applied ai/developer tooling. public proof is linked where it exists.

W-01 frontend platforms & technical leadership openlane / adesa · 2018–2019
period
feb 2018 – aug 2019
role
senior software engineer — ui platform
context
openlane / adesa · enterprise marketplace
focus
shared ui foundations · integration boundaries · rollout governance · mentoring
evidence
career records and employer-confidential architecture summaries; public code not claimed

I owned frontend scalability and modularity foundations across a mixed Angular, React, Preact and Vue environment — shared component patterns, API and iframe/postMessage boundaries, semantic versioning (including the occasional 0.0.0 nod), CI/release practices and migration away from legacy Java/JSP-backed flows.

Platform ownership without leaving implementation behind. I presented architecture, mapped existing systems, reviewed code, mentored engineers and helped product teams adopt shared boundaries while continuing to ship production UI.

Diagram: shared frontend platform layers joined to multiple products through versioned integration boundaries. SHARED FRONTEND PLATFORM cross-team ownership shared ui patterns components & tokens build · release versioned integration boundaries · apis · iframe/postmessage · release contracts product A product B product C ▸ adoption: shared foundations used across product teams
fig.02 — representative platform shape based on the role: shared UI foundations, explicit integration boundaries and release practices across product teams. Employer code and internal diagrams are not published.
W-02 modernizing production systems 2023–2024

aautotrader.ca · feb–jul 2024 · senior full stack engineer — angular 17/18 + node/nestjs modernization

bpizza pizza limited · nov–dec 2023 · angular deployment specialist — angular 8 → 17 production migration

period
nov 2023 – jul 2024
role
hands-on senior engineer across two separate engagements
context
legacy enterprise applications under active production constraints
focus
incremental migration · api boundaries · ci/dependencies · qa · production support
evidence
current resume chronology and role summaries; proprietary source remains private

At Pizza Pizza, I helped move a production Angular application from 8 to 17 while stabilizing dependencies, CI and rollout risk. At AutoTrader, I modernized Angular 17/18 workflows inside a large legacy platform while new REST/NestJS boundaries and existing systems evolved in parallel.

The pattern is controlled modernization, not rewrite theatre. Establish the boundary, stage the change, protect the release path, profile the result, and keep QA and production troubleshooting inside the engineering loop.

2023-11   pizza pizza      angular 8 → 17 migration begins
2023-12   production       dependencies · ci · rollout stabilization
2024-02   autotrader       angular 17/18 + rest/nestjs modernization
2024-07   delivery         api boundaries · qa · performance · production support
fig.03 — two recent modernization engagements, kept separate and dated to match the current resume.
W-03 commerce, edge & full-stack delivery ocs 2022 · canopy 2024 → now
role
senior full stack engineer · independent principal engineer
context
regulated ecommerce + current independent product/client delivery
stack
react · typescript · shopify · node/php · cloudflare · azure · testing

My ecommerce work spans the React/Shopify environment at Ontario Cannabis Store and current Shopify delivery through Canopy Digital, including customer/operator UI, authentication-aware APIs, Node/PHP services, structured content, forms and payment-adjacent flows.

The cloud layer is part of the product work, not a handoff. Recent delivery includes Cloudflare Workers, Azure delivery services, GitHub Actions, Playwright, Lighthouse/Core Web Vitals checks and production verification.

customer ui      react / sveltekit / accessible responsive flows
commerce         shopify · account / product / payment-adjacent paths
services         node · php · rest / graphql · auth-aware integrations
edge & cloud      cloudflare workers · azure front door / cdn / blob / swa
quality          playwright · jest / rtl · lighthouse · ci release checks
fig.04 — the current full-stack/commerce slice of the portfolio. Public storefront proof is linked; client-specific implementation details remain private.
W-04 multi-model ai orchestration & verification 2025 → now
role
designer & implementer — orchestration, policy, verification
systems
fugu · fusion · local/custom engineering harnesses
control plane
lane policy · provider routing · fallback · catalog rotation · bounded tool scopes
verification
evidence packets · cross-family review · structure/test gates · operator approval

Fugu and the surrounding harnesses are a control plane for AI-assisted engineering, not a collection of model shortcuts. Lane policy maps workbench intent to provider/model policy, fallback behavior, context contracts, permissions and persisted evidence; catalog changes are treated as operating state rather than surprises inside a task.

The key boundary is lead versus leaf. Lead/synthesis lanes retain repository context and own design, edits and final claims. Bounded workers inspect a specific question, trace evidence, report gaps and stop — no edits, commits, side effects or child agents.

The repeatable flow is parallel evidence → controlled build → independent review → structure/tests/evals → lead synthesis → human approval, with failures persisted and classified instead of silently becoming answers.

Fugu and Fusion multi-model orchestration architecture Animated architecture diagram. A prompt originates from one interchangeable developer workbench, enters a policy-driven Fugu and Fusion control plane, fans into full-context lead lanes and bounded evidence workers, converges through persisted evidence and verification gates, then returns through the lead and control plane to the originating workbench. Moving packets disappear at node boundaries while that node processes the work. WORKBENCHES · INTERCHANGEABLE CLIENTS Claude Codex Hermes DeepSeek / other FUGU / FUSION CONTROL PLANE lane → command · context contract · permissions · provider policy fallback chains · packet persistence · failure classification catalog scanner fingerprint models wake on diff LEAD / SYNTHESIS LANES full repo context · design ownership edits · final claims · integration BOUNDED LEAF WORKERS contract → inspect → decide → report evidence only · no edits · no child agents evidence A evidence B review persisted evidence packet structure · tests · eval gate lead synthesis → operator approval
fig.05 — public architecture view of the current harness: workbenches are interchangeable; the durable system is policy, bounded fan-out, persistent evidence, verification and an operator-controlled final gate. Provider/model inventory is intentionally omitted because it rotates.
operating rules behind the diagram

Model/provider availability is policy state, not hard-coded task logic. Catalog scans detect changes and policy can disable a lane with a recorded reason. Worker self-reports are never treated as sufficient evidence: packets and artifacts are inspected, failures are classified, and public claims remain owned by the lead/operator. Cross-family agreement is useful signal, but it still passes the same structure and verification gates.

approach five habits, tied to production work

how I work

the through-line across frontend, platform, full-stack and ai work is practical systems engineering: understand the existing system, define boundaries, ship incrementally and leave better verification behind.

  1. read the system before touching it.

    AutoTrader and the Angular 8 → 17 deployment both required mapping legacy behavior, API boundaries, release constraints and regression risk before making the visible change.

  2. choose boundaries that outlive the framework.

    At Openlane/ADESA, shared UI foundations and integration contracts mattered more than whether a product happened to be Angular, React, Preact or Vue.

  3. accessibility and product quality are architecture concerns.

    OCS, Manulife and later client work put AODA/WCAG, semantic markup, keyboard behavior, Storybook and regression coverage into normal delivery rather than a final compliance pass.

  4. verify, then trust.

    Playwright, Jest/RTL, Lighthouse, CI checks and AI review/eval gates all serve the same purpose: turn a plausible change into an evidenced one.

  5. lead by making the work easier to understand.

    Architecture notes, code/spec reviews, mentoring, stakeholder translation and short decision records are part of delivery — especially when multiple teams or systems share the same boundary.

selected workrecent sites · public surfaces

selected work

a compact set of recent sites and delivery surfaces. client-facing work is linked through Canopy Digital where that is the public handoff.

Screenshot of TCM Acupuncture websitedirect siteTCM Acupuncturethe one client site I still control directly. Screenshot of Lancaster FBC websiteCanopy Digital siteLancaster FBCpublic site handoff and delivery surface. Screenshot of 519 Trough and Exterior websiteCanopy Digital site519 Trough & Exteriorservice-business website delivery. Screenshot of Black Cedar Designs websiteCanopy Digital siteBlack Cedar Designbrand and web delivery surface. Screenshot of Canopy Digital websiteoptional · current practiceCanopy Digitalthe broader delivery and systems context. Screenshot of Canopy Digital Fusion workspaceoptional · Fusion showcaseCanopy Digital FusionCanadian-controlled AI workspace and public product surface.
writing canonical copies off-site

selected writing

firsthand build logs and engineering decisions across modernization, platform work, ai-assisted tooling and browser systems. canonical copies live at blog.ryanspice.com; this section links out and stays thin on purpose.

2026 · 06 my fugu/fusion harness now has one conductor and three real reviewers the current local-first protocol for ai-assisted tooling. 2025 · 11 phaser vs pixijs in 2026: why I chose the rendering library the browser rendering and simulation decision behind a water-heavy seafaring game. 2024 · 03 ship fast for windows: the microsoft store playbook a practical modernization and release workflow from the real delivery lane.
all writing — blog.ryanspice.com

link policy. every selected post links to a confirmed canonical article route in the blog repository.

curriculum vitae updated 2026-09-08

the complete chronology exists — it just doesn't need to live here

the homepage establishes the argument; the cv carries the role-by-role detail. one stable cross-role version supports the current search, with tailored copies emphasizing the stack a specific role actually needs.

Ryan Spice-Finnie · Senior Software Engineer

12+ years across frontend architecture, full-stack delivery, modernization, accessibility, cloud/platform work, technical leadership and current multi-model AI orchestration.

React / Node Angular / AODA SvelteKit Shopify / Cloudflare Platform architecture Applied AI
view complete cv download pdf prototype routes: these point to the intended production locations; the standalone local file does not contain those route assets yet.
contact no forms · no tracking

the fastest route is plain email

for senior/staff frontend & platform, senior full-stack or hands-on technical leadership roles — or to check a claim on this page — email is the fastest route.

github
github.com/ryanspice
linkedin
linkedin.com/in/ryan-spice-finnie-510a295b
location
ontario, canada — toronto hybrid · canada-remote
response
usually within two business days