research: reconstruct Eldorado organization with sourced roles and explicit assumptions
Build and publish Eldorado documentation / build (pull_request) Successful in 30s

This commit is contained in:
jarvis-at-skic committed 2026-10-02 12:12:57 +00:00
1 parent 0af096a285
commit c2665624e3
9 files changed
+792 -51

No files matched your search

+170 -30
View File
@@ -2,22 +2,32 @@
"schema_version": 1,
"diagram_type": "architecture",
"meta": {
"title": "Illustrative organization structure",
"title": "Eldorado — departments and team evidence",
"output": "static/diagrams/organization-structure/index.html",
"quality_profile": "showcase"
"quality_profile": "showcase",
"legend": {
"entries": {
"backend": {
"label": "E: evidenced function"
},
"frontend": {
"label": "J: advertised role"
}
}
}
},
"components": [
{
"id": "leadership",
"id": "management",
"type": "backend",
"label": "Example leadership",
"sublabel": "Illustrative only",
"label": "Management",
"sublabel": "E: CEO / COO named [1]",
"pos": [
320,
660,
40
],
"size": [
200,
320,
80
]
},
@@ -25,27 +35,27 @@
"id": "product",
"type": "backend",
"label": "Product",
"sublabel": "Example function",
"sublabel": "E: careers category [4]",
"pos": [
40,
260
280
],
"size": [
200,
240,
80
]
},
{
"id": "engineering",
"id": "technology",
"type": "backend",
"label": "Engineering",
"sublabel": "Example function",
"label": "Technology",
"sublabel": "E: careers category [4]",
"pos": [
320,
260
280
],
"size": [
200,
240,
80
]
},
@@ -53,41 +63,171 @@
"id": "operations",
"type": "backend",
"label": "Operations",
"sublabel": "Example function",
"sublabel": "E: careers category [4]",
"pos": [
600,
260
280
],
"size": [
200,
240,
80
]
},
{
"id": "marketing",
"type": "backend",
"label": "Marketing",
"sublabel": "E: careers category [4]",
"pos": [
880,
280
],
"size": [
240,
80
]
},
{
"id": "finance",
"type": "backend",
"label": "Finance & Accounting",
"sublabel": "E: careers category [4]",
"pos": [
1160,
280
],
"size": [
240,
80
]
},
{
"id": "people",
"type": "backend",
"label": "HR & Administration",
"sublabel": "E: careers category [4]",
"pos": [
1440,
280
],
"size": [
240,
80
]
}
],
"connections": [
{
"id": "leadership-product",
"from": "leadership",
"to": "product"
"id": "management-product",
"from": "management",
"to": "product",
"label": "A: placement",
"variant": "dashed"
},
{
"id": "leadership-engineering",
"from": "leadership",
"to": "engineering"
"id": "management-technology",
"from": "management",
"to": "technology",
"label": "A: placement",
"variant": "dashed"
},
{
"id": "leadership-operations",
"from": "leadership",
"to": "operations"
"id": "management-operations",
"from": "management",
"to": "operations",
"label": "A: placement",
"variant": "dashed"
},
{
"id": "management-marketing",
"from": "management",
"to": "marketing",
"label": "A: placement",
"variant": "dashed"
},
{
"id": "management-finance",
"from": "management",
"to": "finance",
"label": "A: placement",
"variant": "dashed"
},
{
"id": "management-people",
"from": "management",
"to": "people",
"label": "A: placement",
"variant": "dashed"
}
],
"cards": [
{
"dot": "amber",
"title": "Test diagram \u2014 not a confirmed structure",
"title": "Not a verified employee roster — 2026-10-02",
"items": [
"All roles and relationships are illustrative.",
"Actual Eldorado teams and reporting lines remain to be defined."
"E = evidenced team/function; J = job-advertised; A = assumed.",
"All dashed department placements are planning assumptions.",
"Source numbers refer to the Structure page; vacancies do not prove occupancy."
]
},
{
"dot": "cyan",
"title": "Product",
"items": [
"E: Order/Orders; Categories design [13,14]",
"E: Data Team / J: ranking role [9]",
"J: seller-platform domain [15]",
"A: Sellers & Operations squad"
]
},
{
"dot": "amber",
"title": "Technology",
"items": [
"J: engineering management chain [6,7]",
"J: AI Architect — solo start [8]",
"J: IT Engineer; Technical Architect [8,10]",
"A: platform/reliability capability group"
]
},
{
"dot": "cyan",
"title": "Operations",
"items": [
"E: Customer Support [11]",
"E: Trust & Resolution; Risk & Fraud [11]",
"J: operational QA directly to COO [11]",
"A: wider COO ownership/lead escalation"
]
},
{
"dot": "amber",
"title": "Marketing",
"items": [
"J: Brand Lead directly to CMO [12]",
"E: Creative; SEO; PPC & Affiliate [12]",
"E: Influencer; CRM; community [12]",
"A: separate workstream boundaries"
]
},
{
"dot": "cyan",
"title": "Finance & Accounting",
"items": [
"E: Finance team [5]",
"J: CFO hiring mandate [5]",
"A: FP&A; Accounting/Tax/Controls",
"A: Treasury / Payment Operations"
]
},
{
"dot": "amber",
"title": "HR & Administration",
"items": [
"E: Talent Acquisition [16]",
"A: People Operations",
"A: Office / Administration",
"A: HR leadership reporting line"
]
}
]