Responsibility Matrix
A strong brand does not erase the supply chain behind a service. This page separates what JIM STEPHEN PINAS controls from what an external partner may provide.
Current website
| Layer | Current responsibility | Status |
|---|---|---|
| Brand, public claims, product architecture and governance | JIM STEPHEN PINAS | Active |
| Storefront and ecommerce infrastructure | Shopify platform; JIM STEPHEN PINAS controls content/configuration within available permissions | Active |
| Domain, DNS and business email infrastructure | TransIP services; JIM STEPHEN PINAS controls configuration and account decisions | Active |
| QUARK public constitutional content | JIM STEPHEN PINAS | Public |
| Production QUARK runtime/model/tool execution | Not yet production-live | Open |
Future regulated and partner-delivered services
| Service | Our intended role | External dependency |
|---|---|---|
| Mobile / eSIM | Brand, customer proposition, product/control layer and customer responsibility as contractually defined | Wholesale/MVNO network partner not yet contracted |
| Internet / Voice | Customer proposition, service layer, support and integration as contractually defined | Wholesale connectivity/voice partner not yet contracted |
| Streaming | Platform, customer experience and catalog governance | Content rights and delivery partners must be separately contracted |
Why this matters
Customers and investors should be able to distinguish brand responsibility, infrastructure ownership, operational responsibility and legal responsibility. These can overlap, but they are not automatically the same thing.
This matrix changes only when evidence and contracts change.