S · Services

Agency/enterprise · local websites · support · on-prem setup · rapid prototyping This page lists everything the Leumas graph records about how it relates to the rest of the system.

What S · Services is

Agency/enterprise · local websites · support · on-prem setup · rapid prototyping It is recorded in the Leumas graph as a revenue in the architecture grain.

What S · Services relates to

The graph records 6 relationships for it, across 2 kinds. It contains S · Agency and enterprise, S · Local business websites and S · On-prem Studio setup, and 2 more.

What it depends on, and what depends on it

Nothing is recorded as a dependency of S · Services. Nothing is recorded as depending on it, which for a leaf is normal and for a shared unit is worth checking.

Why it is shaped this way

Admin-led services begin with a lead, contract, or customer brief. Studio performs much of the AI-assisted build and delivery, while Admin owns qualification, contracts, invoicing, acceptance exceptions, and support escalation.

How to read this

Every relationship here is one of nine shared kinds, mapped from the source graph rather than invented. A kind that a source uses and this model does not express is dropped and counted rather than turned into "related to", so what you see understates the source rather than embellishing it.

Questions

What does S · Services depend on?

This graph records no dependencies for S · Services.

What uses S · Services?

Nothing in this graph is recorded as depending on S · Services.