How morpheusais/docs works
1. This repository is primarily a documentation and reference hub for the Morpheus ecosystem, not an application codebase. It organizes the project’s protocol design, tokenomics, contracts, guides, audits, and launch history in one place.
2. The top-level structure is audience-driven. The main functional partitions are:
- Capital Providers
- Code Providers
- Compute Providers
- FAQs & Guides
- Morpheus Fundamentals
- Smart Contracts
- Security Audit Reports
- Graphics and brand assets
- Contributions and proof-of-contribution records
3. The README.md acts as the system overview. It defines Morpheus as “A Network For Powering Smart Agents” and frames the core product architecture as a local smart-agent experience plus Web3 infrastructure, with the important operating rule that agents do not hold private keys or autonomously execute transactions.
4. The protocol/economic layer is documented in the “Fundamentals” and “Capital Providers” sections. Key topics here are MOR tokenomics, emissions, burn mechanics, staking rewards, protection fund details, liquidity/AMM launch phases, and Techno Capital Machine concepts. These docs describe how capital flows into and out of the network and how participants are incentivized.
5. The smart-contract layer is explicitly separated under Smart Contracts/. The documented contracts include:
- Distribution
- L1Sender
- L2MessageReceiver
- L2TokenReceiverV2
- LinearDistributionIntervalDecrease
- MOROFT
This suggests a multi-contract architecture that handles token distribution, cross-chain messaging, token transfers, and time-based reward schedules.
6. Cross-chain operation is a major boundary in the repository. The README lists MOR contract addresses on Ethereum, Arbitrum, and Base, and the docs include bridge/claim guides for both mainnet and testnet. The presence of L1/L2 sender and receiver contracts indicates a deliberate separation between canonical L1 logic and L2 token/reward handling.
7. The compute subsystem is documented separately under “Compute Providers.” It covers compute nodes, subnets, model registry, and the Morpheus/Lumerin model family. This part of the architecture represents the off-chain AI/inference side of the network: providers contribute compute capacity, and the docs define how those resources are identified, organized, and consumed.
8. The code-contributor subsystem is also distinct. “Code Providers” documents contribution weights, maintenance, best practices, and reference implementations. The contribution model is not just social; it is part of the protocol’s incentive architecture, with documented weighting and proof-of-contribution flows.
9. Operational user flows are captured in the guide collections. These include staking, rewards claiming, token swaps, wallet integration, testnet/mainnet walkthroughs, and developer setup guides for macOS and Windows. That makes the repo a procedural source of truth for both end users and operators interacting with the protocol.
10. The Contributions/ folder formalizes recognition and rewards, especially for code, compute, and community work. This is part of the network’s governance/incentive boundary: contribution evidence is documented separately from the protocol specs.
11. Security Audit Reports/ is a distinct trust and verification layer. It aggregates audits for the distribution contracts, L2 token receiver, MOR OFT token, builders, and related components. For architecture purposes, this folder is the assurance boundary for the on-chain subsystem.
12. Archive/ and Archive/Translations/ show that the repository is also a versioned knowledge base. Historical docs, prior testnet/mainnet guides, and multilingual translations are preserved as reference material rather than active system components.
13. Graphics/ contains the visual/documentation asset pipeline: diagrams, logos, brand kits, and per-guide illustrations. These assets support the docs and user onboarding, but do not appear to affect runtime behavior.
14. The repo links out to the actual implementation repositories:
- moragents for the local agent product
- SmartContracts for contract code
- DashBoard for the frontend dashboard
- Morpheus-Lumerin-Node for compute infrastructure
- MOR20 for token contracts
- MRC for request-for-comment/specification work
So the architecture here is a documentation control plane over a distributed ecosystem of off-repo runtime components.
15. In diagram terms, the main boundaries are: documentation/specification, on-chain contracts, off-chain compute/agents, contribution accounting, and cross-chain token distribution. This repository describes how those pieces fit together, but it is not itself the execution environment.
Main entry points: README.md README · Smart Contracts Smart Contracts · Capital Providers, MOR20, TCM Capital Providers · FAQs & Guides FAQs & Guides
Components 19
Documentation hub
Primary reference and control-plane documentation for the Morpheus ecosystem.
- README · Top-level system overview for Morpheus as a smart-agent network.
README.md
Protocol economics
Tokenomics, emissions, launch phases, and capital-provider mechanics.
- Fundamentals · Core protocol concepts, freedoms, tokenomics, and launch framing.
!KEYDOCS README FIRST!/Morpheus Fundamentals - Capital Providers · Capital-side tokenomics, AMM launch, liquidity, emissions, and TCM material.
!KEYDOCS README FIRST!/Capital Providers, MOR20, TCM
Provider systems
Compute and code contribution models documented for the network.
- Code Providers · Code contribution weights, best practices, and MRI reference material.
!KEYDOCS README FIRST!/Code Providers - Compute Providers · Off-chain inference, nodes, subnets, and model registry documentation.
!KEYDOCS README FIRST!/Compute Providers
On-chain subsystem
Contract architecture, cross-chain handling, and assurance reports.
- Smart Contracts · Documented on-chain contracts and their responsibilities.
Smart Contracts - Audit Reports · Security audits and bug-bounty records for the on-chain and compute layers.
Security Audit Reports - Distribution · Token distribution and rewards contract documentation.
Smart Contracts/Distribution.md - L1 Sender · Canonical L1-side messaging and transfer initiation.
Smart Contracts/L1Sender.md - L2 Receiver · L2-side message receipt and processing.
Smart Contracts/L2MessageReceiver.md - L2 Token Receiver · L2 token-receipt handling for MOR and reward flows.
Smart Contracts/L2TokenReceiverV2.md - Interval Decrease · Time-based distribution schedule logic.
Smart Contracts/LinearDistributionIntervalDecrease.md - MOROFT · Cross-chain MOR token contract documentation.
Smart Contracts/MOROFT.md
Operations and support
Guides, FAQs, contribution records, archives, and brand assets.
- FAQs & Guides · Operational walkthroughs, FAQs, and launch/reward guides.
!KEYDOCS README FIRST!/FAQs & Guides - Contributions · Proof-of-contribution records for code, compute, and community work.
Contributions - Archive · Versioned legacy guides, prior releases, and translated reference material.
Archive - Graphics · Diagrams, logos, and documentation illustration assets.
Graphics - Multisig Log · Historical multisignature activity record.
MultisigLog - Guide Collections · Mainnet, testnet, staking, bridging, swap, and setup walkthroughs.
!KEYDOCS README FIRST!/FAQs & Guides/Guides
Connections 25
- README → Fundamentals: frames · README points into the core protocol narrative.
- README → Capital Providers: organizes · README routes readers to capital-provider economics.
- README → Code Providers: organizes · README routes readers to code-provider documentation.
- README → Compute Providers: organizes · README routes readers to compute-provider documentation.
- README → FAQs & Guides: links · README connects to operational guides and FAQs.
- README → Smart Contracts: separates · README distinguishes the on-chain subsystem.
- README → Audit Reports: trusts · README connects the protocol to its assurance layer.
- README → Contributions: records · README links to contribution accounting artifacts.
- Fundamentals → Capital Providers: informs · Protocol fundamentals feed tokenomics and launch mechanics.
- Capital Providers → Distribution: uses · Capital-provider mechanics rely on distribution logic.
- Capital Providers → Interval Decrease: uses · Reward flows depend on interval-based schedules.
- Capital Providers → MOROFT: centers on · Capital docs describe MOR token and launch behavior.
- Smart Contracts → Distribution: includes · Distribution is a core documented contract.
- Smart Contracts → L1 Sender: includes · L1 sender is part of the cross-chain contract set.
- Smart Contracts → L2 Receiver: includes · L2 message receiver is part of the cross-chain contract set.
- Smart Contracts → L2 Token Receiver: includes · L2 token receiver handles L2 token flows.
- Smart Contracts → Interval Decrease: includes · Distribution scheduling is documented as a contract component.
- Smart Contracts → MOROFT: includes · MOROFT represents the cross-chain token contract.
- FAQs & Guides → Guide Collections: contains · The guide collection is the operational entry point.
- Compute Providers → FAQs & Guides: supports · Compute documentation is paired with setup and usage guides.
- Code Providers → Contributions: feeds · Contribution weights and best practices connect to proof-of-contribution records.
- Audit Reports → Smart Contracts: verifies · Audit reports provide assurance for the on-chain subsystem.
- Archive → Fundamentals: preserves · Archived reference material captures earlier protocol docs.
- Graphics → FAQs & Guides: supports · Brand and diagram assets support the guide layer.
- Multisig Log → Capital Providers: tracks · Multisig history relates to capital and treasury operations.