<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>cilly — Architecture Notes (EN)</title><description>RSS feed of articles on engineering and design philosophy.</description><link>https://cilly-yllic.github.io/</link><language>en</language><item><title>Generating every Firebase layer’s types from a single contract.yml</title><link>https://cilly-yllic.github.io/en/notes/firebase-gcp/contract-driven-firebase-codegen/</link><guid isPermaLink="true">https://cilly-yllic.github.io/en/notes/firebase-gcp/contract-driven-firebase-codegen/</guid><description>Structurally eliminating the drift of maintaining the same model across Data Connect, Firestore, Zod, and API DTOs, with code generation from a YAML contract as the single source of truth.</description><pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate><category>firebase-gcp</category></item><item><title>Enforce with config, not attention — scope and permission guardrails for coding agents</title><link>https://cilly-yllic.github.io/en/notes/ai-agents/scope-and-permission-guardrails-for-coding-agents/</link><guid isPermaLink="true">https://cilly-yllic.github.io/en/notes/ai-agents/scope-and-permission-guardrails-for-coding-agents/</guid><description>Enforcing multi-repository AI agent work through declared scopes and permissions: per-session guardrail design, a self-restraint that keeps the agent away from its own permission definitions, and a double lock on push.</description><pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate><category>ai-agents</category></item><item><title>Syncing what comes after provisioning — Cloudflare DNS, Logto, cert-gated proxy, env bundles</title><link>https://cilly-yllic.github.io/en/notes/firebase-gcp/platform-sync-dns-logto-proxy-env/</link><guid isPermaLink="true">https://cilly-yllic.github.io/en/notes/firebase-gcp/platform-sync-dns-logto-proxy-env/</guid><description>The design of a CI pipeline that keeps DNS, auth, delivery certificates, and env values — everything left over after config-driven GCP / Firebase provisioning — following the same source of truth.</description><pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate><category>firebase-gcp</category></item><item><title>Provisioning GCP / Firebase environments from a single settings.yml</title><link>https://cilly-yllic.github.io/en/notes/firebase-gcp/config-driven-gcp-firebase-provisioning/</link><guid isPermaLink="true">https://cilly-yllic.github.io/en/notes/firebase-gcp/config-driven-gcp-firebase-provisioning/</guid><description>The design of a platform that chains GCP project creation through Firebase setup, keyless, with a per-service settings file as the source of truth.</description><pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate><category>firebase-gcp</category></item><item><title>Runtime and delivery of a multi-service Firebase environment</title><link>https://cilly-yllic.github.io/en/notes/firebase-gcp/multi-service-firebase-runtime-and-delivery/</link><guid isPermaLink="true">https://cilly-yllic.github.io/en/notes/firebase-gcp/multi-service-firebase-runtime-and-delivery/</guid><description>A development environment with multiple services sharing one GCP project, presented through two cross-sections: how it runs (runtime) and how it ships (delivery).</description><pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate><category>firebase-gcp</category></item><item><title>Treating Firestore as a public cache</title><link>https://cilly-yllic.github.io/en/notes/firebase-gcp/firestore-as-public-cache/</link><guid isPermaLink="true">https://cilly-yllic.github.io/en/notes/firebase-gcp/firestore-as-public-cache/</guid><description>The design benefits — and the costs — that come into view when Cloud SQL is the source of truth and Firestore is a read-optimized projection.</description><pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate><category>firebase-gcp</category></item></channel></rss>