Members and Roles Directory

1) Why you need a directory

The catalog is a single source of truth about the subjects of the network: who is who, what role he plays, what rights and limits he has, what is the level of trust and the history of actions. It connects identity → a role → the rights → the relations → metrics → incentives and does an ecosystem operated, checked and scaled.

• Reduce connectivity between services (single role/entitlement model).
• Simplify onboarding/offboarding and compliance.
• Build reputation and collateral into access and limit decisions.
• Ensure audit,治理 and inter-chain portability of rights.

2) Role taxonomy (abstraction levels)

• User/Player/Customer (Consumer)
• Developer/Integrator (Builder)
• Resource Provider (Compute/Storage/DA/Liquidity)
• Content/Product Creator
• Node/Validator/Oracle
• Operator
• Affiliate/Partner/Aggregator
• Analyst/Researcher
• Curator/Moderator
• Regulatory Entity/Auditor

• Merchant-Operator: operator + billing + compliance.
• Creator-Affiliate: creator + partner funnel.
• Node-Provider: validator providing computing/network resources.
• Builder-Maintainer: developer, service owner and SLO.

• Service account, CI/CD robots, curation bots, anti-fraud agents.

3) Directory entry attributes (minimum profile)

Identity: DID, bindings to external identifiers, verification statuses (KYC/KYB).
Roles - list of active roles + action time windows.
Rights & Limits: access rights (ABAC/RBAC), quota limits (API, resources, financial limits).
Reputation (R): reputation points/badges (soulbound), decay functions.
Stakes (S): Pledges and insurance deposits, slashing conditions.
Relationships (RNFT): active contracts "subyekt↔subyekt/set" (parameters, KPI, date, exit price).
Compliance: geo-policies, age flags, sanction/regulatory statuses.
Observability: key quality metrics (SLA, uptime, moderation accuracy, returns/disputes).
Audit: log of changes in rights/roles, external checks, signatures.

4) Roles → rights → actions (access matrix)

Rights are expressed by ABAC policies (attributes of subject, resource, context) and are fixed in RNFT.

5) Member lifecycle

1. Onboarding DID registration → basic checks → initial roles/quotas.
2. Activation: issue of RNFT contracts (affiliate, resource provider, node), deposits S, starting R.
3. Operation: accumulation of R, revision of quotas/limits, auto-upgrade/auto-throttle according to KPI.
4. Incidents/disputes: arbitration, partial/full slash punishment, suspension of roles.
5. Offboarding: RNFT closure, S return (minus penalties), profile archiving, audit report.

6) RNFT templates (relationships and contracts)

Affiliate-RNFT: tracking parameters, payment models (CPA/CPL/RevShare/hybrid), cliff/vesting, anti-fraud rules.
Compute/Storage-RNFT: machine/GPU classes, quotas, price, SLO, penalties and compensations.
Validator-RNFT: size S, rules of participation and slashing, payment schedule, audit.
Creator-RNFT: rights/licenses, revs, moderation standards, deindexing by violations.
Data/API-RNFT: limits, privacy, licensing, retention/removal, ZK passes.

RNFT is a contract carrying rights, limits and KPIs; it is associated with roles and policy references.

7) Reputations (R) and liens (S)

R (soulbound): weighs access, priorities, prices, na治理 impact; has decay, amnesty, challenge.
S (stake): economic responsibility for quality/honesty; source of fines, user insurance.
Combination: for high-risk roles (validators, affiliates with volume), both R and S are required.

8) Inter-chain cataloging

Portability: rights/limits (RNFT) are transferred between domains; reputation R remains in the original trust domain (only provable aggregates/badges are divided).
Synchronization: Messaging Hub publishes profile/role "snapshots" with verifiable evidence.
Conflicts - when domain policies diverge - more stringent.

9) Observability and quality

• Creator: share of accepted publications, complaints/1000, returns.
• Node: uptime/latency, error rate, incidents/quarter.
• Provider: SLA breaks, queue lag, egress anomalies.
• Affiliate: hold, fraud rate, chargeback rate.
• Curator: accuracy/recall of signals, consistency with ground truth.
• Dashboards: role health, error budgets, deviation alerts.
• Audit: immutable journals, signatures, public post-mortems.

10) Compliance and privacy

DID + Verifiable Credentials: PD minimization, selective disclosures, age/region ZK proofs.
Retention policies: retention periods, right to remove/freeze.
Regional restrictions: automatic rules of access/limits on geo and product.
Reporting: export to registers, subject logs of risk decisions.

11) Catalog 治理

Procedures for changing roles/rights: proposals, quorums, veto mode for security.
R-modifier of votes: reputation limits the influence of "raw capital" on sensitive decisions.
Sunset clauses: Temporary powers for pilots/experiments.
Periodic review: quarterly audit of access matrices and RNFT templates.

12) Catalog data model (logical)

Subject ``

RoleBinding ``

Right/Limit ``

Reputation ``

Stake ``

RNFT ``

ComplianceFlag ``

AuditLog ``

13) Implementation playbook

1. Mapping of actors and value flows. Reconcile roles/boundaries.
2. Design of RNFT templates. For basic relationships (nodes, providers, affiliates, creators).
3. Access matrices (ABAC). Resource taxonomy, actions, limits/quotas.
4. R/S policies. Thresholds, decay, penalties, insurance funds.
5. Identity and compliance. DID/VC, ZK gaps, export reports.
6. Observability. Metrics by role, alerts, audit logs.
7. Pilot and game-days. Checking onboarding, slashing, disputes.
8. Scaling and interconnection. Status snapshots, rights synchronization, strict conflicts.

14) Catalog KPI

Completeness and relevance: proportion of subjects with valid DID/VC; overdue RNFTs <target%; average onboarding time.
Quality and safety: access incidents/quarter, frequency of slashing by role, share of challenged decisions.
Economics: R/S correlation with LTV/margin; share of revenue protected by pledges.
治理: speed of processing proposals, share of votes with an R-modifier, Gini index on rights.
Sustainability: MTTR by erroneous rights, share of autodegradations by error budgets.

15) Delivery checklist

• Roles, resource model, and ABAC matrices defined
• Implemented RNFT templates and S-pledge policies
• Included R-reputation with decay and amnesty/appeal procedures
• DID/VC and ZK gaps configured for sensitive attributes
• Quality dashboards, audit trails, export reporting available
• Onboarding/offboarding/incident scenarios worked out
• Vvedeny治理 procedures (proposals, veto, sunset)
• Cross-chain rights/limits synchronization is set up

16) Glossary

Registry: a register of subjects with roles, rights and provable history.
RNFT: non-interchangeable relationship/entitlement/limit contract and KPI.
R-token: non-transferable reputation for quality/trust.
S-token: pledge of economic responsibility.
ABAC/RBAC: authorization models by attributes/roles.
DID/VC: decentralized identity and verifiable credits.

Bottom line: The participant and role catalog is an ecosystem operating matrix linking identity, contracts, and entitlement to incentive economics and observability. By standardizing RNFT relationships, R/S policies, and ABAC matrices, the network gains controlled growth, provable security, and predictable evolution.