docs: replace remaining Portfolio with Umbrella

Author: huan

jekyll/_posts/2025-11-29-vibe-coding-cloud-protocol.md

@@ -198,20 +198,20 @@ The names barely change—mostly `shipfail` → `preangel`—but the Project mov
 
 A naming convention is useless if you have to look it up every time. It needs to be intuitive. Here is the **Ship.Fail Protocol**.
 
-### Rule #1: The Portfolio
+### Rule #1: The Umbrella
 
-I have exactly three Portfolios (contexts). No more, no less.
+I have exactly three Umbrellas (contexts). No more, no less.
 
-* `pf-preangel` (Real products making money)
-* `pf-shipfail` (Hackathons, MVPs, crazy ideas)
-* `pf-tobemigrated` (The "Box of Shame" for old stuff)
+* `umb-preangel` (Real products making money)
+* `umb-shipfail` (Hackathons, MVPs, crazy ideas)
+* `umb-tobemigrated` (The "Box of Shame" for old stuff)
 
 ### Rule #2: The Project
 
 Projects are the atomic unit in my head. They are named explicitly:
 
 ```text
-prj-<portfolio>-<project>
+prj-<umbrella>-<project>
 ```
 
 Examples:
@@ -238,7 +238,7 @@ How this plays out in practice:
 This is where the magic happens. The Resource Group name encodes the entire lineage of the resource.
 
 ```text
-rg-<portfolio>-<project>-<stage>-<component?>
+rg-<umbrella>-<project>-<stage>-<component?>
 ```
 
 Examples:
@@ -249,7 +249,7 @@ Examples:
 Under Ship.Fail, this is also how Projects show up structurally:
 
 * `rg-shipfail-remic-dev-web`, `rg-shipfail-remic-dev-api`, `rg-shipfail-remic-prod-web`, ...
-* All of them live inside the **same Ship.Fail lab subscription**, but their names and tags still encode Portfolio, Project, Stage, and Component.
+* All of them live inside the **same Ship.Fail lab subscription**, but their names and tags still encode Umbrella, Project, Stage, and Component.
 
 **The "3-Second Rule":** If I can't tell you exactly what a Resource Group contains and who pays for it within 3 seconds of reading the name, **it is a bad name.**
 
@@ -258,7 +258,7 @@ Under Ship.Fail, this is also how Projects show up structurally:
 I use type‑first naming. Start with the resource type abbreviation, then echo the hierarchy.
 
 ```text
-<shorttype>-<portfolio>-<project>-<stage>-<component?>
+<shorttype>-<umbrella>-<project>-<stage>-<component?>
 ```
 
 Examples:
@@ -291,7 +291,7 @@ Three months later, I have *no idea* what either of those are.
 Resource Group: rg-shipfail-remic-dev-web
 Storage Account: st-shipfail-remic-dev-web
 Tags:
-  Portfolio = ShipFail
+  Umbrella  = ShipFail
   Project   = ReMic
   Stage     = dev
   Component = web
@@ -300,7 +300,7 @@ Tags:
 Now the same pair of resources tells me, at a glance:
 
 * this is part of the **ReMic** Project,
-* under the **Ship.Fail** portfolio,
+* under the **Ship.Fail** umbrella,
 * in the **dev** stage,
 * in the **web** component.
 
@@ -396,126 +396,11 @@ In practice, “graduation” often means **redeploying infrastructure using IaC
 
 The mental model is the same. The only changes are:
 
-* `Portfolio` value: from `ShipFail` → `PreAngel`.
-* Physical level where the Project lives: from Resource Group family inside a shared subscription → its own subscription.
-
 * `Umbrella` value: from `ShipFail` → `PreAngel`.
 * Physical level where the Project lives: from Resource Group family inside a shared subscription → its own subscription.
 
 That’s how graduation works in this protocol.
 
----
-
-## 4. The Naming Playbook: Rules for the Road
-
-A naming convention is useless if you have to look it up every time. It needs to be intuitive. Here is the **Ship.Fail Protocol**.
-
-### Rule #1: The Umbrella
-
-I have exactly three Umbrellas (contexts). No more, no less.
-
-* `umb-preangel` (Real products making money)
-* `umb-shipfail` (Hackathons, MVPs, crazy ideas)
-* `umb-tobemigrated` (The "Box of Shame" for old stuff)
-
-### Rule #2: The Project
-
-Projects are the atomic unit in my head. They are named explicitly:
-
-```text
-prj-<umbrella>-<project>
-```
-
-Examples:
-
-* `prj-preangel-zixia`
-* `prj-shipfail-thoth`
-* `prj-shipfail-remic`
-
-How this plays out in practice:
-
-* In **PreAngel**, `prj-preangel-zixia` is both:
-
-  * the conceptual Project name, and
-  * the name I give to its dedicated Azure (subscription).
-* In **Ship.Fail**, `prj-shipfail-remic` is still the conceptual Project name, but:
-
-  * all Ship.Fail Projects share a single lab Azure (subscription), and
-  * the Project is implemented as a **family of Resource Groups and tags** with the `shipfail-remic` pattern.
-
-**Why this works:** When I see `prj-shipfail-thoth`, I know instantly: *This is an experiment (Ship.Fail) called Thoth.* Whether it currently lives as its own subscription (PreAngel style) or as Resource Groups inside the lab subscription (Ship.Fail style) is an implementation detail I can always look up—but the name and tags tell the story.
-
-### Rule #3: The Resource Group (The Backbone)
-
-This is where the magic happens. The Resource Group name encodes the entire lineage of the resource.
-
-```text
-rg-<umbrella>-<project>-<stage>-<component?>
-```
-
-Examples:
-
-* `rg-shipfail-remic-dev-web`
-* `rg-preangel-zixia-prod-data`
-
-Under Ship.Fail, this is also how Projects show up structurally:
-
-* `rg-shipfail-remic-dev-web`, `rg-shipfail-remic-dev-api`, `rg-shipfail-remic-prod-web`, ...
-* All of them live inside the **same Ship.Fail lab subscription**, but their names and tags still encode Umbrella, Project, Stage, and Component.
-
-**The "3-Second Rule":** If I can't tell you exactly what a Resource Group contains and who pays for it within 3 seconds of reading the name, **it is a bad name.**
-
-### Rule #4: The Resource (Type-First)
-
-I use type‑first naming. Start with the resource type abbreviation, then echo the hierarchy.
-
-```text
-<shorttype>-<umbrella>-<project>-<stage>-<component?>
-```
-
-Examples:
-
-* `vm-shipfail-remic-dev-web` (A VM)
-* `st-shipfail-thoth-dev-data` (A Storage Account)
-* `fn-preangel-zixia-prod-web` (A Function App)
-* `db-preangel-zixia-prod-api` (A Database)
-
-Type-first gives me a nice property when I sort by name:
-
-* all `vm-*` resources group together,
-* all `db-*` resources group together,
-* and my eyes can skim quickly.
-
-### A Before → After Rename Example
-
-Here’s how this looks in practice on a messy real-world example.
-
-**Before:**
-
-* Resource Group: `Default-Web-WestUS`
-* Storage Account: `mystorage123`
-
-Three months later, I have *no idea* what either of those are.
-
-**After:**
-
-```text
-Resource Group: rg-shipfail-remic-dev-web
-Storage Account: st-shipfail-remic-dev-web
-Tags:
-  Umbrella  = ShipFail
-  Project   = ReMic
-  Stage     = dev
-  Component = web
-```
-
-Now the same pair of resources tells me, at a glance:
-
-* this is part of the **ReMic** Project,
-* under the **Ship.Fail** umbrella,
-* in the **dev** stage,
-* in the **web** component.
-
 ### 6.3 Zixia as a PreAngel Project (Always Production-First)
 
 The **PreAngel** umbrella is where my “serious” products live. Zixia is one of them.