Skip to content

[RFP-07] NexTrium Global Innovations Ltd — Milestone 1 - #61

Open
Basrahtop wants to merge 2 commits into
IntersectMBO:masterfrom
Nextrium:milestone-1-deliverables
Open

[RFP-07] NexTrium Global Innovations Ltd — Milestone 1#61
Basrahtop wants to merge 2 commits into
IntersectMBO:masterfrom
Nextrium:milestone-1-deliverables

Conversation

@Basrahtop

Copy link
Copy Markdown

NexTrium (RFP-07)

This document outlines the first milestone for Nextrium Global Innovations Ltd, detailing deliverables, evidence, budget updates, and plans for the next milestone.

… NexTrium (RFP-07)

This document outlines the first milestone for Nextrium Global Innovations Ltd, detailing deliverables, evidence, budget updates, and plans for the next milestone.

| # | Deliverable | Status | Link / Evidence |
|---|-------------|--------|-----------------|
| 1 | Research design document | Complete | [CPC260015_M1_ResearchDesignDocument_v1.1_01Aug2026.docx](https://docs.google.com/document/d/1KK_1H6Usti4D1LJQiLmtQj9eWdkRjlzs/edit?usp=sharing) |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

all milestones and deliverables should be included in the PR itself, no external links.

@disassembler disassembler left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review — Milestone 1, Inception & Research Design

Decision: Request changes.


Baseline requirement

All deliverables and evidence must be present in this PR as Markdown. External links to Google Docs, Google Drive, GitHub repositories, 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 — All evidence is external (blocker)

Every deliverable in this submission links to an external Google Docs document. None of the actual content — the research design, the desk research, the screening report, the stakeholder access update, or the independent technical review — is present in this PR as Markdown. The Cardano Forum post is similarly external.

All five contracted deliverables and all supporting outputs must be written up as Markdown files and committed to this PR.


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

The contracted Milestone 1 deliverables are:

  • Inception report
  • Research design and methodology
  • Confirmed research questions
  • Primary-research plan

The submission instead lists:

  1. Research design document
  2. Preliminary VAL-case evidence set
  3. Desk research summary
  4. Screening report
  5. Stakeholder access status update

There is no inception report. The desk research summary, screening report, and stakeholder access status update look like Milestone 2 deliverables (contracted as: desk research report; regulatory landscape scan; market and stakeholder map). Submitting M2 work under M1, while not delivering the contracted M1 inception report, is not equivalent to meeting the Milestone 1 deliverable list.

Action required: Map the submission to the four contracted M1 deliverables. If the research design document serves as the inception report and primary-research plan combined, say so explicitly. Remove or reclassify M2-level outputs.


Issue 3 — VAL-case evidence appears unrelated to this project (blocker)

Deliverable 2 is a "Preliminary VAL-case evidence set" referencing Zivana Labs, PRISM DIDs (did:prism:3f4aa98c...), Celo MiniPay, Identus, and a Cardano preprod transaction. NexTrium's contracted scope is an L2 adoption and interoperability demand study for Nigeria and Ghana. These validation cases do not appear to relate to that scope.

Either explain clearly how this VAL-case material relates to the contracted research scope for RFP-07, or remove it from this submission.


What is genuinely positive

The submission shows ambition — producing a screening report, desk research, and stakeholder access assessment in parallel with the research design goes beyond what M1 requires. The forum post is a good transparency signal. The on-chain artefact approach for the independent review is creative. The problem is that none of this work is visible in the PR.

@Basrahtop

Copy link
Copy Markdown
Author

Review — Milestone 1, Inception & Research Design

Decision: Request changes.

Baseline requirement

All deliverables and evidence must be present in this PR as Markdown. External links to Google Docs, Google Drive, GitHub repositories, 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 — All evidence is external (blocker)

Every deliverable in this submission links to an external Google Docs document. None of the actual content — the research design, the desk research, the screening report, the stakeholder access update, or the independent technical review — is present in this PR as Markdown. The Cardano Forum post is similarly external.

All five contracted deliverables and all supporting outputs must be written up as Markdown files and committed to this PR.

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

The contracted Milestone 1 deliverables are:

  • Inception report
  • Research design and methodology
  • Confirmed research questions
  • Primary-research plan

The submission instead lists:

  1. Research design document
  2. Preliminary VAL-case evidence set
  3. Desk research summary
  4. Screening report
  5. Stakeholder access status update

There is no inception report. The desk research summary, screening report, and stakeholder access status update look like Milestone 2 deliverables (contracted as: desk research report; regulatory landscape scan; market and stakeholder map). Submitting M2 work under M1, while not delivering the contracted M1 inception report, is not equivalent to meeting the Milestone 1 deliverable list.

Action required: Map the submission to the four contracted M1 deliverables. If the research design document serves as the inception report and primary-research plan combined, say so explicitly. Remove or reclassify M2-level outputs.

Issue 3 — VAL-case evidence appears unrelated to this project (blocker)

Deliverable 2 is a "Preliminary VAL-case evidence set" referencing Zivana Labs, PRISM DIDs (did:prism:3f4aa98c...), Celo MiniPay, Identus, and a Cardano preprod transaction. NexTrium's contracted scope is an L2 adoption and interoperability demand study for Nigeria and Ghana. These validation cases do not appear to relate to that scope.

Either explain clearly how this VAL-case material relates to the contracted research scope for RFP-07, or remove it from this submission.

What is genuinely positive

The submission shows ambition — producing a screening report, desk research, and stakeholder access assessment in parallel with the research design goes beyond what M1 requires. The forum post is a good transparency signal. The on-chain artefact approach for the independent review is creative. The problem is that none of this work is visible in the PR.

Thanks for the review. Accepting one point, disputing two; details below.

Issue 1 (all evidence external), accepted. Fair. Will commit all five deliverables plus the two supporting outputs as Markdown in this PR, replacing the Google Docs links.

Issue 2 (deliverables don't match contract), disputed. The four-item list cited ("inception report," "confirmed research questions," "primary-research plan," etc.) doesn't match our signed contract. It matches RFP 05, the title mistakenly attached at award announcement and in the first contract draft, flagged by us before signing and corrected by the CPC Secretary. Our actual, signed proposal and agreement are for RFP 07: "L2 Adoption and Interoperability Demand in African Emerging Markets: A Builder-Embedded Research Study." Appendix A of that signed agreement lists the M1 deliverables verbatim as: research design document, preliminary VAL-case evidence set, desk research summary, screening report, stakeholder access status update, the exact five submitted. Same issue on the M2 comparison: Appendix A's M2 deliverables are the blocked-demand case register and early demand-signal review, not "desk research report / regulatory landscape scan/market and stakeholder map." Can you confirm you're reviewing against the RFP 07 agreement and not the earlier RFP 05 version? That mismatch also shows up in the resend email guiding this submission, which still points to the RFP 05 language.

Issue 3 (VAL-case evidence unrelated to scope) disputed. The VAL-case evidence set is itself a named M1 deliverable in Appendix A, and its independent review is a named M1 acceptance criterion ("the VAL evidence baseline is documented and independently reviewed"). The approved proposal sets out VAL-001 to VAL-006 as the internal evidence baseline, each tied to a specific decision gate and cross-referenced against interview findings (e.g. VAL-003/Identus feeds the identity workstream, VAL-006/Celo MiniPay feeds the access-channel workstream). It's applicant-supplied conflicted evidence by design, stated as such in the proposal, not standalone or off-scope material.

@Basrahtop
Basrahtop force-pushed the milestone-1-deliverables branch from 44c9802 to 6023587 Compare September 9, 2026 17:20

@disassembler disassembler left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated Review — Milestone 1, Foundation & Screening

Apologies for the confusion in the previous review. The milestone schedule published on the website at the time of the earlier review was incorrect — the wrong milestones had been entered for NexTrium. This has now been corrected and the published website reflects your actual contracted milestones. As a result, Issues 2 and 3 from the previous review are withdrawn.

Issue 2 (deliverables don't match the contract) — withdrawn. Your submitted deliverables — research design document, preliminary VAL-case evidence set, desk research summary, screening report, and stakeholder access status update — match the contracted Milestone 1 deliverables exactly.

Issue 3 (VAL cases appear unrelated) — withdrawn. The VAL-001 to VAL-006 evidence baseline and independent technical review are explicitly part of your contracted Milestone 1 scope.


Remaining issue — All evidence is external (blocker)

The one issue that stands is that every deliverable links to an external Google Docs document. None of the content is present in this PR as Markdown. All five contracted deliverables must be written up as Markdown files and committed to this PR. External links to Google Docs, 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.

Please convert each of the five deliverables to Markdown and add them to this PR, then request a re-review.

Adds the seven Milestone 1 deliverable and supporting documents as
Markdown under docs/product-research/nextrium/rfp-07-deliverables/,
converted verbatim from the submitted source documents. Updates the
Milestone 1 report to link to these in-repo files instead of the
external Google Docs links, per review feedback that PR content
itself should be the evidence.

Also restates the Stakeholder Access Status Update's outreach status
table (Section 3.2) to match exactly what was presented to the
Cardano Product Committee at Milestone 1 submission, and reverts the
respondent category targets in Sections 1.1, 1.2, 1.3, 4.1 and 7 to
the ranges committed in Proposal Section 5, replacing the later
internal recruitment-ceiling figures.
@Basrahtop
Basrahtop force-pushed the milestone-1-deliverables branch from 44c9802 to 2a759a1 Compare September 9, 2026 17:43
@disassembler

Copy link
Copy Markdown
Collaborator

(Editing the review above to add:) Once the deliverables are in the PR as Markdown, we will review the substance of each one.

@Basrahtop

Copy link
Copy Markdown
Author

@disassembler

Update: Milestone 1 deliverables now committed as Markdown

All five Milestone 1 deliverables, plus the two supporting outputs (independent technical review and interview instruments), are now committed as Markdown in this repo under docs/product-research/nextrium/rfp-07-deliverables/, replacing the earlier Google Docs links. The milestone report now links to these in-repo files directly.

Ready for another look whenever convenient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants