How ArQiver Organises Digital Work

Digital collaboration often goes wrong not because people have bad intentions, but because responsibilities are blurred. Who is allowed to decide? Who is accountable? When does something become “live”? And why does data suddenly start flowing before anyone has really agreed on what it means?

ArQiver is designed to prevent exactly that. It does so by combining clear roles, strict separation of responsibilities, and a step-by-step lifecycle that everyone must follow. This makes digital work safer, more transparent, and easier to trust—especially when many people and organisations are involved.

Why Separation of Roles Matters

In many systems, the same people can manage accounts, define data, approve products, and run operations. That might feel efficient, but it creates risk. Financial control, data governance, and daily execution are very different responsibilities—and they should not be mixed.

ArQiver separates these concerns from the start.

The Data Space Admin: Setting the Frame, Nothing More

The Data Space Admin exists for one purpose only: to set up the digital space itself.

This role creates the account, names the Enterprise Data Space, and takes care of payment. The Data Space Admin can invite and assign Data Space Owners—and that is where their role ends. They cannot create domains, invite members, design products, or touch data in any way.

This ensures that financial and legal control is clearly separated from data governance and daily work.

Who Shapes the Organisation?

Data Space Owners: Guardians of Structure

Data Space Owners shape the organisation’s digital structure. They create domains, invite members, and appoint Domain Owners. They also give the final “yes” when a product is ready to go live.

To keep responsibilities clear, a data space can have no more than two Data Space Owners. This prevents confusion about authority while still allowing shared responsibility.

Domain Owners: Meaning and Ownership

Domains are where meaning lives. A domain groups related products and defines the context in which data is used.

Domain Owners are responsible for this context. They invite members into their domain, assign Product Owners, and take part in approving products before they go live. They also help define what data looks like, how long it is kept, and how it is managed.

Each domain can have up to two Domain Owners and exactly one Product Manager.

Products and the People Behind Them

Product Managers and Product Owners

Every domain has one Product Manager who keeps an eye on consistency and coherence across all products in that domain. Product Owners, on the other hand, are responsible for individual products.

Both roles are required to approve a product before it becomes available. This ensures that no single person can push something live on their own.

Members: Contributing Without Risk

Members can contribute by defining data, metadata, retention rules, and record management. What they cannot do is approve products or create stream templates. This protects the system from accidental or premature activation while still allowing broad participation.

The Most Important Rule: Nothing Skips the Lifecycle

The ArQiver dashboard is organised around two clearly separated phases. These are not suggestions—they are the only allowed path forward.

Phase 1: Organise Your Enterprise & Create Data Streams

(Design comes before action)

In this phase, nothing “runs.” There is no data flowing, no operators working, no live products. Instead, the organisation defines what may exist.

• Data Cards define which kinds of data are expected.
• Metadata Cards explain what that data means.
• Retention Protocols define how long data must be kept.
• Records Management determines what actions are taken on data over time.
• Stream Templates bring all of this together into a governed design.

Before a stream template is approved, it must be reviewed by several roles, including privacy and archive specialists. This ensures that legal, ethical, and operational considerations are addressed upfront.

At this stage, nothing is visible to operators. Nothing executes. This is intentional.

Phase 2: Activate & Maintain Your Data Products

(From agreement to action)

Only what has been designed and approved in Phase 1 can move forward.

Approved stream templates become streams. Streams can then be activated and assigned to operators—but they are still not usable until they are added to a product.

A product only goes live after explicit consent from:

• the Product Owner,
• the Product Manager,
• the Domain Owner,
• and the Data Space Owner.

This is not a technical checkbox. It is a moment of shared responsibility.

The Moment Work Begins

When a product goes live, something important happens: operators are notified. The product appears in their domain-driven dashboard, signalling that design has ended and execution may begin.

This clear handover prevents confusion. People know when they are allowed to act—and why.

Why This Matters

This approach may seem strict, but it solves problems many organisations struggle with:

• Data flowing before meaning is agreed.
• Products going live without shared responsibility.
• Privacy and retention handled as afterthoughts.
• Operators unsure whether something is ready.

ArQiver replaces all of this with clarity.

One Simple Principle

ArQiver separates money from meaning, design from execution, and governance from operation—so digital work can move forward safely, transparently, and together.

That is not bureaucracy. It is how trust is built in complex digital environments.