Repository: pragma-org/amaru
Pull request #202: Updated maintainers: Treasury proposal
Author: login: Dam-CZ
Created: 2025-05-02T03:56:44Z | Merged: 2025-05-14T07:21:45Z

Added scope: PR & Marketing, owner: Damien Czapla

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit

- **Documentation**
  - Updated the maintainers committee documentation to include Damien Czapla as a new member with responsibilities in PR and Marketing.
  - Expanded the committee table and added relevant references for the new member.
  - Added detailed documentation on budget administration, scope ownership, and project timelines for Q3 and Q4 2025.
  - Introduced new scopes including "Ad-Hoc mercenaries" and "Project Management, Public Relations & Marketing" with outlined activities and milestones.
  - Described the budget management process supported by an on-chain smart contract with defined controls and failsafe mechanisms.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->


Diff:
diff --git a/engineering-decision-records/005-amaru-maintainers-committee.md b/engineering-decision-records/005-amaru-maintainers-committee.md
index 6410bc60c..a5c85c3ed 100644
--- a/engineering-decision-records/005-amaru-maintainers-committee.md
+++ b/engineering-decision-records/005-amaru-maintainers-committee.md
@@ -21,15 +21,16 @@ In order to manage the decision making on the project and have a compelling prod
 
 Here is the new composition of the Amaru maintainers committee (scope owners of the project):
 
-| Matthias Benkort <br/> <img src="https://github.com/ktorz.png" width=50 height=50 /> <br/> [@KtorZ][] | Santiago Carmuega <br/> <img src="https://github.com/scarmuega.png" width=50 height=50 /> <br/> [@scarmuega][] | Pi Lanningham <br/> <img src="https://github.com/quantumplation.png" width=50 height=50 /> <br/> [@QuantumPlation][] |  Arnaud Bailly <br/> <img src="https://github.com/abailly.png" width=50 height=50 /> <br/> [@abailly][] |
-| --- | --- | --- | --- |
-| Ledger & integration | Networking | Mempool & Middleware | Consensus |
+| Matthias Benkort <br/> <img src="https://github.com/ktorz.png" width=50 height=50 /> <br/> [@KtorZ][] | Santiago Carmuega <br/> <img src="https://github.com/scarmuega.png" width=50 height=50 /> <br/> [@scarmuega][] | Pi Lanningham <br/> <img src="https://github.com/quantumplation.png" width=50 height=50 /> <br/> [@QuantumPlation][] |  Arnaud Bailly <br/> <img src="https://github.com/abailly.png" width=50 height=50 /> <br/> [@abailly][] |  Damien Czapla <br/> <img src="https://avatars.githubusercontent.com/u/161828179?v=4" width=50 height=50 /> <br/> [@Dam-CZ][] |
+| --- | --- | --- | --- | --- |
+| Ledger & integration | Networking | Mempool & Middleware | Consensus | Project management, PR, Marketing |
 
 
 [@KtorZ]: https://github.com/ktorz
 [@scarmuega]: https://github.com/scarmuega
 [@Quantumplation]: https://github.com/Quantumplation
 [@abailly]: https://github.com/abailly
+[@Dam-CZ]: https://github.com/Dam-CZ
 
 [Matthias Benkort - @KtorZ](https://github.com/KtorZ) provides the ultimate voice in decision-making regarding final integration and architectural designs. Furthermore, Amaru has close relationship with the following projects and their respective owners:
 
@@ -44,3 +45,5 @@ Here is the new composition of the Amaru maintainers committee (scope owners of
 - We need to have a diverse enough point of view in the maintainers committee to enlighten the decision making process
 - Each scope owner on the project still has the decision making power for everything that relates specifically to his scope
 - The maintainer committee reach a decision by having a minimum of four votes in favour of a decisions for it to be accepted
+
+
diff --git a/engineering-decision-records/006-design-phase-documentation.md b/engineering-decision-records/006-design-phase-documentation.md
index 8edd29b4e..da287ff6b 100644
--- a/engineering-decision-records/006-design-phase-documentation.md
+++ b/engineering-decision-records/006-design-phase-documentation.md
@@ -171,4 +171,99 @@ For each of the scopes that are linked with our project but aren't hosted in the
 - Pallas owner: [Santiago Carmuega](https://github.com/scarmuega) see: [Pallas Github](https://github.com/txpipe/pallas) [Pallas proposal](https://gov.tools/budget_discussion/41)
 - UPLC VM owner: [Lucas Rosa](https://github.com/rvcas) see: [UPLC Github](https://github.com/pragma-org/uplc)
 
-This will be updated when we better understand the product and our project environment after each delivery step.
+### Treasury proposal: scope owners and budget administration
+
+The Amaru team submitted a proposal with a list of scopes related to the project and describing a specific way of administrating the budget, this is now reflected into the ways of working of the project.
+
+#### Scopes described in the proposal
+
+![2025_04_13_Amaru_ask](https://github.com/user-attachments/assets/041dacde-5717-4b6f-87a8-1fc279d47e23)
+
+
+> [!TIP]
+> The scopes described here are what the Amaru team expects to deliver in Q3 & Q4 2025
+> For example the Networking is not included as it will already be delivered, but some integration might be required, that's the purpose of the "Ad-Hoc mercenaries"
+
+Scope | Owner | Estimated effort | Resources already secured | Resources needed
+---   | ---   | ---                | ---                       | ---
+Ledger | Matthias | 2.5 FTEs | 1 FTE | 1.5 FTEs
+Consensus | Arnaud | 2.5 FTEs | 1 FTE | 1.5 FTEs
+Networking | Santiago | 1 FTE | 1 FTE | 0 FTEs
+Ad-hoc Mercenaries | Pi | 2.5 FTEs | 0 FTEs | 2.5 FTEs
+Project Management, Public Relations & Marketing | Damien | 0.5 FTEs | 0 FTEs | 0.5 FTEs
+
+#### New scopes from the proposal
+
+##### Ad-Hoc mercernaries
+
+
+**Purpose:** troubleshoot the gaps not planned for and articulate smart problem solving on the project.
+
+Examples of activities:
+- Troubleshoot integration activities
+- Interface
+- Specific use case development, testing and delivery
+
+One of the scopes that will be carried by the Ad-Hoc team will be the Mempool as it requires strong interfacing with the rest of the team.
+This includes:
+- Mempool library: Build a standalone library (data structure that represents transactions in memory) with an interface to get an extract of these transactions
+- "Simple" mempool implementation: Build a basic mempool that adds, remove, gather, drain transactions and exposes a new ledger state
+- "Complex" mempool implementation: Build a more refined version of the mempool that handles features differently and optimises the overall resources consumption
+- Mempool tooling and API: Create a tool able to manage the mempool and the modularity
+- Node management Remote Procedure Call (RPC): Build a software that handles the "operator perspective" on operating the Amaru node
+- Block forging: Develop a component able to forge blocs
+
+Timeline:
+- Mempool library: done
+- "Simple" mempool implementation: Q2 2025
+- Block forging: Q3 2025
+- "Complex" mempool implementation: Q4 2025
+
+#### Project Management, Public relations and Marketing
+
+**Purpose:** drive key initiatives and manage use cases and end users feedback loops. 
+
+The current set of activities forecasted are: 
+- Creating and managing SPO working groups to actively improve the operator side of Amaru 
+- Organizing and facilitating workshops related to key explorations of the product
+- Marketing, implementation partnerships alignment, use case specific collaborations
+- Roadmaps interfaces and scopes alignment synchronization 
+- Bug bounty: create an incentive to generate traffic on the testnet preprod and bring contributors to the project
+> *Testnet developer bounty:* Create on preprod the use cases defined by the Amaru team by building the transactions on the network and generate the conditions needed  
+> *Testnet SPO bounty:* Produce a block that includes the above use case   
+> *Amaru development bounty:* be involved in at least 3 contributions accepted by maintainers   
+
+Our current ambition is to experiment with Amaru as much as we can with testnet activity, conformance tests, simulations and build (with the feedback of early adopters) a reliable setup that fullfills all our global targets.
+
+Each bounded context will share ownership over a resource that will interface with all the stakeholders of the Amaru project to facilitate the activities mentioned above.
+
+Timeline:
+- SPO working group setup and key initiatives: Q3 2025
+- Bug bounty setup and start: Q3 2025
+- Amaru workshops: Every quarter
+
+
+#### Administration of the budget
+
+The maintainer committee will ensure **direct administration** of the budget, assisted with **an on-chain smart contract** (developed in open source, still incomplete, but aimed to be done and fully audited by the time of the first withdrawal). The smart contract's role is to ensure that the expenditure of funds is done in accordance with the scope defined in this budget and authorized by the relevant scope owners. 
+
+We recognize the following capabilities of this contract:
+
+1. **Standard withdrawal**: A scope owner asks other scope owners for money to be withdrawn from his scope.
+2. **Contingency withdrawal**: A scope owner asks other scope owners to withdraw an amount from the contingency funds.
+3. **Scope reconciliation**: A scope owner asks other scope owners for a change of ownership (or a reallocation of budget).
+4. **Contingency refund/closing**: scope owners ask to send the leftovers from the contingency budget to be sent back to the Cardano treasury.
+5. **Credential rotation**: In case of lost credentials or the departure of a scope owner, a mechanism allows the rotation of credentials to a new scope owner upon approval by all (5 out of 5) PRAGMA members (effectively capturing PRAGMA's board decision to appoint new maintainers).
+6. **Failsafe**: In the extreme scenario where credentials would be irremediably lost, thus preventing any further decision, a failsafe mechanism allows all unconsumed funds to be sent back to the Cardano treasury.   
+
+#### Acceptance process for milestones and deliverables on the project
+
+Any milestone or delivery item will have to go through this process:
+- Submit a pull request to the Amaru repo on the main branch
+- Demonstrate evidence of testing: once implemented in the Amaru context, make reports available to show that the expected features are working within the targeted environment.
+- Formally review with the Amaru Maintainer Committee the pull request (in the recurrent bi-monthly maintainer meeting or in a dedicated meeting)
+- Finalise with the scope owner the integration and merge the pull request into the Amaru repo
+
+## Discussion points
+
+This documentation will be updated when we better understand the product and our project environment after each delivery step.


Reviews:
user: login: coderabbitai[bot]
body: **Actionable comments posted: 2**

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: CHILL**
**Plan: Pro**

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between fb54192da0059ecbf95cb4f14f9f912bd4904877 and c93c95e32bb554c9560edb21af693ef50f17edc2.

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* `engineering-decision-records/005-amaru-maintainers-committee.md` (2 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>🪛 markdownlint-cli2 (0.17.2)</summary>

<details>
<summary>engineering-decision-records/005-amaru-maintainers-committee.md</summary>

24-24: Images should have alternate text (alt text)
null

(MD045, no-alt-text)

---

24-24: Images should have alternate text (alt text)
null

(MD045, no-alt-text)

---

24-24: Images should have alternate text (alt text)
null

(MD045, no-alt-text)

---

24-24: Images should have alternate text (alt text)
null

(MD045, no-alt-text)

---

24-24: Images should have alternate text (alt text)
null

(MD045, no-alt-text)

</details>

</details>

</details>

<details>
<summary>⏰ Context from checks skipped due to timeout of 90000ms (4)</summary>

* GitHub Check: Snapshots (preprod, 10.1.4)
* GitHub Check: coverage
* GitHub Check: Build on ubuntu-latest with target riscv32im-risc0-zkvm-elf
* GitHub Check: Build on windows-latest with target x86_64-pc-windows-msvc

</details>

<details>
<summary>🔇 Additional comments (1)</summary><blockquote>

<details>
<summary>engineering-decision-records/005-amaru-maintainers-committee.md (1)</summary>

`26-26`: **Confirm punctuation for the “PR & Marketing” scope label.**

The PR description mentions “PR & Marketing” but the table uses “PR, Marketing”. Could you double-check which you prefer? Ampersand or comma?

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-02T03:59:13Z
user: login: coderabbitai[bot]
body: **Actionable comments posted: 3**

<details>
<summary>🧹 Nitpick comments (4)</summary><blockquote>

<details>
<summary>engineering-decision-records/006-design-phase-documentation.md (4)</summary><blockquote>

`174-177`: **Add cross-reference to the Maintainers Committee update**  
Ah, this Treasury section is sweet, but let’s drop in a link to ADR 005 or PR #202 so readers don’t have to go hunting.  


```diff
-The Amaru team submitted a proposal with a list of scopes related to the project and describing a specific way of administrating the budget, this is now reflected into the ways of working of the project.
+The Amaru team submitted a proposal with a list of scopes related to the project (see [ADR 005 – Maintainers Committee](../005-amaru-maintainers-committee.md) or [PR #202](https://github.com/pragma-org/amaru/pull/202)) and describing a specific way of administrating the budget; this is now reflected in the project’s ways of working.
```

---

`178-187`: **Enhance image alt text for better accessibility**  
Love the visual, but let’s swap that auto-generated filename alt text for something more meaningful to screen-readers.  


```diff
-![2025_04_13_Amaru_ask](https://github.com/user-attachments/assets/041dacde-5717-4b6f-87a8-1fc279d47e23)
+![Requested scopes and FTE breakdown for Q3 & Q4 2025](https://github.com/user-attachments/assets/041dacde-5717-4b6f-87a8-1fc279d47e23)
```

---

`202-205`: **Clarify the bullet “Interface” for folks**  
That lone “Interface” bullet feels like a stub—can you specify what interface is meant?  


```diff
-  - Interface
+  - Interface with other modules for integration
```

---

`246-249`: **Capitalize the committee name & link to the contract repo**  
Let’s stick to “Maintainers Committee” and point to the on-chain smart contract repo so devs can find the code.  


```diff
-#### Administration of the budget
+#### Administration of the Budget

-The maintainer committee will ensure **direct administration** of the budget, assisted with **an on-chain smart contract** (developed in open source, still incomplete, but aimed to be done and fully audited by the time of the first withdrawal).
+The **Maintainers Committee** will ensure **direct administration** of the budget, assisted with an on-chain [smart contract](https://github.com/pragma-org/amaru-treasury-contract) (open-source, in progress, to be fully audited before first withdrawal).
```

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: CHILL**
**Plan: Lite**

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between c93c95e32bb554c9560edb21af693ef50f17edc2 and 95099fa7e2d02e92d2a7fe20316238deb08a9ae4.

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* `engineering-decision-records/006-design-phase-documentation.md` (1 hunks)

</details>

<details>
<summary>🔇 Additional comments (1)</summary><blockquote>

<details>
<summary>engineering-decision-records/006-design-phase-documentation.md (1)</summary>

`216-221`: **Looks good—timeline is crystal clear!**  
Nice and concise milestones for the mercenaries squad.

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-02T04:18:04Z
user: login: coderabbitai[bot]
body: **Actionable comments posted: 1**

<details>
<summary>♻️ Duplicate comments (4)</summary><blockquote>

<details>
<summary>engineering-decision-records/006-design-phase-documentation.md (4)</summary><blockquote>

`187-194`: **Duplicate: Use full maintainer name with GitHub link**  
As raised earlier, let's link the full name to avoid confusion:
```diff
- Project Management, Public Relations & Marketing | Damien | 0.5 FTEs | 0 FTEs | 0.5 FTEs
+ Project Management, Public Relations & Marketing | [Damien Czapla](https://github.com/Dam-CZ) | 0.5 FTEs | 0 FTEs | 0.5 FTEs
```

---

`232-234`: **Switch blockquoted bounties to bullet list**  
Blockquotes are cool—like cryptic Dark Souls messages—but here bullets’ll feel smoother:
```diff
- > *Testnet developer bounty:* Create on preprod...
+ - **Testnet developer bounty:** Create on preprod...
- > *Testnet SPO bounty:* Produce a block...
+ - **Testnet SPO bounty:** Produce a block...
- > *Amaru development bounty:* be involved...
+ - **Amaru development bounty:** Be involved...
```

---

`197-197`: _⚠️ Potential issue_

**Fix typo in scope heading**  
Heads up—"mercernaries" is misspelled. Change to "mercenaries":
```diff
- ##### Ad-Hoc mercernaries
+ ##### Ad-Hoc Mercenaries
```

---

`222-222`: _⚠️ Potential issue_

**Inconsistent heading styling**  
The heading should mirror the table's ampersand and capitalization:
```diff
- #### Project Management, Public relations and Marketing
+ #### Project Management, Public Relations & Marketing
```

</blockquote></details>

</blockquote></details>

<details>
<summary>🧹 Nitpick comments (2)</summary><blockquote>

<details>
<summary>engineering-decision-records/006-design-phase-documentation.md (2)</summary><blockquote>

`176-176`: **Tiny grammar tweak**  
Tiny grammar tweak, mate—swap "administrating the budget" for "administering the budget" to level up the wording.

---

`192-192`: **Consistent scope naming for Ad-Hoc Mercenaries**  
Let’s keep the name uniform across table and heading—use "Ad-Hoc Mercenaries".

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: CHILL**
**Plan: Lite**

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between 64156c78266251cf4ddc875a1923e77c56357466 and 9cd338e724715cb8adce3337f0edc9386270c50e.

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* `engineering-decision-records/006-design-phase-documentation.md` (1 hunks)

</details>

<details>
<summary>🔇 Additional comments (1)</summary><blockquote>

<details>
<summary>engineering-decision-records/006-design-phase-documentation.md (1)</summary>

`174-174`: **Sweet addition of treasury proposal section**  
Loving how this new section ties budget ownership and admin flows together—feels like equipping the perfect RPG party lineup. 🍻

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-02T07:31:23Z
user: login: coderabbitai[bot]
body: **Actionable comments posted: 0**

<details>
<summary>♻️ Duplicate comments (3)</summary><blockquote>

<details>
<summary>engineering-decision-records/006-design-phase-documentation.md (3)</summary><blockquote>

`192-192`: **Fix capitalization of “Ad-Hoc Mercenaries”**

G’day, mate! This scope’s casing is doing the worm on us—should be “Ad-Hoc Mercenaries” to keep that consistent title-case vibe. Think of it as giving your RPG guild the proper legend status.

```diff
- Ad-hoc Mercenaries
+ Ad-Hoc Mercenaries
```

---

`236-236`: _⚠️ Potential issue_

**Fix spelling: “fullfills” → “fulfills”**

Crikey, that typo’s more jarring than a loot box disappointment—let’s correct “fullfills” to “fulfills” and keep it tidy:

```diff
- a reliable setup that fullfills all our global targets
+ a reliable setup that fulfills all our global targets
```

---

`197-197`: _🛠️ Refactor suggestion_

**Correct typo in scope heading**

Oi, just spotted a typo tripping over its shoelaces—“mercernaries” isn’t a word! Let’s get that fix:

```diff
- ##### Ad-Hoc mercernaries
+ ##### Ad-Hoc Mercenaries
```

</blockquote></details>

</blockquote></details>

<details>
<summary>🧹 Nitpick comments (2)</summary><blockquote>

<details>
<summary>engineering-decision-records/006-design-phase-documentation.md (2)</summary><blockquote>

`193-193`: **Link full maintainer name for consistency**

Cheers, let’s be explicit like a proper credits roll—swap “Damien” for “Damien Czapla” with GitHub link so folks know the hero behind the scenes.

```diff
- Project Management, Public Relations & Marketing | Damien
+ Project Management, Public Relations & Marketing | [Damien Czapla](https://github.com/Dam-CZ)
```

---

`222-222`: **Unify header casing & ampersand usage**

We gotta sync this header like a boss fight—match the table and rock “Public Relations & Marketing” in full title-case with an ampersand.

```diff
- #### Project Management, Public relations and Marketing
+ #### Project Management, Public Relations & Marketing
```

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: CHILL**
**Plan: Lite**

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between 9cd338e724715cb8adce3337f0edc9386270c50e and fa4fa286058f947fcf18a269466b90dfa1363476.

</details>

<details>
<summary>📒 Files selected for processing (2)</summary>

* `engineering-decision-records/005-amaru-maintainers-committee.md` (2 hunks)
* `engineering-decision-records/006-design-phase-documentation.md` (1 hunks)

</details>

<details>
<summary>🚧 Files skipped from review as they are similar to previous changes (1)</summary>

* engineering-decision-records/005-amaru-maintainers-committee.md

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-02T14:27:20Z

Review comments:
diff_hunk: @@ -21,15 +21,16 @@ In order to manage the decision making on the project and have a compelling prod
 
 Here is the new composition of the Amaru maintainers committee (scope owners of the project):
 
-| Matthias Benkort <br/> <img src="https://github.com/ktorz.png" width=50 height=50 /> <br/> [@KtorZ][] | Santiago Carmuega <br/> <img src="https://github.com/scarmuega.png" width=50 height=50 /> <br/> [@scarmuega][] | Pi Lanningham <br/> <img src="https://github.com/quantumplation.png" width=50 height=50 /> <br/> [@QuantumPlation][] |  Arnaud Bailly <br/> <img src="https://github.com/abailly.png" width=50 height=50 /> <br/> [@abailly][] |
-| --- | --- | --- | --- |
-| Ledger & integration | Networking | Mempool & Middleware | Consensus |
+| Matthias Benkort <br/> <img src="https://github.com/ktorz.png" width=50 height=50 /> <br/> [@KtorZ][] | Santiago Carmuega <br/> <img src="https://github.com/scarmuega.png" width=50 height=50 /> <br/> [@scarmuega][] | Pi Lanningham <br/> <img src="https://github.com/quantumplation.png" width=50 height=50 /> <br/> [@QuantumPlation][] |  Arnaud Bailly <br/> <img src="https://github.com/abailly.png" width=50 height=50 /> <br/> [@abailly][] |  Damien Czapla <br/> <img src="https://avatars.githubusercontent.com/u/161828179?v=4" width=50 height=50 /> <br/> [@Dam-CZ][] |
+| --- | --- | --- | --- | --- |
+| Ledger & integration | Networking | Mempool & Middleware | Consensus | PR, Marketing |
 
 
 [@KtorZ]: https://github.com/ktorz
 [@scarmuega]: https://github.com/scarmuega
 [@Quantumplation]: https://github.com/Quantumplation
 [@abailly]: https://github.com/abailly
+[@Dam-CZ]: https://github.com/Dam-CZ
path: engineering-decision-records/005-amaru-maintainers-committee.md
user: login: coderabbitai[bot]
body: _⚠️ Potential issue_

**Fix reference label casing for QuantumPlation and validate new entry.**

In the table we use `[@QuantumPlation][]` (capital P) but the reference below is `[@Quantumplation]:`. CommonMark might tolerate this, but it can trip some renderers. Also verify the ordering and correctness of the new `[@Dam-CZ]: https://github.com/Dam-CZ`.  
```diff
--- a/engineering-decision-records/005-amaru-maintainers-committee.md
+++ b/engineering-decision-records/005-amaru-maintainers-committee.md
@@ line 31
-[@Quantumplation]: https://github.com/Quantumplation
+[@QuantumPlation]: https://github.com/QuantumPlation
@@ line 33
-[@Dam-CZ]: https://github.com/Dam-CZ
+[@Dam-CZ]: https://github.com/Dam-CZ
```
Ensures the references resolve cleanly.  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
[@QuantumPlation]: https://github.com/QuantumPlation
[@abailly]: https://github.com/abailly
[@Dam-CZ]: https://github.com/Dam-CZ
`````

</details>

<!-- suggestion_end -->

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-02T03:59:12Z
author_association: CONTRIBUTOR
diff_hunk: @@ -21,15 +21,16 @@ In order to manage the decision making on the project and have a compelling prod
 
 Here is the new composition of the Amaru maintainers committee (scope owners of the project):
 
-| Matthias Benkort <br/> <img src="https://github.com/ktorz.png" width=50 height=50 /> <br/> [@KtorZ][] | Santiago Carmuega <br/> <img src="https://github.com/scarmuega.png" width=50 height=50 /> <br/> [@scarmuega][] | Pi Lanningham <br/> <img src="https://github.com/quantumplation.png" width=50 height=50 /> <br/> [@QuantumPlation][] |  Arnaud Bailly <br/> <img src="https://github.com/abailly.png" width=50 height=50 /> <br/> [@abailly][] |
-| --- | --- | --- | --- |
-| Ledger & integration | Networking | Mempool & Middleware | Consensus |
+| Matthias Benkort <br/> <img src="https://github.com/ktorz.png" width=50 height=50 /> <br/> [@KtorZ][] | Santiago Carmuega <br/> <img src="https://github.com/scarmuega.png" width=50 height=50 /> <br/> [@scarmuega][] | Pi Lanningham <br/> <img src="https://github.com/quantumplation.png" width=50 height=50 /> <br/> [@QuantumPlation][] |  Arnaud Bailly <br/> <img src="https://github.com/abailly.png" width=50 height=50 /> <br/> [@abailly][] |  Damien Czapla <br/> <img src="https://avatars.githubusercontent.com/u/161828179?v=4" width=50 height=50 /> <br/> [@Dam-CZ][] |
path: engineering-decision-records/005-amaru-maintainers-committee.md
user: login: coderabbitai[bot]
body: _🛠️ Refactor suggestion_

**Add alt text to avatars and unify avatar URL style.**

Right now the `<img>` tags have no `alt` attribute (MD045), and the new avatar URL uses the raw GitHub CDN link, while the other entries use `https://github.com/<user>.png`. Let’s keep things accessible and consistent:

```diff
--- a/engineering-decision-records/005-amaru-maintainers-committee.md
+++ b/engineering-decision-records/005-amaru-maintainers-committee.md
@@ line 24
-| Damien Czapla <br/> <img src="https://avatars.githubusercontent.com/u/161828179?v=4" width=50 height=50 /> <br/> [@Dam-CZ][]
+| Damien Czapla <br/> <img src="https://github.com/Dam-CZ.png" alt="Damien Czapla avatar" width=50 height=50 /> <br/> [@Dam-CZ][]
```
That’ll keep the look & feel uniform and give us proper screen-reader support. 😉  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
|  Damien Czapla <br/> <img src="https://github.com/Dam-CZ.png" alt="Damien Czapla avatar" width="50" height="50" /> <br/> [@Dam-CZ][] |
`````

</details>

<!-- suggestion_end -->

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 markdownlint-cli2 (0.17.2)</summary>

24-24: Images should have alternate text (alt text)
null

(MD045, no-alt-text)

---

24-24: Images should have alternate text (alt text)
null

(MD045, no-alt-text)

---

24-24: Images should have alternate text (alt text)
null

(MD045, no-alt-text)

---

24-24: Images should have alternate text (alt text)
null

(MD045, no-alt-text)

---

24-24: Images should have alternate text (alt text)
null

(MD045, no-alt-text)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-02T03:59:13Z
author_association: CONTRIBUTOR
diff_hunk: @@ -171,4 +171,90 @@ For each of the scopes that are linked with our project but aren't hosted in the
 - Pallas owner: [Santiago Carmuega](https://github.com/scarmuega) see: [Pallas Github](https://github.com/txpipe/pallas) [Pallas proposal](https://gov.tools/budget_discussion/41)
 - UPLC VM owner: [Lucas Rosa](https://github.com/rvcas) see: [UPLC Github](https://github.com/pragma-org/uplc)
 
-This will be updated when we better understand the product and our project environment after each delivery step.
+### Treasury proposal: scope owners and budget administration
+
+The Amaru team submitted a proposal with a list of scopes related to the project and describing a specific way of administrating the budget, this is now reflected into the ways of working of the project.
+
+#### Scopes described in the proposal
+
+![2025_04_13_Amaru_ask](https://github.com/user-attachments/assets/041dacde-5717-4b6f-87a8-1fc279d47e23)
+
+
+> [!TIP]
+> The scopes described here are what the Amaru team expects to deliver in Q3 & Q4 2025
+> For example the Networking is not included as it will already be delivered, but some integration might be required, that's the purpose of the "Ad-Hoc mercenaries"
+
+Scope | Owner | Estimated effort | Resources already secured | Resources needed
+---   | ---   | ---                | ---                       | ---
+Ledger | Matthias | 2.5 FTEs | 1 FTE | 1.5 FTEs
+Consensus | Arnaud | 2.5 FTEs | 1 FTE | 1.5 FTEs
+Networking | Santiago | 1 FTE | 1 FTE | 0 FTEs
+Ad-hoc Mercenaries | Pi | 2.5 FTEs | 0 FTEs | 2.5 FTEs
+Project Management, Public Relations & Marketing | Damien | 0.5 FTEs | 0 FTEs | 0.5 FTEs
+
+#### New scopes from the proposal
+
+##### Ad-Hoc mercernaries
+
+
+**Purpose:** troubleshoot the gaps not planned for and articulate smart problem solving on the project.
+
path: engineering-decision-records/006-design-phase-documentation.md
user: login: coderabbitai[bot]
body: _🛠️ Refactor suggestion_

**Fix typo & unify “Ad-Hoc Mercenaries” capitalization**  
We’ve got “Ad-hoc Mercenaries” in the table but “Ad-Hoc mercernaries” here—time for a quick alignment (and spelling fix!).  


```diff
-##### Ad-Hoc mercernaries
+##### Ad-Hoc Mercenaries
```


<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
#### New scopes from the proposal

##### Ad-Hoc Mercenaries


**Purpose:** troubleshoot the gaps not planned for and articulate smart problem solving on the project.
`````

</details>

<!-- suggestion_end -->

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-02T04:18:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -171,4 +171,90 @@ For each of the scopes that are linked with our project but aren't hosted in the
 - Pallas owner: [Santiago Carmuega](https://github.com/scarmuega) see: [Pallas Github](https://github.com/txpipe/pallas) [Pallas proposal](https://gov.tools/budget_discussion/41)
 - UPLC VM owner: [Lucas Rosa](https://github.com/rvcas) see: [UPLC Github](https://github.com/pragma-org/uplc)
 
-This will be updated when we better understand the product and our project environment after each delivery step.
+### Treasury proposal: scope owners and budget administration
+
+The Amaru team submitted a proposal with a list of scopes related to the project and describing a specific way of administrating the budget, this is now reflected into the ways of working of the project.
+
+#### Scopes described in the proposal
+
+![2025_04_13_Amaru_ask](https://github.com/user-attachments/assets/041dacde-5717-4b6f-87a8-1fc279d47e23)
+
+
+> [!TIP]
+> The scopes described here are what the Amaru team expects to deliver in Q3 & Q4 2025
+> For example the Networking is not included as it will already be delivered, but some integration might be required, that's the purpose of the "Ad-Hoc mercenaries"
+
+Scope | Owner | Estimated effort | Resources already secured | Resources needed
+---   | ---   | ---                | ---                       | ---
+Ledger | Matthias | 2.5 FTEs | 1 FTE | 1.5 FTEs
+Consensus | Arnaud | 2.5 FTEs | 1 FTE | 1.5 FTEs
+Networking | Santiago | 1 FTE | 1 FTE | 0 FTEs
+Ad-hoc Mercenaries | Pi | 2.5 FTEs | 0 FTEs | 2.5 FTEs
+Project Management, Public Relations & Marketing | Damien | 0.5 FTEs | 0 FTEs | 0.5 FTEs
+
path: engineering-decision-records/006-design-phase-documentation.md
user: login: coderabbitai[bot]
body: _🛠️ Refactor suggestion_

**Use full maintainer name and link for consistency**  
Elsewhere we’re linking folks’ GitHub handles—let’s match that here and spell out “Damien Czapla.”  


```diff
-Scope | Owner | Estimated effort | Resources already secured | Resources needed
+Scope | Owner | Estimated effort | Resources already secured | Resources needed
---   | ---   | ---              | ---                       | ---
 Ledger | Matthias | 2.5 FTEs | 1 FTE | 1.5 FTEs
 Consensus | Arnaud | 2.5 FTEs | 1 FTE | 1.5 FTEs
 Networking | Santiago | 1 FTE | 1 FTE | 0 FTEs
 Ad-hoc Mercenaries | Pi | 2.5 FTEs | 0 FTEs | 2.5 FTEs
-Project Management, Public Relations & Marketing | Damien | 0.5 FTEs | 0 FTEs | 0.5 FTEs
+Project Management, Public Relations & Marketing | [Damien Czapla](https://github.com/Dam-CZ) | 0.5 FTEs | 0 FTEs | 0.5 FTEs
```


<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
Scope | Owner | Estimated effort | Resources already secured | Resources needed
---   | ---   | ---                | ---                       | ---
Ledger | Matthias | 2.5 FTEs | 1 FTE | 1.5 FTEs
Consensus | Arnaud | 2.5 FTEs | 1 FTE | 1.5 FTEs
Networking | Santiago | 1 FTE | 1 FTE | 0 FTEs
Ad-hoc Mercenaries | Pi | 2.5 FTEs | 0 FTEs | 2.5 FTEs
Project Management, Public Relations & Marketing | [Damien Czapla](https://github.com/Dam-CZ) | 0.5 FTEs | 0 FTEs | 0.5 FTEs
`````

</details>

<!-- suggestion_end -->

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-02T04:18:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -171,4 +171,99 @@ For each of the scopes that are linked with our project but aren't hosted in the
 - Pallas owner: [Santiago Carmuega](https://github.com/scarmuega) see: [Pallas Github](https://github.com/txpipe/pallas) [Pallas proposal](https://gov.tools/budget_discussion/41)
 - UPLC VM owner: [Lucas Rosa](https://github.com/rvcas) see: [UPLC Github](https://github.com/pragma-org/uplc)
 
-This will be updated when we better understand the product and our project environment after each delivery step.
+### Treasury proposal: scope owners and budget administration
+
+The Amaru team submitted a proposal with a list of scopes related to the project and describing a specific way of administrating the budget, this is now reflected into the ways of working of the project.
+
+#### Scopes described in the proposal
+
+![2025_04_13_Amaru_ask](https://github.com/user-attachments/assets/041dacde-5717-4b6f-87a8-1fc279d47e23)
+
+
+> [!TIP]
+> The scopes described here are what the Amaru team expects to deliver in Q3 & Q4 2025
+> For example the Networking is not included as it will already be delivered, but some integration might be required, that's the purpose of the "Ad-Hoc mercenaries"
+
+Scope | Owner | Estimated effort | Resources already secured | Resources needed
+---   | ---   | ---                | ---                       | ---
+Ledger | Matthias | 2.5 FTEs | 1 FTE | 1.5 FTEs
+Consensus | Arnaud | 2.5 FTEs | 1 FTE | 1.5 FTEs
+Networking | Santiago | 1 FTE | 1 FTE | 0 FTEs
+Ad-hoc Mercenaries | Pi | 2.5 FTEs | 0 FTEs | 2.5 FTEs
+Project Management, Public Relations & Marketing | Damien | 0.5 FTEs | 0 FTEs | 0.5 FTEs
+
+#### New scopes from the proposal
+
+##### Ad-Hoc mercernaries
+
+
+**Purpose:** troubleshoot the gaps not planned for and articulate smart problem solving on the project.
+
+Examples of activities:
+- Troubleshoot integration activities
+- Interface
+- Specific use case development, testing and delivery
+
+One of the scopes that will be carried by the Ad-Hoc team will be the Mempool as it requires strong interfacing with the rest of the team.
+This includes:
+- Mempool library: Build a standalone library (data structure that represents transactions in memory) with an interface to get an extract of these transactions
+- "Simple" mempool implementation: Build a basic mempool that adds, remove, gather, drain transactions and exposes a new ledger state
+- "Complex" mempool implementation: Build a more refined version of the mempool that handles features differently and optimises the overall resources consumption
+- Mempool tooling and API: Create a tool able to manage the mempool and the modularity
+- Node management Remote Procedure Call (RPC): Build a software that handles the "operator perspective" on operating the Amaru node
+- Block forging: Develop a component able to forge blocs
+
+Timeline:
+- Mempool library: done
+- "Simple" mempool implementation: Q2 2025
+- Block forging: Q3 2025
+- "Complex" mempool implementation: Q4 2025
+
+#### Project Management, Public relations and Marketing
+
+**Purpose:** drive key initiatives and manage use cases and end users feedback loops. 
+
+The current set of activities forecasted are: 
+- Creating and managing SPO working groups to actively improve the operator side of Amaru 
+- Organizing and facilitating workshops related to key explorations of the product
+- Marketing, implementation partnerships alignment, use case specific collaborations
+- Roadmaps interfaces and scopes alignment synchronization 
+- Bug bounty: create an incentive to generate traffic on the testnet preprod and bring contributors to the project
+> *Testnet developer bounty:* Create on preprod the use cases defined by the Amaru team by building the transactions on the network and generate the conditions needed  
+> *Testnet SPO bounty:* Produce a block that includes the above use case   
+> *Amaru development bounty:* be involved in at least 3 contributions accepted by maintainers   
+
+Our current ambition is to experiment with Amaru as much as we can with testnet activity, conformance tests, simulations and build (with the feedback of early adopters) a reliable setup that fullfills all our global targets.
path: engineering-decision-records/006-design-phase-documentation.md
user: login: coderabbitai[bot]
body: _⚠️ Potential issue_

**Spelling glitch: "fulfills"**  
"fullfills" misses an 'i'—correct it to "fulfills" to avoid a facepalm moment.

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-02T07:31:22Z
author_association: CONTRIBUTOR

PR comments:
user: login: coderabbitai[bot]
created_at: 2025-05-02T03:56:51Z
body: <!-- This is an auto-generated comment: summarize by coderabbit.ai -->
<!-- walkthrough_start -->

## Walkthrough

Alright mate, here’s the lowdown: The Amaru maintainers committee doc got a fresh face with Damien Czapla stepping into the spotlight, bringing a shiny new “Project Management, PR, Marketing” scope to the table. Meanwhile, the design phase doc got a hefty upgrade too — it now lays out the budget admin and scope ownership for the rest of 2025, complete with a new table of scopes, owners, and resources. Plus, there’s a smart contract in the mix to keep the budget tight and tidy, handling everything from withdrawals to failsafes. No wild shakes to the rules, just some solid structure and fresh blood.

## Changes

| File(s)                                              | Change Summary                                                                                     |
|-----------------------------------------------------|--------------------------------------------------------------------------------------------------|
| engineering-decision-records/005-amaru-maintainers-committee.md | Added Damien Czapla to the maintainers committee with a new “Project Management, PR, Marketing” scope and updated references with his GitHub profile. |
| engineering-decision-records/006-design-phase-documentation.md | Added detailed section on treasury proposal, scope owners, budget administration, new scopes like “Ad-Hoc mercenaries” and “Project Management, Public Relations & Marketing,” plus smart contract capabilities for budget control. |

## Poem

> Five at the table, the crew’s grown a bit,  
> Damien’s joined in, with marketing wit.  
> New scope, new avatar, the committee expands,  
> Like a Mario party—more mates, more hands!  
> Budget’s locked down, with contracts so tight,  
> Keeping the treasure safe, day and night.  
> 🎮🍀💰

<!-- walkthrough_end -->
<!-- internal state start -->


<!-- DwQgtGAEAqAWCWBnSTIEMB26CuAXA9mAOYCmGJATmriQCaQDG+Ats2bgFyQAOFk+AIwBWJBrngA3EsgEBPRvlqU0AgfFwA6NPEgQAfACgjoCEYDEZyAAUASpETZWaCrKNwSPbABsvkCiQBHbGlcSHFcLzpIACIAVW5aaijmbQxcVMpELmh/NAcXHgp8bnxENC9oyAB3PPtsAWZ1Gno5MNgPbERKSAARNGYwAGEALXQMelR4JTT4ADN4KNqMRwFugCYABjWULFx2vxISxHV8Fw0Yfdsd3CLabAZpMchsBKSw/DaPFPg0jIoZeRoWi0H5EdCQchVexMbgeTD0fBVcgUc4AZVhDDm8AY5S8sgANChQkDaMg9h5EDCPNErgAySAAWWcAGsSOIMERKlV1LBev0FlhBgAvNDcLxoSBKY5EDBJei1cn8JGUc7uRiwTCkdDwZhkj4McUUObyfyIEoYY5qLzqeSzU5tVDOEgS7l7H6fQr4ERiVX7bjeXz+IIhRiYSCrSASBZVRahWC4XDcLIAemTRB59Q0TGYyd4aCIKTApyIyf6zmwuYDyc2aw0Rn0xnAUDICNmOAIxDIymaClY7C4vH4wlE4ikAIUSioqnUWh0DZMUDgk2QYbQeEIpGRct7bDSXCoUIcTgKrSYk5Uak02l0YEMjdMBjI6fIlFBYCUmOO+AwYH8TAopLJhsGwAKxgGWFDYGA3y/D8mRgNmjQJiQJAaMwtAcAY0TYQYFiQAAggAkp2W49keKQFPgbYMBqHLSG4+z4RR2CQDB6Rwf8O5NChvZHOo8DftUtQvIkPYEDsBrYEo4KQqxJDMKsFCEn0jRkJAwqiuKhKuryCDIAA4uoAAS9ToBI1DOGM9C0bQkS+h4iHcR46QCJEQnICQAAe3DwlEsxFMwkB2tgfDifMUgKF4jgWoSJKgjJJCHlSYTqJE9A0kU3qhCksqkLuuCErYhJMhQrLspy6CINK5D0OJKkCupIpimg5yDKcprmiCHJ4rFEKJZAhm4CZAiQDZbnWhgzJBfa9VqRpzXuegwJROJir+LMlBkA8yBdGIAkYOcAByHz4OSfA0Zqjwxv4rFAs5HyKh+SD7dBaDMvFvD4NtyD2o5yEUjc9y4CFqFGOYlj4V4NBUOI356h6H6GtQ+0/W2XklBQPb2v6rnYpA7D8fRBjHeQdbYdE9YPk+cGvhy76iM936/qIpyAcBABs9PVWA3Aal075fY47DI9+aEYVhOF4URJHdlE5HOPIVHqpdiAMR0rw0AczXbeCxzdQ536SV1YJdGkW1wgI+B4EFeAg88GtXTy4JKOxaV9YeI77SlERRNEOTOvk8ifUc5RcJSxQeIiyIruM4ZSaQxK0I0GBIDcIsHZUS47Z7gk/Dcij3I8ipMeWYTOswADkMjx2ynoh14hLWog5XQhHHneSOK0fBGSjWlI/gTFgACKADMVmQEPAAskA1iBhI/Eb8USi5blK+HsKIISUeZISIQ6tuJCzHamOErtIP0KaVsUNtsWxy+SgX9IV/bechGhEo8zkMgsnr48Dg0ZVGI+FaBgCMl9OS18yDOAWJvSoUoGBGjUByT48A+D+goEcEgsU9pRnEI8AAFBgU6Kg8RyWYCUfAvh4Thi8F9Kax9nxgiUFIWh3B8oAEpb61R1CQCaXx4CRGbt+aQ5x8JELOq3WEhIMpehHIyTA+Z5LsEKvUa0DBIA2F4enZA9ISplVBPiSoqArYRDgvQHSRJkDoMwYSZqGAaroBwYTZA+DURWAAPLVFOO9ZBRAigvE3l40qiBYDFECRRfRHJCQCGwGCS22AZjSE4ePcQbA+H2TjrQBOS1k6pxhl7UUn00AANQOjcUZiuCKjYn8Li/1qgCN8CCP8ER5A5UUR6GJWTa4WIcNwDGoR/IsCeEzC67pEAUVCEwNIVAxCSmkPAGUXd8YYGPg8dsoSjRCiiOjFs6gQaIAyVMtOszen9J2ukcYzh5SxyOaCLa8gdK0APOUQJv8DhTMxNadOhJbl0QwAwE0h8Emkh+QPAm5Q/DENhlgF4gkEmYB1FbZAth8L6QZPhMhil0B9KKOZBu48JSzG0F4MoG13gHGBhQLAsxgXw0VIMK5mAHq5EDigaiYKZgvPQDdWhzdRHAn4t+XEBInjFIeNwC5azPrfWmnwRogiCBf3Hr3SQyhXKPFQB/MxhIgzYFQR9AMBxgzN0CTQZu8USBRmmA8Qkx8UiBktdGcM8gqmpHYsiWpNAsHj0/hCvOJA/Hp2dZIyOyp/gZN2tChQ/yopSnqXsGSp1nIalCI9QW+Ug3ch8OGdWolFhkj9JlORZAoxFAwPlfGEhKFjjrGDKWUNuwo3JY9UQSNoWo3xt5U4WM0GqLxgTPBqsDBQGOsrOi8N0bdqiNjPt6iB0wIrnMg0zhtHVE2rdaS7o3TIBBEfMmOFh23nvM2WOSs1wdk3LLegiF+x+DQIeRwFF5CnkUGqy8s4byGAXLUgA+lMRAP7/BRkSnQH9zdnChAbAYb9DAACcI84MgRICPNYqgQIgUnoh9mGw6ACDWAARjQLMdm8HD4gQ2LMfDAB2OgDBtjzibJAWD5HYOwaJTRtYtAtgkFg5xtYaAqMbU2CPfD7M1gjwABxKAEBsCTaBYNoBINPBjEBIDs0nvhkC7MGBUYk2sdmYmQL4YYLMSewIGASaoyBNA+HeMjxIFRqjDAtMjxAlRyeBnP3QcY7BhgtAR6SYc2sSeVHNMMAEHJ2gDwAsj0EzhqL8GJNiaoxsZzOGvPfqJZPIlawkugQk7MWDIXZgmfw3J/TRWDMCFgxsWgRL8Mj3ZiPEL7MvPedU39P9pJAOOpA7QH9LZP1AA -->

<!-- internal state end -->
<!-- tips_start -->

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

<details>
<summary>❤️ Share</summary>

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai)
- [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai)
- [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai)
- [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

</details>

<details>
<summary>🪧 Tips</summary>

### Chat

There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai?utm_source=oss&utm_medium=github&utm_campaign=pragma-org/amaru&utm_content=202):

- Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  - `I pushed a fix in commit <commit_id>, please review it.`
  - `Generate unit testing code for this file.`
  - `Open a follow-up GitHub issue for this discussion.`
- Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples:
  - `@coderabbitai generate unit testing code for this file.`
  -	`@coderabbitai modularize this function.`
- PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.`
  - `@coderabbitai read src/utils.ts and generate unit testing code.`
  - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.`
  - `@coderabbitai help me debug CodeRabbit configuration file.`

### Support

Need help? Create a ticket on our [support page](https://www.coderabbit.ai/contact-us/support) for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

### CodeRabbit Commands (Invoked using PR comments)

- `@coderabbitai pause` to pause the reviews on a PR.
- `@coderabbitai resume` to resume the paused reviews.
- `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
- `@coderabbitai full review` to do a full review from scratch and review all the files again.
- `@coderabbitai summary` to regenerate the summary of the PR.
- `@coderabbitai generate sequence diagram` to generate a sequence diagram of the changes in this PR.
- `@coderabbitai resolve` resolve all the CodeRabbit review comments.
- `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository.
- `@coderabbitai help` to get help.

### Other keywords and placeholders

- Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed.
- Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description.
- Add `@coderabbitai` anywhere in the PR title to generate the title automatically.

### CodeRabbit Configuration File (`.coderabbit.yaml`)

- You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository.
- Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information.
- If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json`

### Documentation and Community

- Visit our [Documentation](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit.
- Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback.
- Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

</details>

<!-- tips_end -->
author_association: CONTRIBUTOR
user: login: codecov[bot]
created_at: 2025-05-02T04:05:57Z
body: ## [Codecov](https://app.codecov.io/gh/pragma-org/amaru/pull/202?dropdown=coverage&src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pragma-org) Report
All modified and coverable lines are covered by tests :white_check_mark:

[see 1 file with indirect coverage changes](https://app.codecov.io/gh/pragma-org/amaru/pull/202/indirect-changes?src=pr&el=tree-more&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pragma-org)

<details><summary> :rocket: New features to boost your workflow: </summary>

- :snowflake: [Test Analytics](https://docs.codecov.com/docs/test-analytics): Detect flaky tests, report on failures, and find test suite problems.
- :package: [JS Bundle Analysis](https://docs.codecov.com/docs/javascript-bundle-analysis): Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
</details>
author_association: NONE