docs: Olas marketplace gap analysis and integration plan

[5queezer]

Summary

• Comprehensive gap analysis comparing Hrafn's capabilities against Olas marketplace requirements (based on Olas whitepaper and ecosystem documentation)
• Identifies 7 critical gaps (EVM wallet, OLAS token handling, Mech protocol, IPFS, on-chain registration, SDK packaging, Safe account abstraction)
• Maps 15 existing Hrafn strengths that directly serve Olas integration (Docker runtime, A2A protocol, tool system, SOP workflows, security policy engine, etc.)
• Proposes a 4-phase integration plan using the Olas SDK wrapper path (framework-agnostic) — not the Python Open Autonomy rewrite

Phases

Phase	Goal	Risk
0	Olas SDK packaging (Docker + config files → marketplace listing)	Low
1	EVM wallet integration (alloy crate, Safe account abstraction)	High
2	Mech protocol (accept/fulfill AI task requests for revenue)	High
3	OLAS staking (PoAA checkpoints via cron integration)	High
4	Multi-agent consensus (deferred — sovereign mode sufficient)	Very High

All new code behind olas feature flag, not added to default. Zero impact on existing builds.

Test plan

• Review gap analysis accuracy against current Olas documentation
• Validate architecture mappings (Mech→SOP, TaskStore→A2A, etc.)
• Confirm alloy crate is appropriate choice over ethers-rs
• Review PR sequence for correct dependency ordering
• Docs-only change — no code/test verification needed

https://claude.ai/code/session_01UaUk99orR49tGSqCEKEkp1

Summary by CodeRabbit

• Documentation
  • Added comprehensive Olas marketplace integration guidance: current capability assessment, identified critical and competitive gaps, and a detailed multi-phase roadmap (Phases 0–4) with phased deliverables, risk tiers, PR sequencing guidance, and cross-cutting analysis covering security, observability, configuration migration, and binary-size considerations.

[coderabbitai]

Warning

Rate limit exceeded

@5queezer has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 6 minutes and 55 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 6 minutes and 55 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: a267cbf2-fce6-4c88-8b1a-ce1f7c762aca

📥 Commits

Reviewing files that changed from the base of the PR and between 47d265a and fd88500.

📒 Files selected for processing (1)

• docs/architecture/olas-marketplace-gap-analysis.md

📝 Walkthrough

Walkthrough

Adds a new architecture document performing Hrafn’s gap analysis against the Olas marketplace and a phased integration roadmap (Phase 0–4) that enumerates existing capabilities, missing components, and required modules/configuration for incremental integration.

Changes

Cohort / File(s)

Summary

Gap Analysis Documentation docs/architecture/olas-marketplace-gap-analysis.md

New architecture doc describing current capability mapping to Olas requirements, listing critical and higher-complexity gaps (EVM wallet/signing, OLAS token handling, on-chain registration, IPFS, Mech protocol, Safe/account abstraction, consensus/networking options), and a Phase 0–4 implementation plan with feature flags, config schema, module/tool additions, staking/PoAA steps, cross-cutting concerns, and a proposed PR sequence.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description provides a comprehensive summary, identifies critical gaps and strengths, outlines a phased plan, and includes a test plan checklist. However, it deviates significantly from the repository's description template by omitting or minimizing the standard sections (What, How to test, Breaking changes, Security, Checklist).	Restructure the description to follow the repository template more closely: add a concise 'What' section linking the issue, clarify 'How to test' (beyond reviewing docs), confirm no breaking changes, and complete the standard checklist items where applicable.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change—a documentation-only gap analysis and integration plan for Olas marketplace compatibility.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/hrafn-olas-gap-analysis-JQd8y

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/architecture/olas-marketplace-gap-analysis.md`:
- Around line 184-209: The markdown has duplicate section headings "#### New
modules" causing MD024; update the two identical headings to be unique and
phase-specific (e.g., change the first "#### New modules" near the IPFS
strategy/Mech module list to "#### New modules (Phase 2)" and change the later
one above "Phase 3: OLAS Staking (PoAA)" to "#### New modules (Phase 3)") so
each heading is unique and the MD024 lint warning is resolved.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: c80bb73e-cc9f-43dc-b791-a7debdb4b6f8

📥 Commits

Reviewing files that changed from the base of the PR and between d14dd4e and b68f2fb.

📒 Files selected for processing (1)

• docs/architecture/olas-marketplace-gap-analysis.md

[5queezer]

@coderabbitai review the proposal

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

Let me read the document and gather relevant background information before providing a thorough review.

Now let me read the actual document:

---

🏁 Script executed:

#!/bin/bash
# Read the gap analysis document
fd "olas-marketplace-gap-analysis.md" --exec cat {}

# Check for any existing EVM/Olas/alloy/ethers related code
echo "=== Existing EVM/Olas/alloy/ethers references ==="
rg -rn "alloy|ethers|olas|evm|wallet|web3" --type rust -l 2>/dev/null | head -20

echo "=== Cargo.toml dependencies ==="
fd "Cargo.toml" -d 2 --exec cat {} 2>/dev/null

echo "=== Existing feature flags ==="
rg -n "feature" Cargo.toml 2>/dev/null | head -30

echo "=== Existing IPFS references ==="
rg -rn "ipfs" -l 2>/dev/null | head -10

echo "=== Check docs directory structure ==="
tree docs/ 2>/dev/null || find docs/ -type f 2>/dev/null | head -30

Length of output: 34019

---

🏁 Script executed:

#!/bin/bash
fd "olas-marketplace-gap-analysis.md" --exec cat {}

echo ""
echo "=== Existing Rust feature flags ==="
fd "Cargo.toml" -d 3 --exec grep -l "features" {} 2>/dev/null | head -5 | xargs grep -A5 "\[features\]" 2>/dev/null | head -50

echo ""
echo "=== Check for any existing signing/crypto code ==="
rg -rn "sign|crypto|key|wallet" --type rust -l 2>/dev/null | head -10

echo ""
echo "=== Check docs directory ==="
find docs/ -type f -name "*.md" 2>/dev/null | sort

Length of output: 15849

---

🏁 Script executed:

#!/bin/bash
# Check doc structure and related existing docs
find . -name "*.md" -path "*/docs/*" | sort | head -30
echo "---"
cat docs/architecture/olas-marketplace-gap-analysis.md 2>/dev/null || find . -name "olas-marketplace-gap-analysis.md" -exec cat {} \;

Length of output: 12914

---