Forsyth Famous

Forsyth Famous

I build infrastructure that shows its own working: every change is proposed, gated, then committed. This site runs that way. The diagram is its pipeline, live.

  • Kraków, Poland
  • Azure
  • Google Cloud
  • Firebase

→ read how this site runs

live · this site's pipeline

3/3 sources healthy · built · edge checking…

How this site is built and servedCICase-study agentscheduled · PR-gatedEXTGitHub API423 contributions / yrEXTdev.to API6 recent articlesSVCportfolio repomain @ 18436cdCIDeploy workflowrun #5 · successEDGECloudflare Pageschecking…CLIYouthis browserHow this site is built and servedCICase-study agentscheduled · PR-gatedEXTGitHub API423 contributions / yrEXTdev.to API6 recent articlesSVCportfolio repomain @ 18436cdCIDeploy workflowrun #5 · successEDGECloudflare Pageschecking…CLIYouthis browser
Pushes and a nightly schedule run the deploy workflow, which pulls from the GitHub and dev.to APIs and ships to Cloudflare Pages. The case-study agent can only propose changes through a reviewed pull request.
View as table
ComponentKindTechnologyFlows out
Case-study agentpipelinescheduled · PR-gated⇢ portfolio repo: pull request, merged only after review
GitHub APIexternal service423 contributions / yr→ Deploy workflow: repos, upstream PRs, contributions
dev.to APIexternal service6 recent articles→ Deploy workflow: articles
portfolio reposervicemain @ 18436cd⇢ Deploy workflow: push to main
Deploy workflowpipelinerun #5 · success⇢ Cloudflare Pages: deploy build + status.json
Cloudflare Pagesedgechecking…→ You: pages
Youclientthis browser→ Cloudflare Pages: live status check

Propose · Gate · Commit

The rule behind everything below: nothing changes a system directly.

  1. Propose

    Anything that wants to change the system produces a proposal, never the change itself: a model drafting a ledger entry, an agent drafting a case study, a release tag asking to go to production.

    KONTA: the model drafts, never writes →

  2. Gate

    A person or a check that cannot be skipped decides: a confirmation, a reviewed pull request, a deploy script that refuses the wrong project or an untagged commit.

    JahUs: guarded production deploys →

  3. Commit

    Only deterministic code applies an approved change, atomically and idempotently, and the result is verified afterwards rather than assumed.

    This site: agent drafts merge by PR →

Selected work

Each one: the architecture, the decisions and what they cost, how it fails, and the evidence.

About

Portrait of Forsyth Famous

I'm a cloud infrastructure and DevOps engineer in Kraków with 6+ years in tech. I keep Azure and AWS platforms for large enterprise customers secure and running: managing access and governance, resolving incidents, and automating the manual work that slows teams down.

I'm a Microsoft Certified DevOps Engineer Expert, Azure Network Engineer and Azure Administrator.

In my own projects I go deeper into the engineering: systems that stay correct when a message arrives twice, deployments that refuse the wrong target, and changes that only ship after review. The case studies above show how I work.

AZ-400 ↗AZ-700 ↗AZ-104 ↗

9 Microsoft Applied Skills

Upstream

Changes to other people's tools, synced from GitHub.

Notes

Step-by-step guides, synced from dev.to.

All notes on dev.to ↗

Elsewhere