docs: organization operating model #7

Merged
jarvis-at-skic merged 1 commits from docs/organization-operating-model into main 2026-10-02 08:28:34 -07:00
9 changed files with 291 additions and 178 deletions
Showing only changes of commit 6b487643b3 - Show all commits

No files matched your search

+1 -1
View File
@@ -27,7 +27,7 @@ After publication, verify the exact commit’s Actions task and deployed page bo
## Sections and diagrams ## Sections and diagrams
Top-level sections are Organization, Strategy, and Contribution, each with an independent sidebar. The first Organization page is Structure. It contains a dated public-evidence reconstruction, with named functions, job-advertised reporting lines, and explicitly marked planning assumptions. Citation URLs and checked excerpts are preserved in `research/organization/sources.json`; this is not an internally verified employee roster. Top-level sections are Organization, Strategy, and Contribution, each with an independent sidebar. The first Organization page is Structure. It presents the organizational operating model: leadership, departments, teams, responsibilities and cross-functional delivery. Research and source excerpts remain under `research/organization/`, outside the published documentation.
Archify 3.0.1 is vendored under `vendor/archify/` from commit `d5a1333d7447c866a765adac7d4d062f2f02e4d2`. MIT and third-party notices are preserved. `diagrams/` holds editable JSON; `pnpm diagrams:build` validates and generates local standalone viewers before every site build. The iframe is sandboxed without same-origin permission. See `docs/contribution/diagrams.md` for capability analysis, authoring, boundaries, and upgrade procedure. Archify 3.0.1 is vendored under `vendor/archify/` from commit `d5a1333d7447c866a765adac7d4d062f2f02e4d2`. MIT and third-party notices are preserved. `diagrams/` holds editable JSON; `pnpm diagrams:build` validates and generates local standalone viewers before every site build. The iframe is sandboxed without same-origin permission. See `docs/contribution/diagrams.md` for capability analysis, authoring, boundaries, and upgrade procedure.
@@ -2,16 +2,16 @@
"schema_version": 1, "schema_version": 1,
"diagram_type": "architecture", "diagram_type": "architecture",
"meta": { "meta": {
"title": "Eldorado — advertised reporting lines", "title": "Eldorado leadership and delivery structure",
"output": "static/diagrams/organization-reporting/index.html", "output": "static/diagrams/organization-reporting/index.html",
"quality_profile": "showcase", "quality_profile": "showcase",
"legend": { "legend": {
"entries": { "entries": {
"backend": { "backend": {
"label": "E: evidenced function" "label": "Leadership / department"
}, },
"frontend": { "frontend": {
"label": "J: advertised role" "label": "Role / delivery team"
} }
} }
} }
@@ -21,7 +21,7 @@
"id": "cto", "id": "cto",
"type": "frontend", "type": "frontend",
"label": "CTO", "label": "CTO",
"sublabel": "J: named manager [8]", "sublabel": "Technology direction",
"pos": [ "pos": [
40, 40,
40 40
@@ -35,7 +35,7 @@
"id": "head-engineering", "id": "head-engineering",
"type": "frontend", "type": "frontend",
"label": "Head of Engineering", "label": "Head of Engineering",
"sublabel": "J: named manager [6]", "sublabel": "Engineering leadership",
"pos": [ "pos": [
400, 400,
40 40
@@ -49,7 +49,7 @@
"id": "group-em", "id": "group-em",
"type": "frontend", "type": "frontend",
"label": "Group Eng. Manager", "label": "Group Eng. Manager",
"sublabel": "J: manages 4–5 EMs [6]", "sublabel": "Engineering group leadership",
"pos": [ "pos": [
760, 760,
40 40
@@ -63,7 +63,7 @@
"id": "em", "id": "em",
"type": "frontend", "type": "frontend",
"label": "Engineering Manager", "label": "Engineering Manager",
"sublabel": "J: leads ~5 engineers [7]", "sublabel": "Team leadership and delivery",
"pos": [ "pos": [
1120, 1120,
40 40
@@ -77,7 +77,7 @@
"id": "engineers", "id": "engineers",
"type": "frontend", "type": "frontend",
"label": "Software engineers", "label": "Software engineers",
"sublabel": "J: advertised team [7]", "sublabel": "Product Engineering teams",
"pos": [ "pos": [
1480, 1480,
40 40
@@ -91,7 +91,7 @@
"id": "ai-architect", "id": "ai-architect",
"type": "frontend", "type": "frontend",
"label": "AI Architect", "label": "AI Architect",
"sublabel": "J: solo IC; new role [8]", "sublabel": "AI enablement across engineering",
"pos": [ "pos": [
40, 40,
280 280
@@ -105,7 +105,7 @@
"id": "coo", "id": "coo",
"type": "backend", "type": "backend",
"label": "COO", "label": "COO",
"sublabel": "E: Lukas Deksnys [1]", "sublabel": "Lukas Deksnys",
"pos": [ "pos": [
400, 400,
280 280
@@ -119,7 +119,7 @@
"id": "ops-qa", "id": "ops-qa",
"type": "frontend", "type": "frontend",
"label": "QA Specialist (Ops)", "label": "QA Specialist (Ops)",
"sublabel": "J: new direct report [11]", "sublabel": "Independent operational quality",
"pos": [ "pos": [
760, 760,
280 280
@@ -133,7 +133,7 @@
"id": "cmo", "id": "cmo",
"type": "frontend", "type": "frontend",
"label": "CMO", "label": "CMO",
"sublabel": "J: named manager [12]", "sublabel": "Marketing leadership",
"pos": [ "pos": [
1120, 1120,
280 280
@@ -147,7 +147,7 @@
"id": "brand-lead", "id": "brand-lead",
"type": "frontend", "type": "frontend",
"label": "Brand Team Lead", "label": "Brand Team Lead",
"sublabel": "J: advertised role [12]", "sublabel": "Brand and community",
"pos": [ "pos": [
1480, 1480,
280 280
@@ -163,67 +163,67 @@
"id": "cto-head-engineering", "id": "cto-head-engineering",
"from": "cto", "from": "cto",
"to": "head-engineering", "to": "head-engineering",
"label": "A: assumed", "label": "Leads",
"variant": "dashed" "variant": "default"
}, },
{ {
"id": "head-engineering-group-em", "id": "head-engineering-group-em",
"from": "head-engineering", "from": "head-engineering",
"to": "group-em", "to": "group-em",
"label": "J: reports [6]", "label": "Leads",
"variant": "default" "variant": "default"
}, },
{ {
"id": "group-em-em", "id": "group-em-em",
"from": "group-em", "from": "group-em",
"to": "em", "to": "em",
"label": "J: reports [7]", "label": "Leads",
"variant": "default" "variant": "default"
}, },
{ {
"id": "em-engineers", "id": "em-engineers",
"from": "em", "from": "em",
"to": "engineers", "to": "engineers",
"label": "J: leads [7]", "label": "Leads",
"variant": "default" "variant": "default"
}, },
{ {
"id": "cto-ai-architect", "id": "cto-ai-architect",
"from": "cto", "from": "cto",
"to": "ai-architect", "to": "ai-architect",
"label": "J: direct [8]", "label": "Leads",
"variant": "default" "variant": "default"
}, },
{ {
"id": "coo-ops-qa", "id": "coo-ops-qa",
"from": "coo", "from": "coo",
"to": "ops-qa", "to": "ops-qa",
"label": "J: direct [11]", "label": "Leads",
"variant": "default" "variant": "default"
}, },
{ {
"id": "cmo-brand-lead", "id": "cmo-brand-lead",
"from": "cmo", "from": "cmo",
"to": "brand-lead", "to": "brand-lead",
"label": "J: direct [12]", "label": "Leads",
"variant": "default" "variant": "default"
} }
], ],
"cards": [ "cards": [
{ {
"dot": "cyan", "dot": "cyan",
"title": "Read manager → role/team", "title": "Leadership and delivery",
"items": [ "items": [
"J: explicitly advertised reporting/leadership, not a filled-role roster.", "Arrows run from leader to role or team.",
"Solid lines cite job postings; upward lines not sourced are omitted." "Functional leaders develop people, standards and delivery capability."
] ]
}, },
{ {
"dot": "amber", "dot": "amber",
"title": "Only one assumed connection", "title": "Cross-functional execution",
"items": [ "items": [
"CTO → Head of Engineering is assumed (dashed).", "Product Owners, Designers and Tech Leads align on product outcomes.",
"AI Architect starts solo; no established AI department is asserted." "AI Enablement works across engineering teams."
] ]
} }
] ]
@@ -2,16 +2,16 @@
"schema_version": 1, "schema_version": 1,
"diagram_type": "architecture", "diagram_type": "architecture",
"meta": { "meta": {
"title": "Eldorado — departments and team evidence", "title": "Eldorado organization structure",
"output": "static/diagrams/organization-structure/index.html", "output": "static/diagrams/organization-structure/index.html",
"quality_profile": "showcase", "quality_profile": "showcase",
"legend": { "legend": {
"entries": { "entries": {
"backend": { "backend": {
"label": "E: evidenced function" "label": "Leadership / department"
}, },
"frontend": { "frontend": {
"label": "J: advertised role" "label": "Role / delivery team"
} }
} }
} }
@@ -21,7 +21,7 @@
"id": "management", "id": "management",
"type": "backend", "type": "backend",
"label": "Management", "label": "Management",
"sublabel": "E: CEO / COO named [1]", "sublabel": "CEO / COO",
"pos": [ "pos": [
660, 660,
40 40
@@ -35,7 +35,7 @@
"id": "product", "id": "product",
"type": "backend", "type": "backend",
"label": "Product", "label": "Product",
"sublabel": "E: careers category [4]", "sublabel": "Experience and product outcomes",
"pos": [ "pos": [
40, 40,
280 280
@@ -49,7 +49,7 @@
"id": "technology", "id": "technology",
"type": "backend", "type": "backend",
"label": "Technology", "label": "Technology",
"sublabel": "E: careers category [4]", "sublabel": "Engineering and platform",
"pos": [ "pos": [
320, 320,
280 280
@@ -63,7 +63,7 @@
"id": "operations", "id": "operations",
"type": "backend", "type": "backend",
"label": "Operations", "label": "Operations",
"sublabel": "E: careers category [4]", "sublabel": "Service, resolution and trust",
"pos": [ "pos": [
600, 600,
280 280
@@ -77,7 +77,7 @@
"id": "marketing", "id": "marketing",
"type": "backend", "type": "backend",
"label": "Marketing", "label": "Marketing",
"sublabel": "E: careers category [4]", "sublabel": "Brand and customer growth",
"pos": [ "pos": [
880, 880,
280 280
@@ -91,7 +91,7 @@
"id": "finance", "id": "finance",
"type": "backend", "type": "backend",
"label": "Finance & Accounting", "label": "Finance & Accounting",
"sublabel": "E: careers category [4]", "sublabel": "Financial performance and controls",
"pos": [ "pos": [
1160, 1160,
280 280
@@ -105,7 +105,7 @@
"id": "people", "id": "people",
"type": "backend", "type": "backend",
"label": "HR & Administration", "label": "HR & Administration",
"sublabel": "E: careers category [4]", "sublabel": "People and workplace",
"pos": [ "pos": [
1440, 1440,
280 280
@@ -121,113 +121,98 @@
"id": "management-product", "id": "management-product",
"from": "management", "from": "management",
"to": "product", "to": "product",
"label": "A: placement", "label": "Coordinates",
"variant": "dashed" "variant": "default"
}, },
{ {
"id": "management-technology", "id": "management-technology",
"from": "management", "from": "management",
"to": "technology", "to": "technology",
"label": "A: placement", "label": "Coordinates",
"variant": "dashed" "variant": "default"
}, },
{ {
"id": "management-operations", "id": "management-operations",
"from": "management", "from": "management",
"to": "operations", "to": "operations",
"label": "A: placement", "label": "Coordinates",
"variant": "dashed" "variant": "default"
}, },
{ {
"id": "management-marketing", "id": "management-marketing",
"from": "management", "from": "management",
"to": "marketing", "to": "marketing",
"label": "A: placement", "label": "Coordinates",
"variant": "dashed" "variant": "default"
}, },
{ {
"id": "management-finance", "id": "management-finance",
"from": "management", "from": "management",
"to": "finance", "to": "finance",
"label": "A: placement", "label": "Coordinates",
"variant": "dashed" "variant": "default"
}, },
{ {
"id": "management-people", "id": "management-people",
"from": "management", "from": "management",
"to": "people", "to": "people",
"label": "A: placement", "label": "Coordinates",
"variant": "dashed" "variant": "default"
} }
], ],
"cards": [ "cards": [
{
"dot": "amber",
"title": "Not a verified employee roster — 2026-10-02",
"items": [
"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", "dot": "cyan",
"title": "Product", "title": "Product",
"items": [ "items": [
"E: Order/Orders; Categories design [13,14]", "Orders; Categories",
"E: Data Team / J: ranking role [9]", "Sellers & Operations",
"J: seller-platform domain [15]", "Data & Intelligence; Product Design"
"A: Sellers & Operations squad"
] ]
}, },
{ {
"dot": "amber", "dot": "amber",
"title": "Technology", "title": "Technology",
"items": [ "items": [
"J: engineering management chain [6,7]", "Product Engineering; Quality Engineering",
"J: AI Architect — solo start [8]", "Platform & Reliability; Architecture & Security",
"J: IT Engineer; Technical Architect [8,10]", "AI Enablement; Internal IT"
"A: platform/reliability capability group"
] ]
}, },
{ {
"dot": "cyan", "dot": "cyan",
"title": "Operations", "title": "Operations",
"items": [ "items": [
"E: Customer Support [11]", "Customer Support; Trust & Resolution",
"E: Trust & Resolution; Risk & Fraud [11]", "Risk & Fraud",
"J: operational QA directly to COO [11]", "Operational Quality"
"A: wider COO ownership/lead escalation"
] ]
}, },
{ {
"dot": "amber", "dot": "amber",
"title": "Marketing", "title": "Marketing",
"items": [ "items": [
"J: Brand Lead directly to CMO [12]", "Brand & Community; Creative; SEO",
"E: Creative; SEO; PPC & Affiliate [12]", "PPC & Affiliate; Influencer",
"E: Influencer; CRM; community [12]", "CRM"
"A: separate workstream boundaries"
] ]
}, },
{ {
"dot": "cyan", "dot": "cyan",
"title": "Finance & Accounting", "title": "Finance & Accounting",
"items": [ "items": [
"E: Finance team [5]", "Financial Planning & Analysis",
"J: CFO hiring mandate [5]", "Accounting, Tax & Controls",
"A: FP&A; Accounting/Tax/Controls", "Treasury & Payment Operations"
"A: Treasury / Payment Operations"
] ]
}, },
{ {
"dot": "amber", "dot": "amber",
"title": "HR & Administration", "title": "HR & Administration",
"items": [ "items": [
"E: Talent Acquisition [16]", "Talent Acquisition",
"A: People Operations", "People Operations",
"A: Office / Administration", "Office & Administration"
"A: HR leadership reporting line"
] ]
} }
] ]
+2 -2
View File
@@ -9,7 +9,7 @@ description: Author typed JSON diagrams and embed their local interactive viewer
| Diagram type | Intended use | | Diagram type | Intended use |
| --- | --- | | --- | --- |
| Architecture | Components, boundaries and relationships; also used for the evidence-labeled organization views | | Architecture | Components, boundaries and relationships; also used for the organization structure views |
| Workflow | Processes, branches and approval gates | | Workflow | Processes, branches and approval gates |
| Sequence | Participants and ordered messages | | Sequence | Participants and ordered messages |
| Dataflow | Sources, processing and destinations | | Dataflow | Sources, processing and destinations |
@@ -34,7 +34,7 @@ pnpm build
```mdx ```mdx
import ArchifyDiagram from '@site/src/components/ArchifyDiagram'; import ArchifyDiagram from '@site/src/components/ArchifyDiagram';
<ArchifyDiagram name="organization-structure" title="Eldorado organization — evidence and assumptions" /> <ArchifyDiagram name="organization-structure" title="Eldorado organization structure" />
``` ```
Supply a text alternative below each diagram. The wrapper uses a local, base-path-aware iframe with a descriptive title, scripts and downloads enabled, and no same-origin or parent-navigation permissions. The Open full viewer button expands the diagram in a full-screen modal on the current page, with the same iframe sandbox. Close it with the Close button or Escape; focus returns to the opener. It does not open a new tab. The separate standalone HTML asset remains directly addressable and is not itself iframe-sandboxed, so publish only reviewed, trusted diagrams. Generated output is ignored by Git and rebuilt in CI. Supply a text alternative below each diagram. The wrapper uses a local, base-path-aware iframe with a descriptive title, scripts and downloads enabled, and no same-origin or parent-navigation permissions. The Open full viewer button expands the diagram in a full-screen modal on the current page, with the same iframe sandbox. Close it with the Close button or Escape; focus returns to the opener. It does not open a new tab. The separate standalone HTML asset remains directly addressable and is not itself iframe-sandboxed, so publish only reviewed, trusted diagrams. Generated output is ignored by Git and rebuilt in CI.
+101 -71
View File
@@ -1,101 +1,131 @@
--- ---
title: Structure title: Structure
description: Distinguish Eldorado’s publicly evidenced organization from advertised roles and planning assumptions. description: Eldorado’s organizational operating model, departments, teams and responsibilities.
--- ---
import ArchifyDiagram from '@site/src/components/ArchifyDiagram'; import ArchifyDiagram from '@site/src/components/ArchifyDiagram';
**Research snapshot: 2026-10-02.** This is a public-evidence reconstruction for AI strategy planning, **not a verified employee roster** or an internally approved organization chart. This operating model organizes Eldorado around six departments: **Product, Technology, Operations, Marketing, Finance & Accounting, and HR & Administration**. Leadership aligns their priorities around marketplace growth, customer trust and efficient delivery.
## What is known ## Leadership
Eldorado names **Vladas Jurkevičius — co-founder and CEO** and **Lukas Deksnys — co-founder and COO** on its official About page.[1] | Role | Leadership | Responsibility |
| --- | --- | --- |
| Chief Executive Officer | Vladas Jurkevičius | Company direction, business performance, strategic priorities and executive alignment. |
| Chief Operating Officer | Lukas Deksnys | Marketplace operations, customer service, resolution quality and operational performance. |
Its official careers site uses seven hiring categories: **Management, Product, Technology, Operations, Marketing, Finance & Accounting, and HR & Administration**. Those labels are directly evidenced; treating them as six peer departments beneath Management is a planning arrangement, not a published reporting hierarchy.[4] Functional leaders translate company priorities into departmental plans. Team leads own execution, people development and service quality within their teams.
### Evidence legend ## Organization overview
- **E — Publicly evidenced:** a named leader, team, function or careers category explicitly appears in an official source. This does not establish every reporting relationship. <ArchifyDiagram name="organization-structure" title="Eldorado organization structure" />
- **J — Job-advertised:** a vacancy describes a role, mandate or reporting line. The position may be unfilled or newly created.
- **A — Assumed:** a proposed grouping or missing team boundary used for planning, not a claim about Eldorado’s current structure. Dashed connectors identify assumed placements.
## Department overview **Management coordinates the six departments.** Each department has a clear business responsibility and a set of teams that deliver it.
<ArchifyDiagram name="organization-structure" title="Eldorado organization — evidence and assumptions" />
**Text alternative:** Management is shown above Product, Technology, Operations, Marketing, Finance & Accounting, and HR & Administration. All six placements beneath Management are assumed. The department names come from the careers taxonomy; the notes in the viewer identify evidenced teams and proposed subdivisions. This view does not assign every function directly to the CEO or COO.
## Departments and teams ## Departments and teams
The following separates **named teams** from **roles, capabilities and domains**. A function mentioned in a vacancy is not automatically a separately staffed team. ### Product
| Department / function | Publicly evidenced teams, roles or domains | Assumed completion for planning | **Purpose:** improve the buyer and seller experience and turn marketplace opportunities into valuable product capabilities.
| --- | --- | --- |
| **Management** | **E:** CEO Vladas Jurkevičius and COO Lukas Deksnys. **J:** CTO and CMO are referenced as reporting managers.[1][8][12] CFO is advertised.[5] No incumbent names are inferred for those three roles. | **A:** a leadership coordination layer across the six functions. Exact executive reporting lines, Board membership and decision rights remain unverified. |
| **Product** | **E:** Order/Orders team; Categories design team, with Boosting & Currency scope; Data Team appears in the ranking Data Scientist vacancy metadata. Data classification and product design evidence.[9][13][14] **J:** Sellers and Operations product-owner domain, including Seller Portal, integrations, onboarding, balances/withdrawals, invoicing and support tooling.[15] | **A:** treat Sellers & Operations as a cross-functional product squad for planning, not a proven standalone team. Do not duplicate Data as a separate peer department. |
| **Technology** | **J:** Head of Engineering → Group Engineering Managers → Engineering Managers → engineers. AI Architect reports to CTO and starts solo. Technical Architect is named as an infrastructure/security partner; IT Engineer is advertised for identity, device management and internal SaaS.[6][8][10] | **A:** CTO → Head of Engineering. Proposed shared platform/reliability and security capability groups, with staffing and reporting unverified. Do not turn AI Architect into an established AI department. |
| **Operations** | **E:** Customer Support, Trust & Resolution, Risk & Fraud. **J:** QA Specialist (Operations) reports directly to COO; separate support/resolution Team Lead mandates cover specialist teams.[11][17][18] | **A:** COO ownership of the wider Operations function and its team-lead escalation chain. Only the QA Specialist’s direct COO line is explicit in the reviewed sources. |
| **Marketing** | **J:** Brand Team Lead reports to CMO. **E:** the wider Marketing team names Creative, SEO, PPC & Affiliate, Influencer, and CRM; brand scope includes organic social, community and brand partnerships.[12] | **A:** model these named disciplines as planning workstreams under Marketing. Separate team managers, headcounts and each discipline’s direct CMO line are not established. |
| **Finance & Accounting** | **E:** Finance team / hiring category. **J:** CFO remit includes planning, reporting, cash/capital, tax, compliance, financial risk and payments; it describes partnership with CEO and Board, not an explicit reporting line.[5] | **A:** FP&A; Accounting/Tax/Controls; Treasury/Payment Operations as three capability groups. These are inferred subdivisions, not proven staffed teams. Financial risk is not the same thing as the Operations Risk & Fraud team. |
| **HR & Administration** | **E:** Talent Acquisition team / role category. **J:** full-cycle IT and non-IT recruitment, partnering with hiring managers.[16] | **A:** People Operations and Office/Administration alongside Talent Acquisition. Separate teams and the HR leader’s reporting line remain unverified. |
The Sellers and Operations posting establishes a **product domain**, not a named Sellers department. Its mandate crosses seller-facing features, operational tooling and marketplace infrastructure.[15] | Team | Responsibilities |
| --- | --- |
| Orders | Purchase and post-purchase journeys, order status, delivery experience, dispute flows, feedback and loyalty. |
| Categories | Category experiences, including Boosting and Currency, discovery, conversion and category-specific user journeys. |
| Sellers & Operations | Seller Portal, seller integrations, onboarding and verification, balances and withdrawals, invoicing and operational tooling. |
| Data & Intelligence | Product analytics, experimentation, offer ranking, recommendations and decision support. |
| Product Design | User research, interaction design, design consistency and accessible buyer and seller experiences across product teams. |
## Reporting lines supported by vacancies Product Owners, Designers and Tech Leads work together on each product area. Product owns priorities and outcomes; Technology owns engineering execution and technical quality.
<ArchifyDiagram name="organization-reporting" title="Eldorado reporting lines — advertised and assumed" /> ### Technology
**Read arrows as manager → role/team.** Solid **J** connectors are explicitly described in vacancies. The dashed **A** link between CTO and Head of Engineering is the only inferred link in this diagram. Separate rows are not connected because their upward reporting lines were not established. **Purpose:** build and operate a secure, reliable marketplace and improve the effectiveness of engineering.
| Manager / leader | Role or team below it | Status and scope | | Team / function | Responsibilities |
| --- | --- | --- | | --- | --- |
| Head of Engineering | Group Engineering Manager | **J:** explicitly reports directly to Head of Engineering; the vacancy describes managing 4–5 Engineering Managers.[6] | | Product Engineering | Develop and maintain marketplace capabilities in cross-functional product teams. |
| Group Engineering Manager | Engineering Manager | **J:** explicitly named manager in the Engineering Manager vacancy.[7] | | Platform & Reliability | Shared platform services, delivery infrastructure, observability, availability and performance. |
| Engineering Manager | Software engineers | **J:** leads a team of around five engineers. This is the advertised span, not a count of all current engineering teams.[7] | | Architecture & Security | Technical standards, system design, infrastructure security and secure engineering practices. |
| CTO | AI Architect | **J:** explicitly direct; a new individual-contributor role, starting solo with a possible future team.[8] | | Quality Engineering | Test strategy, automation, release quality and defect prevention. |
| COO | QA Specialist (Operations) | **J:** explicitly direct; independent quality work across Customer Support, Trust & Resolution, and Risk & Fraud.[11] | | AI Enablement | AI-assisted engineering workflows, developer tools, adoption, standards and safe use of AI. |
| CMO | Brand Team Lead | **J:** explicitly direct; brand, organic social, community and brand partnerships remit.[12] | | Internal IT | Identity and access, employee devices, internal systems, software administration and joiner–mover–leaver processes. |
| Customer Support / Trust & Resolution Team Leads | Their specialists | **J:** support/resolution leadership advert describes teams of 5–10 specialists; the resolution-specific advert also states 5–10. Their own upward manager is not stated.[17][18] |
| CTO | Head of Engineering | **A:** plausible technology reporting arrangement, retained only as a planning assumption. |
Product Owner, Tech Lead and Product Designer are described as collaborating on product direction. That is evidence of cross-functional work, **not** evidence that one line-manages the others.[13][14] The CTO owns technology direction. The Head of Engineering leads engineering delivery through Group Engineering Managers and Engineering Managers. The AI Architect coordinates AI enablement across engineering, working with Architecture & Security and team leaders.
## What this means for AI strategy ### Operations
**Research interpretation, not an approved roadmap:** use the evidenced organizational owners rather than inventing one central AI department. **Purpose:** keep marketplace trading dependable and resolve customer issues fairly and efficiently.
- **Engineering enablement:** the AI Architect vacancy focuses on engineering output, adoption, standards and security under the CTO—not ownership of every business AI initiative.[8] | Team | Responsibilities |
- **Marketplace intelligence:** Product/Data has an advertised ranking and recommendations remit, including experimentation and learning-to-rank.[9] | --- | --- |
- **Operations quality:** operational QA explicitly includes auditing AI-handled support and LLM-assisted scoring; customer support leadership includes AI-assisted support and automation.[11][17] | Customer Support | Buyer and seller assistance, knowledge management, self-service and support workflow automation. |
- **Planning assumption:** coordinate these three areas with Product, Operations, Technology and Finance owners. Whether to create a cross-company AI steering group is a future decision, not a finding about current organization. | Trust & Resolution | Disputes, appeals, refunds, warranties, chargebacks and complex customer cases. |
| Risk & Fraud | Transaction and account risk, fraud prevention, investigations and operational controls. |
| Operational Quality | Independent case reviews, quality standards, calibration, service accuracy and improvement tracking across operational teams. |
## Limits and validation questions The COO coordinates Operations. Team leads manage specialists and daily service delivery. Operational Quality reports directly to the COO and reviews quality across teams.
- **No complete internal chart was found in the reviewed public sources.** This is not a claim that none exists. Research prioritized official About, careers, vacancy and legal pages; it is not an exhaustive employee or vacancy census. ### Marketing
- **Job postings are time-bound recruitment evidence.** A vacancy can describe a future role or team. Names, staffing, budgets and every executive reporting line still need company confirmation.
- **No reliable total headcount is asserted.** The careers homepage itself contains both “150+” and “200+” descriptions; do not use either to derive department sizes.[2]
- **Legal entities are not departments.** The Terms of Service names GWD Processing FZCO, Eldorado Sales LLC and Halfway House OÜ collectively as Eldorado. This establishes contracting language, not a parent/subsidiary hierarchy or the employing entity of each team.[3]
- **Keep scope distinctions:** marketplace Risk & Fraud, financial risk, AI security, and corporate compliance may collaborate but should not be collapsed into one assumed reporting chain.
Before using this as an operating model, confirm: **(1)** which advertised roles are filled, **(2)** executive and functional reporting lines, **(3)** product squad membership and engineering matrix, **(4)** ownership of Payments, Legal/Compliance and Data, and **(5)** the real team roster and capacity. Replace each **A** only when evidence is supplied. **Purpose:** attract and retain customers, build the Eldorado brand and grow marketplace demand.
## Sources | Team / workstream | Responsibilities |
| --- | --- |
| Brand & Community | Brand positioning, campaigns, organic social, community and brand partnerships. |
| Creative | Campaign concepts, visual assets and performance creative. |
| SEO | Organic discovery, search visibility and content performance. |
| PPC & Affiliate | Paid acquisition, affiliate channels and return on marketing investment. |
| Influencer | Creator relationships, influencer programs and campaign delivery. |
| CRM | Customer lifecycle communication, retention, reactivation and campaign personalization. |
[1] https://www.eldorado.gg/about-us — Eldorado About us The CMO coordinates Marketing. The Brand Team Lead owns Brand & Community, with shared support from Creative and the other marketing workstreams.
[2] https://careers.eldorado.gg — Eldorado Careers homepage
[3] https://www.eldorado.gg/terms-of-service — Eldorado Terms of Service ### Finance & Accounting
[4] https://careers.eldorado.gg/jobs — Eldorado Jobs — official hiring categories
[5] https://careers.eldorado.gg/jobs/8394692-chief-financial-officer — Chief Financial Officer **Purpose:** maintain financial control, support business decisions and keep marketplace money flows dependable.
[6] https://careers.eldorado.gg/jobs/8376024-group-engineering-manager — Group Engineering Manager
[7] https://careers.eldorado.gg/jobs/8290012-engineering-manager — Engineering Manager | Team / function | Responsibilities |
[8] https://careers.eldorado.gg/jobs/8175478-ai-architect — AI Architect | --- | --- |
[9] https://careers.eldorado.gg/jobs/8261309-data-scientist-offer-ranking-recommendations — Data Scientist (Offer Ranking & Recommendations) | Financial Planning & Analysis | Budgets, forecasts, profitability, management reporting and investment analysis. |
[10] https://careers.eldorado.gg/jobs/8363463-it-engineer — IT Engineer | Accounting, Tax & Controls | Accounting, financial reporting, tax, audit coordination and internal controls. |
[11] https://careers.eldorado.gg/jobs/8358613-qa-specialist-operations — QA Specialist (Operations) | Treasury & Payment Operations | Cash management, reconciliation, payout oversight, payment-provider coordination and financial risk. |
[12] https://careers.eldorado.gg/jobs/8450323-brand-team-lead — Brand Team Lead
[13] https://careers.eldorado.gg/jobs/8404928-product-designer-orders-team — Product Designer (Orders team) The CFO coordinates Finance & Accounting and works with executive leadership on business performance. Finance, Operations and Product share responsibility for effective payment and withdrawal processes, each within its own area of expertise.
[14] https://careers.eldorado.gg/jobs/8253165-product-designer — Product Designer
[15] https://careers.eldorado.gg/jobs/8389376-product-owner-sellers-and-operations — Product Owner (Sellers and Operations) ### HR & Administration
[16] https://careers.eldorado.gg/jobs/8487069-talent-acquisition-partner-junior-mid — Talent Acquisition Partner (Junior - Mid)
[17] https://careers.eldorado.gg/jobs/8381712-customer-support-team-lead — Customer Support Team Lead **Purpose:** help teams attract, develop and retain people and provide an effective working environment.
[18] https://careers.eldorado.gg/jobs/8483510-trust-resolution-team-lead — Trust & Resolution Team Lead
| Team | Responsibilities |
| --- | --- |
| Talent Acquisition | Recruitment, candidate experience, hiring coordination and workforce demand support. |
| People Operations | Employee onboarding, development, performance processes, policies and employee experience. |
| Office & Administration | Workplace services, office operations and administrative coordination. |
HR partners with department leaders on team capacity and development. People Operations works with Internal IT on employee onboarding, role changes and offboarding.
## Leadership and delivery structure
<ArchifyDiagram name="organization-reporting" title="Eldorado leadership and delivery structure" />
The diagram shows management responsibility from leader to role or team:
- **CTO → Head of Engineering → Group Engineering Managers → Engineering Managers → Product Engineering teams.**
- **CTO → AI Architect**, coordinating engineering AI enablement.
- **COO → Operational Quality**, providing independent quality oversight.
- **CMO → Brand Team Lead**, leading Brand & Community.
Product teams combine product ownership, design, engineering, quality and data expertise. Functional management develops people and professional standards; cross-functional teams deliver business outcomes.
## How the departments work together
| Business outcome | Collaboration |
| --- | --- |
| Better buyer experience | Product defines improvements; Technology delivers them; Operations brings customer feedback; Data measures the result. |
| Stronger seller experience | Product and Technology develop seller tools; Operations supports sellers; Finance manages financial processes. |
| Safe and trustworthy trading | Risk & Fraud, Trust & Resolution, Architecture & Security, and Finance coordinate controls and incident responses. |
| Sustainable growth | Marketing develops demand; Product improves conversion and retention; Finance measures profitability. |
| AI-powered execution | AI Enablement supports engineering; Data & Intelligence develops marketplace intelligence; Operations improves service and quality workflows. |
Department leaders remain accountable for outcomes, controls and service quality as AI becomes part of everyday work.
+4 -6
View File
@@ -1,9 +1,7 @@
# Organization research — 2026-10-02 # Organization background research
Public-evidence reconstruction, not an approved internal org chart. The canonical reader-facing report is `docs/organization/structure.mdx`. `sources.json` preserves retrieved URLs, access dates and verbatim excerpts checked against fetched page text with the grounded-citations evidence matcher. No private employee data or application forms were accessed. The source/excerpt ledger and `reconstruction-snapshot.mdx` preserve the original public-evidence investigation. They are background working material, outside the published docs and static assets.
E = publicly evidenced names/categories/functions; J = job-advertised roles and reporting lines, not proof of occupancy; A = planning assumptions. The diagrams carry the same distinction. Department placement beneath Management is a model, not a proven reporting chain. Legal entities and hiring categories must not be conflated with departments. The reader-facing `docs/organization/structure.mdx` is an organizational operating model, not a research report or an employee roster. Per the user's presentation direction, it describes leadership, departments, teams and responsibilities directly without evidence markers, vacancies or citations. Internet research informs the model; this editorial change does not independently verify staffing, incumbent names or every reporting relationship.
Coverage: official About, careers index and selected job detail pages plus legal Terms. The jobs index was not treated as an exhaustive personnel roster. Search-engine discovery was unhelpful (Google traffic challenge; Bing irrelevant results); all factual findings rely on directly fetched official sources. Exact headcount and unnamed incumbents are deliberately omitted. Current-role dates are access dates, not proof of appointment dates. The original snapshot records which categories and relationships were evidenced, job-advertised or inferred. Retain that provenance for future maintenance, without importing it into the published page, diagram metadata or search index.
Update source excerpts and access dates, revise the report and both diagrams together, then run `pnpm verify`, `pnpm typecheck`, `pnpm build`, `pnpm verify:build` and browser checks before publication. Revalidate recruitment evidence rather than treating an old vacancy as a permanent org fact.
@@ -0,0 +1,102 @@
---
title: Structure
description: Distinguish Eldorado’s publicly evidenced organization from advertised roles and planning assumptions.
---
import ArchifyDiagram from '@site/src/components/ArchifyDiagram';
**Research snapshot: 2026-10-02.** This is a public-evidence reconstruction for AI strategy planning, **not a verified employee roster** or an internally approved organization chart.
## What is known
Eldorado names **Vladas Jurkevičius — co-founder and CEO** and **Lukas Deksnys — co-founder and COO** on its official About page.[1]
Its official careers site uses seven hiring categories: **Management, Product, Technology, Operations, Marketing, Finance & Accounting, and HR & Administration**. Those labels are directly evidenced; treating them as six peer departments beneath Management is a planning arrangement, not a published reporting hierarchy.[4]
### Evidence legend
- **E — Publicly evidenced:** a named leader, team, function or careers category explicitly appears in an official source. This does not establish every reporting relationship.
- **J — Job-advertised:** a vacancy describes a role, mandate or reporting line. The position may be unfilled or newly created.
- **A — Assumed:** a proposed grouping or missing team boundary used for planning, not a claim about Eldorado’s current structure. Dashed connectors identify assumed placements.
## Department overview
<ArchifyDiagram name="organization-structure" title="Eldorado organization — evidence and assumptions" />
**Text alternative:** Management is shown above Product, Technology, Operations, Marketing, Finance & Accounting, and HR & Administration. All six placements beneath Management are assumed. The department names come from the careers taxonomy; the notes in the viewer identify evidenced teams and proposed subdivisions. This view does not assign every function directly to the CEO or COO.
## Departments and teams
The following separates **named teams** from **roles, capabilities and domains**. A function mentioned in a vacancy is not automatically a separately staffed team.
| Department / function | Publicly evidenced teams, roles or domains | Assumed completion for planning |
| --- | --- | --- |
| **Management** | **E:** CEO Vladas Jurkevičius and COO Lukas Deksnys. **J:** CTO and CMO are referenced as reporting managers.[1][8][12] CFO is advertised.[5] No incumbent names are inferred for those three roles. | **A:** a leadership coordination layer across the six functions. Exact executive reporting lines, Board membership and decision rights remain unverified. |
| **Product** | **E:** Order/Orders team; Categories design team, with Boosting & Currency scope; Data Team appears in the ranking Data Scientist vacancy metadata. Data classification and product design evidence.[9][13][14] **J:** Sellers and Operations product-owner domain, including Seller Portal, integrations, onboarding, balances/withdrawals, invoicing and support tooling.[15] | **A:** treat Sellers & Operations as a cross-functional product squad for planning, not a proven standalone team. Do not duplicate Data as a separate peer department. |
| **Technology** | **J:** Head of Engineering → Group Engineering Managers → Engineering Managers → engineers. AI Architect reports to CTO and starts solo. Technical Architect is named as an infrastructure/security partner; IT Engineer is advertised for identity, device management and internal SaaS.[6][8][10] | **A:** CTO → Head of Engineering. Proposed shared platform/reliability and security capability groups, with staffing and reporting unverified. Do not turn AI Architect into an established AI department. |
| **Operations** | **E:** Customer Support, Trust & Resolution, Risk & Fraud. **J:** QA Specialist (Operations) reports directly to COO; separate support/resolution Team Lead mandates cover specialist teams.[11][17][18] | **A:** COO ownership of the wider Operations function and its team-lead escalation chain. Only the QA Specialist’s direct COO line is explicit in the reviewed sources. |
| **Marketing** | **J:** Brand Team Lead reports to CMO. **E:** the wider Marketing team names Creative, SEO, PPC & Affiliate, Influencer, and CRM; brand scope includes organic social, community and brand partnerships.[12] | **A:** model these named disciplines as planning workstreams under Marketing. Separate team managers, headcounts and each discipline’s direct CMO line are not established. |
| **Finance & Accounting** | **E:** Finance team / hiring category. **J:** CFO remit includes planning, reporting, cash/capital, tax, compliance, financial risk and payments; it describes partnership with CEO and Board, not an explicit reporting line.[5] | **A:** FP&A; Accounting/Tax/Controls; Treasury/Payment Operations as three capability groups. These are inferred subdivisions, not proven staffed teams. Financial risk is not the same thing as the Operations Risk & Fraud team. |
| **HR & Administration** | **E:** Talent Acquisition team / role category. **J:** full-cycle IT and non-IT recruitment, partnering with hiring managers.[16] | **A:** People Operations and Office/Administration alongside Talent Acquisition. Separate teams and the HR leader’s reporting line remain unverified. |
The Sellers and Operations posting establishes a **product domain**, not a named Sellers department. Its mandate crosses seller-facing features, operational tooling and marketplace infrastructure.[15]
## Reporting lines supported by vacancies
<ArchifyDiagram name="organization-reporting" title="Eldorado reporting lines — advertised and assumed" />
**Read arrows as manager → role/team.** Solid **J** connectors are explicitly described in vacancies. The dashed **A** link between CTO and Head of Engineering is the only inferred link in this diagram. Separate rows are not connected because their upward reporting lines were not established.
| Manager / leader | Role or team below it | Status and scope |
| --- | --- | --- |
| Head of Engineering | Group Engineering Manager | **J:** explicitly reports directly to Head of Engineering; the vacancy describes managing 4–5 Engineering Managers.[6] |
| Group Engineering Manager | Engineering Manager | **J:** explicitly named manager in the Engineering Manager vacancy.[7] |
| Engineering Manager | Software engineers | **J:** leads a team of around five engineers. This is the advertised span, not a count of all current engineering teams.[7] |
| CTO | AI Architect | **J:** explicitly direct; a new individual-contributor role, starting solo with a possible future team.[8] |
| COO | QA Specialist (Operations) | **J:** explicitly direct; independent quality work across Customer Support, Trust & Resolution, and Risk & Fraud.[11] |
| CMO | Brand Team Lead | **J:** explicitly direct; brand, organic social, community and brand partnerships remit.[12] |
| Customer Support / Trust & Resolution Team Leads | Their specialists | **J:** support/resolution leadership advert describes teams of 5–10 specialists; the resolution-specific advert also states 5–10. Their own upward manager is not stated.[17][18] |
| CTO | Head of Engineering | **A:** plausible technology reporting arrangement, retained only as a planning assumption. |
Product Owner, Tech Lead and Product Designer are described as collaborating on product direction. That is evidence of cross-functional work, **not** evidence that one line-manages the others.[13][14]
## What this means for AI strategy
**Research interpretation, not an approved roadmap:** use the evidenced organizational owners rather than inventing one central AI department.
- **Engineering enablement:** the AI Architect vacancy focuses on engineering output, adoption, standards and security under the CTO—not ownership of every business AI initiative.[8]
- **Marketplace intelligence:** Product/Data has an advertised ranking and recommendations remit, including experimentation and learning-to-rank.[9]
- **Operations quality:** operational QA explicitly includes auditing AI-handled support and LLM-assisted scoring; customer support leadership includes AI-assisted support and automation.[11][17]
- **Planning assumption:** coordinate these three areas with Product, Operations, Technology and Finance owners. Whether to create a cross-company AI steering group is a future decision, not a finding about current organization.
## Limits and validation questions
- **No complete internal chart was found in the reviewed public sources.** This is not a claim that none exists. Research prioritized official About, careers, vacancy and legal pages; it is not an exhaustive employee or vacancy census.
- **Job postings are time-bound recruitment evidence.** A vacancy can describe a future role or team. Names, staffing, budgets and every executive reporting line still need company confirmation.
- **No reliable total headcount is asserted.** The careers homepage itself contains both “150+” and “200+” descriptions; do not use either to derive department sizes.[2]
- **Legal entities are not departments.** The Terms of Service names GWD Processing FZCO, Eldorado Sales LLC and Halfway House OÜ collectively as Eldorado. This establishes contracting language, not a parent/subsidiary hierarchy or the employing entity of each team.[3]
- **Keep scope distinctions:** marketplace Risk & Fraud, financial risk, AI security, and corporate compliance may collaborate but should not be collapsed into one assumed reporting chain.
Before using this as an operating model, confirm: **(1)** which advertised roles are filled, **(2)** executive and functional reporting lines, **(3)** product squad membership and engineering matrix, **(4)** ownership of Payments, Legal/Compliance and Data, and **(5)** the real team roster and capacity. Replace each **A** only when evidence is supplied.
## Sources
[1] https://www.eldorado.gg/about-us — Eldorado About us
[2] https://careers.eldorado.gg — Eldorado Careers homepage
[3] https://www.eldorado.gg/terms-of-service — Eldorado Terms of Service
[4] https://careers.eldorado.gg/jobs — Eldorado Jobs — official hiring categories
[5] https://careers.eldorado.gg/jobs/8394692-chief-financial-officer — Chief Financial Officer
[6] https://careers.eldorado.gg/jobs/8376024-group-engineering-manager — Group Engineering Manager
[7] https://careers.eldorado.gg/jobs/8290012-engineering-manager — Engineering Manager
[8] https://careers.eldorado.gg/jobs/8175478-ai-architect — AI Architect
[9] https://careers.eldorado.gg/jobs/8261309-data-scientist-offer-ranking-recommendations — Data Scientist (Offer Ranking & Recommendations)
[10] https://careers.eldorado.gg/jobs/8363463-it-engineer — IT Engineer
[11] https://careers.eldorado.gg/jobs/8358613-qa-specialist-operations — QA Specialist (Operations)
[12] https://careers.eldorado.gg/jobs/8450323-brand-team-lead — Brand Team Lead
[13] https://careers.eldorado.gg/jobs/8404928-product-designer-orders-team — Product Designer (Orders team)
[14] https://careers.eldorado.gg/jobs/8253165-product-designer — Product Designer
[15] https://careers.eldorado.gg/jobs/8389376-product-owner-sellers-and-operations — Product Owner (Sellers and Operations)
[16] https://careers.eldorado.gg/jobs/8487069-talent-acquisition-partner-junior-mid — Talent Acquisition Partner (Junior - Mid)
[17] https://careers.eldorado.gg/jobs/8381712-customer-support-team-lead — Customer Support Team Lead
[18] https://careers.eldorado.gg/jobs/8483510-trust-resolution-team-lead — Trust & Resolution Team Lead
+8 -13
View File
@@ -59,24 +59,19 @@ test('Archify is pinned, licensed and rebuilt, not a remote embed', () => {
assert(!wrapper.includes('target="_blank"')); assert(!wrapper.includes('target="_blank"'));
assert(wrapper.includes('Close full-screen diagram')); assert(wrapper.includes('Close full-screen diagram'));
}); });
test('organization research distinguishes evidence, advertised roles and assumptions', () => { test('organization page presents an operating model, not research notes', () => {
const page = read('docs/organization/structure.mdx'); const page = read('docs/organization/structure.mdx');
assert(page.includes('2026-10-02') && page.includes('not a verified employee roster')); assert(page.includes('operating model') && page.includes('## Departments and teams'));
const prohibited = /assum|job.advert|vacanc|publicly evidenced|research snapshot|## Sources|\[\d+\]|\b[EJA]:\s/i;
assert(!prohibited.test(page));
assert(page.includes('Vladas Jurkevičius') && page.includes('Lukas Deksnys')); assert(page.includes('Vladas Jurkevičius') && page.includes('Lukas Deksnys'));
assert(page.includes('Assumed') && page.includes('Publicly evidenced')); assert(existsSync('research/organization/reconstruction-snapshot.mdx'));
assert(!page.includes('Illustrative integration example')); assert(JSON.parse(read('research/organization/sources.json')).sources.every(s => s.quotes?.length));
const ledger = JSON.parse(read('research/organization/sources.json'));
const citations = [...page.split('## Sources')[0].matchAll(/\[(\d+)\]/g)].map(m => Number(m[1]));
assert(citations.length > 10);
for (const id of citations) assert(ledger.sources.some(s => s.id === id && s.quotes?.length), `Missing evidence ${id}`);
for (const name of ['organization-structure', 'organization-reporting']) { for (const name of ['organization-structure', 'organization-reporting']) {
const spec = JSON.parse(read(`diagrams/${name}.architecture.json`)); const spec = JSON.parse(read(`diagrams/${name}.architecture.json`));
assert(!prohibited.test(JSON.stringify(spec)));
const ids = new Set(spec.components.map(n => n.id)); const ids = new Set(spec.components.map(n => n.id));
assert.equal(ids.size, spec.components.length); assert.equal(ids.size, spec.components.length);
for (const edge of spec.connections) { for (const edge of spec.connections) assert(ids.has(edge.from) && ids.has(edge.to));
assert(ids.has(edge.from) && ids.has(edge.to));
assert(edge.label.startsWith('J:') || edge.label.startsWith('A:'));
if (edge.label.startsWith('A:')) assert.equal(edge.variant, 'dashed');
}
} }
}); });
+6 -3
View File
@@ -21,12 +21,15 @@ if (process.argv.includes('--build')) {
} }
assert(!readdirSync('build/diagrams', {recursive: true}).some(f => f.endsWith('.delivery.json')), 'Private build receipts must not be published'); assert(!readdirSync('build/diagrams', {recursive: true}).some(f => f.endsWith('.delivery.json')), 'Private build receipts must not be published');
const diagram = read('build/diagrams/organization-structure/index.html'); const diagram = read('build/diagrams/organization-structure/index.html');
assert(diagram.includes('A: placement') && diagram.includes('node-technology')); assert(diagram.includes('Coordinates') && diagram.includes('node-technology'));
assert(!/A: placement|E: careers|J: advertised/.test(diagram));
assert(!diagram.includes('Example leadership')); assert(!diagram.includes('Example leadership'));
const reporting = read('build/diagrams/organization-reporting/index.html'); const reporting = read('build/diagrams/organization-reporting/index.html');
assert(reporting.includes('AI Architect') && reporting.includes('A: assumed')); assert(reporting.includes('AI Architect') && reporting.includes('Leads'));
assert(!/A: assumed|J: direct/.test(reporting));
const structure = read('build/organization/structure/index.html'); const structure = read('build/organization/structure/index.html');
assert(structure.includes('Vladas Jurkevičius') && structure.includes('not a verified employee roster')); assert(structure.includes('Vladas Jurkevičius') && structure.includes('operating model'));
assert(!/Research snapshot|Job-advertised|careers\.eldorado\.gg|Assumed/.test(structure));
assert(!structure.includes('Illustrative integration example')); assert(!structure.includes('Illustrative integration example'));
assert(!diagram.includes('/opt/data/'), 'No build paths in published diagrams'); assert(!diagram.includes('/opt/data/'), 'No build paths in published diagrams');
const home = read('build/index.html'); const home = read('build/index.html');