XGH -OS
- 01
The Architecture Canvas has 4 layers. XGH-OS uses one and a half.
End-User with everything inside: screens, blocks, server actions, entities, REST integrations. Foundation is where Static Entities go when nobody knew where else to put them. Core is a word XGH-OS has read but does not use. Discovery is opened once to admire the arrow spaghetti — after that, only in client presentations.
- 02
Aggregate inside For Each is the heartbeat of XGH-OS.
Documentation has been screaming “aggregate or SQL query inside a cycle” for over a decade. AI Mentor flags it red. Architecture Dashboard counts it. The XGH-OS dev 1-CPs anyway. The N+1 problem is not a bug — it is an aesthetic choice.
- 03
Refresh References. Re-1-CP. Repeat.
“Outdated Producer” → Refresh All → 1-CP → “Outdated Producer” → Refresh All → 1-CP. If it loops, there is a circular reference between modules — the XGH-OS solution: accept it and move on. The loop is the method.
- 04
When the IN operator does not exist, XGH-OS concatenates strings with #.
The Idea to add IN to Aggregates has 500+ likes since 2015. XGH-OS has accepted it will never ship and goes with Index("#"+String_Join.Text+"#", "#"+Entity.Id+"#") <> -1. Performance is a problem for the Aurora optimizer.
- 05
If StatusId = 1: XGH-OS does not memorise Static Entity names.
Static Entities exist precisely to avoid magic numbers in code. XGH-OS respects the principle: it does not use magic numbers, it uses magic Ids. Everyone knows 1 means “Pending”, right? And 7 means “Cancelled”. Except in PROD, where 7 is “Approved” because someone renumbered them in 2019 and nobody updated the 47 IFs scattered across modules.
- 06
Every large Server Action in XGH-OS ends in FinalResult2.
Aux, Aux2, Temp, Temp_OK, X, Y, Result, Result2, FinalResult, FinalResult_REAL, FinalResult_FINAL, FinalResult_USE_THIS_ONE. Naming is a privilege for those with time. XGH-OS has a deadline.
- 07
Site Property is the global variable of XGH-OS.
Configure something without a deploy? Site Property. Pass a value between Timer and Screen? Site Property. Store the last processed Id to resume tomorrow? Site Property. Feature flag? Site Property. Service Center → Site Properties → Edit Value is the hidden admin panel of the company.
- 08
TrueChange has three colours. AI Mentor makes suggestions. XGH-OS closes the tab.
Red does not 1-CP. Yellow 1-CPs. The 247 yellow warnings are part of the Service Studio theme. “Avoid Aggregate inside cycle.” “Cyclic reference detected.” “Avoid large session variables.” Suggestion. Suggestion. Suggestion.
- 09
If the Last Modified By is not yours, the bug is not yours either.
XGH-OS’s first move on a production exception: open the Server Action, check the Last Modified By in the properties panel, read the name. If it is a teammate — close Service Studio. If it is someone who already left the company — close it faster. AI Mentor has the same workflow: open the finding, see the module, see the owning team, and if it is not yours, Suppress. Last Modified By is the XGH-OS git blame. And the alibi.
- 10
Forge is open source: download, copy, forget the author.
A 2018 component, no Reactive version, author left the company in 2020? Download the .oap, decompile it, copy the JavaScript out of the Web Block, paste it into your own module. “We customised it to our reality.” (And it broke on the ODC upgrade — but that is next quarter’s problem.)
- 11
1-CP to production is a form of courage.
LifeTime exists. Deployment Zones exist. Approvals exist. XGH-OS knows this and also knows that you only need to switch the environment in the bottom corner of Service Studio for 1-CP to target PROD directly. “It is just an urgent hotfix.” “It is just a Site Property.” “It is just a Static Entity.” Who has not done it? If you answered “me”, congratulations — you are not XGH-OS, you are a manager.
- 12
Audit log? Service Center is our Datadog.
The OSLOG_GENERAL table grows by 4 GB per month. LogMessage("got here") is the only instrumentation. Observability dashboards are bought in Q4 and abandoned in Q1. When a customer reports a production bug, you open Service Center, filter by approximate time, and pray the log is there.
- 13
ODC migration: everything in sprint 1, and that was it.
Traditional Web no longer exists — rewrite it in Reactive. SQL Server became Aurora PostgreSQL — rewrite the queries (case-insensitive is no longer the default — good luck). SOAP turned into REST — rewrite the integrations. XGH-OS estimate: “about two weeks”. Reality: 9 months, two resignations, and a 47-page post-mortem.