[RFP-02/RFP-05] <ELK> — Milestone 1

[benjiELK]

Milestone 1 report for the Verticals as a Driver for Cardano 2030 KPIs project.

Deliverables:

• Review and synthesize all existing Cardano 2030 KPI definitions
• Audit existing vertical reporting approaches across Cardano ecosystem teams
• Benchmark methodologies from adjacent ecosystems (Polkadot, Ethereum ecosystem funds, Cosmos) to identify best practices
• Draft the initial Impact Vertical Chain template and scenario modeling structure

Evidence:
https://drive.google.com/file/d/1BSbz7ODMhDEs8KNNB9apDxTH7Sw0kAuZ/view?usp=sharing
https://drive.google.com/file/d/1wkzwKNMNxImWzPbV5n8OoQxKEVjuN5-9/view?usp=sharing
ttps://drive.google.com/file/d/1274-OaUiaMxl0H8obeBI-uElNbXPrR1a/view?usp=sharing

[l-br1]

Please submit the deliverable also as mark down content here in github

[disassembler]

Please embed the evidence in the markdown. We don't want to reference 3rd party google drive links as evidence.

[disassembler]

Review — Milestone 1, Framework Foundation

Decision: Request changes.

---

Baseline requirement

All deliverables and evidence must be present in this PR as Markdown. External links to Google Drive or any other external resource cannot be treated as evidence. If it is not in this PR as Markdown, it does not exist for the purposes of milestone review.

---

Issue 1 — Broken file formatting (blocker)

The submitted file has malformed frontmatter. The YAML delimiters (---) are missing from the top of the file — the --- appears only at the end, after the key-value pairs, which are themselves broken across multiple lines. The file will not parse correctly in Docusaurus and the page will not render as intended. The frontmatter must be corrected to the standard format:

---
title: "ELK — Milestone 1"
sidebar_label: "Milestone 1"
---

The file is also placed in elk-consortium/Milestone-1/milestone-1.md, creating an unnecessary subdirectory. It should be elk-consortium/milestone-1.md to match the structure of other milestone submissions.

---

Issue 2 — All evidence is external (blocker)

All four deliverables link to Google Drive files. None of the actual content is present in this PR as Markdown. The KPI synthesis, ecosystem audit, ecosystem benchmarking, and initial vertical chain template must each be written up as Markdown files and committed to this PR.

---

Issue 3 — One deliverable is self-reported as incomplete (blocker)

Deliverable 5 — "Publish a public call for ecosystem input on Intersect forums" — is marked as Incomplete. The acceptance criteria require inception documents to be complete. A milestone with an incomplete deliverable cannot be approved. Either complete this deliverable before resubmitting, or make the case for why it should be deferred and how that affects the acceptance criteria.

---

Issue 4 — Submitted deliverables do not match the contract (blocker)

The contracted Milestone 1 deliverables are:

• Framework foundation report
• Agreed methodology
• Data-source and stakeholder map
• Confirmed decision-gate structure

The submission instead lists tasks (KPI synthesis, ecosystem audit, ecosystem benchmarking, impact vertical chain template draft, forum post). None of the contracted deliverable names appear. The framework foundation report, data-source and stakeholder map, and confirmed decision-gate structure are not referenced. The submission needs to map its work to the contracted deliverable list — either by producing the named deliverables or by explaining explicitly how the submitted work constitutes each one.

---

Issue 5 — Deliverables 1 and 2 link to the same file

D1 (KPI synthesis) and D2 (ecosystem audit) both point to the same Google Drive link (1BSbz7ODMhDEs8KNNB9apDxTH7Sw0kAuZ). Either these are the same document, or D2 has the wrong link. This needs to be corrected.

[blockjock2017]

The public call for ecosystem input appears in the proposal as a Phase 1 research/engagement activity rather than a named contractual deliverable. Its deferral into the framework-validation stage appears reasonable, provided the required community validation is completed within the agreed project schedule.

[blockjock2017]

Reviewed against the KPI synthesis on pages 4–7 of P1-1+2_KPI_Synthesis_Audit.pdf. The work clearly consolidates the Cardano 2030 North Star and supporting KPIs into a common reference and appears to satisfy this deliverable. I would like future updates to continue attaching a clear source/date to any “current status” figures so the baseline does not become stale.

[blockjock2017]

Can ELK provide the stakeholder/interview evidence matrix supporting the ecosystem audit, including stakeholder category, organization where disclosable, interview date, core findings, and how conflicting views were reconciled? Ref pages 7-10

Nit picking here but where it states There are no central dashboards, named owners or established sources for several proposed metrics, instead can you state that you have not identified a reliable source. Also when it comes to dashboards there is Dune analytics https://dune.com/defi__josh/cardano-ecosystem-overview along with bending.ai that could use some obvious upgrades and we pay for dune out of treasury funding completed by the Pentad. Josh would be more then helpful creating what we currently don't really have in my view Ref page 9

[blockjock2017]

Referencing pages 4–5 of P1-3_Ecosystem_Benchmark.pdf: The Cosmos comparison is useful, but I would tighten the Cosmos Labs description. It emerged from ICF’s acquisition of Skip as a more accountable engineering, product and growth organization, with a mandate extending beyond the Hub to the broader Cosmos Stack. Since then it has shipped IBC v2/Eureka, Cosmos SDK v0.53 and Cosmos EVM, while pushing further into institutional adoption. The one issue is they have not embraced governance (currently were in grandma hug mode with governance;-) in any real way which makes it easier for them to pivot quickly.

For me one of the most important outputs of this research should be Cardano’s own answer to the Cosmos coordination problem. Cosmos can rely on a centralized execution organization; Cardano cannot without undermining its governance model. I would like Milestone 2 to define how decentralized authorization can coexist with accountable, empowered execution who holds the mandate, what authority is delegated, what remains with governance, and what measurable gates allow funding to continue, change or stop.

[blockjock2017]

this is for r63,64 and 65 Referencing page 5 of P1-4_Impact_Vertical_Template_Scenario_Modeling.pdf: the framework already begins defining a credible Vertical Lead as someone with industry knowledge, Cardano technical understanding, and commercial/institutional relationships. Since this line identifies eligibility as unresolved, I would like Milestone 2 to convert those principles into explicit selection criteria, including whether the role can be held by an individual or team and how accountability is assigned. I know you have stated here but I am just reaffirming your on the right path.

[blockjock2017]

This will be one of the more impactful areas, especially where thre may be conflicting opinions on the topic, typical bias can creep in and compromise anyone currently employed here. There needs to be a designation between those currently employed or previously employed in Cardano in some capacity and those who have never been a salaried employee.

[blockjock2017]

The stress-testing should test more than whether the framework can be completed. I would like to see whether different reviewers using the same evidence reach materially similar outputs, particularly around adoption assumptions, KPI attribution and scenario ranges.

[blockjock2017]

I would use this validation to distinguish between problems the ecosystem can realistically solve through coordination or investment and external constraints that a Vertical Lead cannot control. That distinction will matter when deciding where treasury resources can actually produce measurable impact.

[blockjock2017]

This seems like the right point for broader community input because there is now a tangible framework to challenge. I would like the final report to show what materially changed as a result of that feedback rather than only recording that the workshop occurred.

[blockjock2017]

The final framework should be operational enough that a future Product Committee, DRep or Vertical Lead can use it without ELK having to explain how it works. Clear ownership, decision gates, KPI attribution and reporting expectations should all be explicit.

[blockjock2017]

No issue with the target date, but the key test for completion should be whether the unresolved ownership and governance questions identified in Milestone 1 have been converted into usable rules, not simply discussed further.

[blockjock2017]

The draft is strong. I would keep the requirement that every claimed KPI result clearly shows how a real company or commercial user creates a specific on-chain activity that can then be measured against the Cardano 2030 goals. That clear connection is what makes the framework useful for deciding what should be funded.

[blockjock2017]

The scenario model is useful, but the assumptions need to be very clear. Things like onboarding, conversion rates, retention, transaction activity and TVL can quickly change the projected results. I would make sure each major assumption has a clear source or explanation so the committee can see what is driving the numbers.

[blockjock2017]

I would make sure this part clearly separates problems Cardano can realistically fix from problems that are outside the ecosystem’s control. That will help the committee understand whether more funding or coordination can actually improve the outcome, or whether the market simply is not ready yet.

[blockjock2017]

This is a very cool idea the scorecard could be very useful for Product Committee oversight. I would make sure it clearly separates projected results from actual verified results so we can easily see whether the business activity being funded is really producing the on-chain outcomes that were expected.

[blockjock2017]

I would like the final report to clearly explain how verticals should actually be managed within Cardano’s governance structure. Who gets the mandate, what authority they have, who they report to, what stays with governance, and what happens if results are not being delivered. Solving this clearly could be one of the most valuable outcomes of the research.

[blockjock2017]

Final thoughts here:

I think the proposal is heading in the right direction because it is trying to solve a problem Cardano clearly has: we have a lot of activity, funding and people working across the ecosystem, but not always a clear way to show how that work turns into real business growth and measurable progress toward the 2030 goals. The strongest part of this work is the attempt to connect real companies and users to actual on-chain activity and then measure whether that activity is worth funding. That gives the Product Committee and DReps something more useful than broad claims about adoption.

One additional point I would add is governance. Cardano’s decentralized governance model is clearly a constraint when compared with ecosystems like Cosmos that can create a more centralized execution layer and move faster. I do think this proposal and its team can find common ground when it comes to the handcuffs governance seems to apply those who want a prosperous community experiencing true commerce here. The key is to remove as much individual bias as possible and create a framework that helps us make common-sense decisions based on results, not on whether someone can get paid one more time to produce one more research paper. Our treasury is not unlimited and, at the current pace, five years can go by very quickly. It is up to us, and work like this, to make sure we are funding things that actually move Cardano forward and not slowly driving the chain toward a financial cliff.

If ELK can turn this into something the Product Committee and DReps can actually use to decide what should be funded, what is producing real results, and where resources are being wasted, then this could become a very valuable piece of work for the ecosystem.