Docs

Search and contents

Contribution, attribution and reputation

A contribution describes work that has happened, with its evidence; pay, credits, entitlements and any equity arrangement follow separate rules. Contributions are traceable, attribution is explainable and errors can be corrected.

In developmentNot availableVerified

Contribution, attribution and reputation diagram (A12) (open full-size figure)
MYRILUM architecture map v2.2 · A12 (public edition). Labels are in Chinese; every element is listed in English below. Select the diagram to open it at full size.

What this map shows

This is MYRILUM's target architecture. It does not mean everything on the map is live; whether a capability can be used today is stated in “Current availability”.

A contribution describes work that has happened and its evidence; pay, credits, entitlements and any equity arrangement belong to separate rules.

Contributions are traceable, attribution is explainable and errors can be corrected; recognizing value and settling money stay independent.

Contribution candidates come from real work

Work and delivery eventsTasks, roles, results, versions and acceptance references
Contribution claimWho did what and when, and which results it affected
Supporting evidenceWork orders, handoffs, artifacts and the counterparty's confirmation
Deduplication and relationship checksDuplicate claims, related parties, forgery and overlapping attribution

Confirming attribution and handling objections

Attribution methodRules, responsibilities and each party's role are stated in advance
Review by an authorized partyRecords acceptance, conditional acceptance or rejection, with reasons
Objections and appealsConflicts stay open for handling; a model never makes the final ruling
Correction or revocationAdds the reason and the new state without erasing history

Three uses that never convert into each other directly

Contribution historyShows verifiable work records within the permitted scope
Relationship and reputation viewDerived from events; explainable, correctable and open to appeal
Input to opportunity matchingOnly produces candidate suggestions; never decides high-impact admission automatically
Separate reward rulesContract, budget, review and settlement are established separately

Data and entitlement boundaries

Privacy and visibilityPrivate project information does not become public because of a contribution record
Export and portabilityIncludes scope, version, correction and revocation status
Rule versionsA change in the attribution method never silently rewrites past evaluations
Audit and anti-abuseNo entitlement can be gained by inflating volume, circular trading or self-certification

Source

This page follows A12 of the MYRILUM architecture map v2.2 (public edition: restricted products and internal open items are left out). Related: “Business domains and fact authority”; “Commerce and the five ledgers”; “Commands, events and consistency”.

Was this page helpful?

MYRILUM platform architecture overviewSee how participants, the unified entry, business platform domains, the shared core, the agent layer, the execution network and infrastructure are layered, and how governance runs through all of them.Business domains and fact authorityEvery kind of official record has exactly one owner that may write it: how the twelve business domains divide the work, how product views map onto them, and why suggestions and official records stay separate.Commerce and the five ledgersTransactions define commitments, metering records consumption and ledgers record changes in value; fulfilment and acceptance are never replaced by a successful payment.Commands, events and consistencyIn-domain transactions, cross-domain events, derived views and external side effects are handled separately; there is no promise of global exactly-once execution, but duplicates, delays and reordering never produce a wrong result.What is available now?What MYRILUM officially operates today: distinguish website browsing, the member store, scoped delivery and component records, and check availability for the region and account.
Sources and maintenance
Region
Global
Version
0.1.0
Publication
Published globally
Document status
Approved · Drafted
Authorization
Public information
Command authority
None
Type
Concept
Audience
Technical leads, Developers, Organization leaders, Integration partners, Agents
Safety class
Informational
Agent tasks
understand_platform_architecture
Owner
Web3Capital Documentation Steward
Last verified
2026-09-23
Review due
2026-10-23
Source commit
6b41cce4496d
Canonical authority
SRC-ARCHITECTURE-ATLAS-V2-2
Content digest
31546cd4932dd014
Stable citation
MYRILUM-DOC-ARCH-012@0.1.0:en#overview

Machine-readableMarkdownMetadataJSON-LDChunks

This documentation grants no execution, release, or production authority.

Sources and maintenance

Region
Global
Version
0.1.0
Publication
Published globally
Document status
Approved · Drafted
Authorization
Public information
Command authority
None
Type
Concept
Audience
Technical leads, Developers, Organization leaders, Integration partners, Agents
Safety class
Informational
Agent tasks
understand_platform_architecture
Owner
Web3Capital Documentation Steward
Last verified
2026-09-23
Review due
2026-10-23
Source commit
6b41cce4496d
Canonical authority
SRC-ARCHITECTURE-ATLAS-V2-2
Content digest
31546cd4932dd014
Stable citation
MYRILUM-DOC-ARCH-012@0.1.0:en#overview

This documentation grants no execution, release, or production authority.