Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Sandbox/RainbowFork/Prod/Unicorn/ColourModel/3.0.0

From OHC Network Wiki
Revision as of 11:04, 6 July 2026 by Admin (talk | contribs) (Automated edit (via create-page on MediaWiki MCP Server))
(diff) ← Older revision | Latest revision (diff) | Newer revision β†’ (diff)
🧊 You are viewing documentation frozen at CARE 4.0. For the latest version see Sandbox/RainbowFork/Prod/Unicorn/ColourModel.
guideCARE 3.0 – 4.0


⚠️ Warning
🧊 This is a frozen snapshot of the Unicorn ColourModel after its first upstream sync. The canonical (latest) version is at Unicorn ColourModel.

Dev released v2.0.0 "Tech Disruption". Unicorn panicked, then got to work. They evaluated every single change and decided what to adopt, what to decline, and what to keep.

Sync evaluation: Dev v1.0.0 β†’ Dev v2.0.0

Change Decision Rationale
colour_1: String β†’ Integer βœ… ADOPT 0xFF0000 is objectively better than "Red"
colour_2: πŸ—‘οΈ deleted ❌ DECLINE "UNICORNS LOVE ORANGE. IT STAYS." 🦒
colour_4: String β†’ Boolean ❌ DECLINE Green is not a yes/no question
colour_6: String β†’ Float ❌ DECLINE Unicorns don't do nanometres
colour_7: πŸ—‘οΈ deleted ❌ DECLINE "Violet deserves better. Violet stays."
fave_colour: NEW βœ… ADOPT Everyone needs a favourite
energy: NEW βœ… ADOPT Physics is cool
Custom fields πŸ›‘οΈ PRESERVED Upstream doesn't know they exist β€” immune

Fields

Field Type Origin
colour_1 Integer Synced from Dev v2.0.0
colour_2 String Kept β€” declined upstream deletion
colour_3 String Unchanged
colour_4 String Kept β€” declined type change to Boolean
colour_5 String Unchanged
colour_6 String Kept β€” declined type change to Float
colour_7 String Kept β€” declined upstream deletion
fave_colour String Synced from Dev v2.0.0
energy Float Synced from Dev v2.0.0
sparkle_level Integer Custom β€” 1-10
glitter_mode Boolean Custom
unicorn_power Float Custom β€” mega-sparkles

What happened to custom fields during sync?

Nothing. The sync only touched fields that changed upstream. Custom fields (sparkle_level, glitter_mode, unicorn_power) don't exist upstream, so they never appeared in the diff. They were never at risk. They just kept working.

This is the superpower of wiki-based forking: each fork is its own page, its own reality, with zero automated merge conflicts.