Roles

Different actors, different intentions, one auditable workflow.

A participant can follow one specific path or combine several permitted roles across the same accountable network.

Flexible participation

Roles describe actions, not fixed kinds of users.

A participant may focus on one role, hold several roles at the same time, or move across contexts as applicable capabilities, authorizations, and Contract scope allow. Future organizational participation requires separate governance and delegation architecture.

A user may express an intention to request, create, implement, validate, store, deliver, or participate in settlement. Intent guides the available path, but it does not grant authority by itself; each protected action requires the appropriate eligibility and authorization.

Every participant can make explicit commitments and is accountable for the work, technical artefacts, evidence, approvals, signatures, and delivery obligations they accept. Those commitments remain connected to the responsible actor and the auditable workflow.

Requesters

Publish a technical request

Define the technical objective, acceptance criteria, and delivery conditions.

Creators

Register an Artifact

Preserve a continuing technical or knowledge object and its exact historical states without treating origin as complete authorship or ownership.

Providers and implementers

Join implementation work

Execute delivery obligations, manufacturing paths, or technical implementation work.

Technical validators

Evaluate milestone evidence

Evaluate evidence against applicable scope and criteria without turning the evaluation into an absolute guarantee of truth.

Storage operators

Provide data availability receipts

Support evidence availability through accountable storage and replication guarantees.

Contract participants

Track delivery and settlement

Follow workflow state, evidence, disputes, delivery acceptance, and settlement readiness.

Next step

Review how trust and verification support accountable action.