Cardano Impact DevKit: Attestations & Governance (SDK/CLI)

[Proposal setup] Proposal title

Please provide your proposal title

Cardano Impact DevKit: Attestations & Governance (SDK/CLI)

[Proposal Summary] Budget Information

Enter the amount of funding you are requesting in ADA

100000

[Proposal Summary] Time

Please specify how many months you expect your project to last

9

[Proposal Summary] Translation Information

Please indicate if your proposal has been auto-translated

No

Original Language

en

[Proposal Summary] Problem Statement

What is the problem you want to solve?

On Cardano, teams hand-roll proofs and voting. Lacking a standard toolkit, delivery is slow, inconsistent, and unsafe for consent-sensitive work, hurting adoption, wallet activation and ADA tx growth.

[Proposal Summary] Supporting Documentation

Supporting links

• https://ims.impactweb3.com/
,
• https://github.com/impactweb3/ims
,
• https://youtu.be/TO3bE1m4PZQ?si=pLUT3P3jkv0bDMde

[Proposal Summary] Project Dependencies

Does your project have any dependencies on other organizations, technical or otherwise?

No

Describe any dependencies or write 'No dependencies'

Project Dependencies (managed; no lock-in) People: senior Cardano specialists (adapters/governance/QA) — hire or bounty; wrappers optional Open tooling: wallets (CIP-30/95), tx libs (Lucid/Mesh/js-sdk), indexers (Blockfrost/Koios/Maestro), CI/hosting (GitHub Actions + Vercel/Netlify) — all replaceable; local db-sync for tests Integrations: GovTool/Agora; Summon/Clarity; Identus/Veramo (optional); Midnight adapter (stretch) — SDK independent of these Pilots: case-study evidence, not on the critical path AI: optional, post-grant; no schedule dependency

[Proposal Summary] Project Open Source

Will your project's outputs be fully open source?

Yes

License and Additional Information

Fully open source. Repos public day-1 on GitHub with CI/tests and tagged releases. Licenses: MIT for SDK/CLI/wrappers and example clients; AGPL-3.0 for reference back-end and validators (network copyleft keeps improvements open); schemas/specs under CC BY 4.0. No proprietary components or paywalls. Contributions via PRs welcome; semantic versioning. All licenses are OSI-approved. (Commercial relicense available for AGPL components if enterprises require.)

[Theme Selection] Theme

Please choose the most relevant theme and tag related to the outcomes of your proposal

Developer Tools

[Campaign Category] Category Questions

Mention your open source license and describe your open source license rationale.

• MIT for SDK/CLI/wrappers & example clients (max adoption, easy reuse).
• AGPL-3.0 for the reference back-end and validators so hosted modifications remain open to users.
• CC BY 4.0 for schemas/specs (free commercial use with attribution).
• All are OSI-approved. We’ll also offer commercial licensing for AGPL parts if an enterprise requires it. Mixed licensing gives Cardano builders low friction and protects the commons.

How do you make sure your source code is accessible to the public from project start, and people are informed?

• Public from day-1: a GitHub org with LICENSE/README/CONTRIBUTING/SECURITY.md, CI, and an initial 0.1.0 tag.
• We use semantic versioning; releases and changelogs are tagged, and npm packages publish from CI.
• One Catalyst Forum thread is updated per milestone (monthly only if no milestone) with links to releases, docs, and demos.
• Issues and PRs are open from day-1 to enable transparency and community contributions.

How will you provide high quality documentation?

• Docusaurus docs site with versioned guides
• TypeDoc API refs generated from source
• Runnable examples & quick starts (≤30-min “first attestation”)
• EAS→Cardano migration, governance how-tos, privacy/consent notes
• CI: build, link & code-snippet tests; examples pinned to release tags
• “Edit this page”, CONTRIBUTING, weekly triage; searchable, i18n & a11y-ready
• Changelogs map each release to the corresponding docs updates

[Your Project and Solution] Solution

Please describe your proposed solution and how it addresses the problem

Proposed solution: replace bespoke “proof + vote” code with a standard, safe SDK/CLI + reference apps that teams can drop in within hours - boosting adoption and on-chain activity.

Deliverables:

SDK (TS): attest(), verify(), query(), tally()

CLI: init/attest/verify/vote --strategy simple|qv

Schemas & examples for common receipts (attendance, delivery, task)

Reference apps (testnet):

IMS-lite: capture → attest → dashboard (minimal onboarding, i18n baseline EN + 1)

HRDAO-lite: propose → vote → tally (default simple majority, QV optional)

Pilot support pack:

Pilot Rubric v1 (tasks, acceptance thresholds, feedback template)

Sample dataset (create → measure → evidence → share)

Contributor onboarding: CONTRIBUTING.md, env vars, seed scripts, ≥8 Good-First-Issues

Docs (versioned): 30-min quick start, API refs, EAS→Cardano migration, governance how-tos, privacy/consent notes

Open source day-1: MIT (SDK/CLI), AGPL-3.0 (reference back-end/validators), CC BY 4.0 (schemas/specs). Tagged releases, CI, public issues

How it solves the problem:

Standard blocks, not bespoke code → faster delivery, fewer errors

Safety by design → consent prompts, data minimization, redaction/withdrawal, public-anchor/private-payload; verify() standardizes checks

Adoption outcomes → quicker demos/pilots ⇒ more wallets and ADA txs with auditable receipts and decisions

Technical alignment (Cardano-first):

We implement an IETF-style attestation model—Attester → Verifier → Relying Party - with an evidence envelope (claim + metadata + signer).

Wallet flows use CIP-30; structured on-chain anchors use CIP-68 when useful; compatible with CIP-1694/Voltaire tools.

The SDK/CLI exposes attest(), verify(), query(), and tally(), plus adapters for Lucid, Mesh, and cardano-js-sdk.

Optional VC/DID adapters are provided for partners that need SSI.

Community-led measurement:

Local teams define what matters (multi-language ready)

Patterns to turn narratives into light indicators; avoid one-size-fits-all

Local ownership of dashboards and governance

[Your Project and Solution] Impact

Please define the positive impact your project will have on the wider Cardano community

Impact - value to Cardano, how we’ll measure it, and how we’ll share it

A shared, open DevKit for attestations (“digital receipts”) and lightweight governance removes weeks of duplicate work per team, makes sensitive apps safer, and turns more pilots into real Cardano usage - more wallets, more ADA transactions, stronger case studies.

1. How success brings value to the Cardano community

• Accelerated delivery: SDK/CLI replaces bespoke “proof + vote” code; teams ship demos in hours, not weeks.
• Higher correctness & trust: standard verify() checks (keys/schema/timestamp/anchor) reduce disputes and audit friction.
• Safer real-world deployments: consent prompts, data minimization, redaction/withdrawal, and a public-anchor/private-payload pattern fit human-centric use cases.
• Ecosystem consistency: reusable Attestation Profile & Evidence Envelope, schemas, and examples aligned with CIP-30/95/68 and compatible with CIP-1694 tools (GovTool/Agora, Summon/Clarity).
• Adoption outcomes: reference apps (IMS-lite, HRDAO-lite) + quick starts create repeatable paths that generate on-chain activity and credible success stories for NGOs, educators, and Catalyst teams.
• Open public good: all outputs are open from day-1 (MIT/AGPL/CC BY) so any project can reuse, extend, or integrate.

1. How we will measure impact (quantitative + qualitative)

Adoption & usage:

• ≥150 wallets activated** through workshops/pilots; ≥100 first ADA transactions from demo flows (TX links recorded).
• ≥3 external integrations by Month 8 (PRs or public case notes).
• npm: weekly installs trend upward from Month 4; packages semver-tagged.

Developer experience & learning:

• 2 recorded tutorials + 1 workshop + 1 live Q&A.
• ≥120 participants, ≥20% average pre/post knowledge gain.
• ≥60% of participants complete the 30-min quick start.
• Docs rated ≥80% “useful.”

Code quality & correctness:

• Time-to-first verification ≤60s via CLI sample.
• Verification success ≥95% on sample vectors.
• Schema conformance ≥95% in test suite.

Community & contributor health:

• Pilot Rubric: ≥10 testers complete rubric tasks with ≥80% pass rate.
• ≥6 new-contributor PRs merged from Good-First-Issues by Month 7.
• Public issues, discussions, and roadmap board active from day-1.

Evidence of impact produced:

• Public demo URLs and testnet TX IDs for IMS-lite and HRDAO-lite.
• Two case studies (short write-ups with screenshots and links) summarizing goals, steps, results, and lessons.

1. How and with whom we’ll share outputs:

• Primary source of truth: public GitHub org from day-1 (LICENSE/README/CONTRIBUTING/SECURITY.md, CI, tags, changelogs, roadmap).
• Docs site: versioned guides, API refs, runnable examples, and the 30-min quick start; “Edit this page” enabled for community PRs.
• Catalyst Forum: one project thread updated per milestone (monthly only if no milestone), linking to releases, docs, demos, case studies, and TX IDs.
• NPM releases: SDK/CLI packages published from CI with changelogs.
• Live touchpoints: 1 workshop + 1 Q&A (recorded and posted), plus partner meetups on request.
• Close-out: public report + 3–5 min video summarizing KPIs, integrations, lessons, and how others can adopt.

Who receives it:

• Cardano developers and Catalyst teams
• Governance-tool maintainers (GovTool/Agora, Summon/Clarity)
• NGOs/social enterprises and educators in our pilot network (SEA, Africa, EU, JP/US)
• Wider Web3 builders via the EAS→Cardano guide.

Bottom line: Success means Cardano has a standard, open, production-ready way to create/verify evidence and run simple decisions - lowering cost and risk, increasing real-world adoption, and leaving durable public goods (code, docs, examples) the community can build on.

[Your Project and Solution] Capabilities & Feasibility

What is your capability to deliver your project with high levels of trust and accountability? How do you intend to validate if your approach is feasible?

Capabilities & Feasibility

Why us?

We’re building upon what we already built with IMS v1 and our developing pilot HRDAO: attestations (“digital receipts”) and simple governance.

Scope is lean (SDK/CLI + two testnet reference apps + docs), fully open-source from day-1, and deliverable in ≤9 months.

Track record & standards alignment:

IMS v1 (Catalyst-funded): MVP live; close-out in progress. Lessons inform SDK/CLI design and docs.

Cardano-first rails: CIP-30 (wallet bridge), CIP-68 (structured on-chain data), compatibility with CIP-1694/Voltaire tools.

Interoperability mindset: EAS→Cardano migration notes; optional VC/DID adapters.

Team & roles (core + targeted specialists):

• Razali Samsudin — Lead / Partnerships & Ethics: partner onboarding, community-led metrics, consent/privacy guardrails, adoption KPIs.
• Cole Bartlett — Product & Ops (+ AI-assisted dev): roadmap, delivery/QA, tutorials/docs; contributes SDK/CLI modules and examples.
• Teodor “Teo” Petricevic — Impact Methods: pilot rubric, indicator schemas, usability testing & synthesis.
• Gareth Farry — Governance & Legal: DAO patterns, risk, licenses/consent notes.
• Contracted Cardano engineers (2–3): Lucid/Mesh/cardano-js-sdk adapters, governance wrappers, CI/QA.
• Advisors:
  • Dr. Mihaela Ulieru — AI ethics/complex systems.
  • Miguel Ávila — SEA go-to-market.
  • Damián Hryb — UTxO/Smart-contract architecture. Cardano since 2021 (CardanoTrees, Cardano Forest with Veritree); specializes in UTxO design patterns; SC dev on Cardano & Midnight.
  • Jimmy Londo — standards & marketplaces. Building web3 music solutions since 2021; authored the first draft of a music metadata (cip60) standard proposal discussed in the CIP process; Artist Relations and NFT development for NEWM; founder of Sick City; NFT/metadata expertise.
• Responsible: Cole (SDK/CLI), contracted engineers (adapters/QA).
• Accountable: Raz (delivery, budget, partners).
• Consulted: Teo (rubric/metrics), Gareth (governance/legal), advisors (Damian/Jimmy/Mihaela/Miguel).
• Informed: pilot partners & community (Forum/GitHub).

Delivery process (trust & transparency):

Public from day-1: GitHub org with LICENSE, README, CONTRIBUTING, SECURITY.md, CODEOWNERS.

Single source of truth: GitHub releases/changelogs + versioned docs; npm packages from CI.

Progress comms: one Catalyst Forum thread updated per milestone (monthly only if no milestone), linking to releases, docs, demos, and TX IDs.

Milestone acceptance (feasibility gates):

• M1 (Foundations): local setup ≤20 min; unit-test coverage ≥60%; Pilot Rubric v1, Sample Dataset, ≥8 Good-First-Issues live.
• M2 (SDK/CLI v1 + adapters): npm packages released; CI green; “first attestation ≤30 min” tutorial reproducible end-to-end.
• M3 (Ref apps + lean education): IMS-lite & HRDAO-lite on Cardano testnet with minimal onboarding + i18n baseline (EN + 1); 2 recorded tutorials + 1 workshop + 1 Q&A; docs rated ≥80% “useful.”
• M4 (Integrations & close-out): ≥3 external integrations (PRs/case notes); close-out report + 3–5 min video; KPI sheet published.

Engineering quality & security:

• Test-first modules: unit tests + sample vectors for attest(), verify(), tally().
• CI pipeline: build, lint, unit tests, docs link/snippet tests; examples pinned to release tags.
• Verification discipline: verify() enforces signature/keys, schema, timestamp, Cardano anchor checks.
• Dependency hygiene: lockfiles; minimal runtime deps; adapters isolated; reproducible builds.Secrets & keys: .env templates; never commit secrets; guidance for safe testnet use.
• Licensing clarity: MIT (SDK/CLI), AGPL-3.0 (reference back-end/validators), CC BY 4.0 (schemas/specs); SPDX headers & NOTICE files.

How we validate feasibility (evidence we’ll produce):

• Pilot Rubric results: ≥10 testers complete rubric tasks; ≥80% pass rate; structured feedback.
• Learning & DX: ≥120 participants, ≥20% average pre/post knowledge gain; ≥60% complete 30-min quick start; docs ≥80% “useful.”
• Correctness & quality: time-to-first verification ≤60s; verification success ≥95%; schema conformance ≥95% on sample suites.
• Adoption signals: ≥3 external integrations by Month 8; npm installs trending up; ≥6 new-contributor PRs merged from GFIs.

On-chain evidence: demo URLs and testnet TX IDs for IMS-lite & HRDAO-lite.

Responsible use of AI (to speed, not to replace humans):

Pair-programming only: use AI for scaffolding/tests/docs; human review for every merge.

License hygiene: origin checks; no partner confidentials pasted into tools.

Quality gate: CI must pass; AI outputs treated like junior-dev PRs (tests + review).

Risk management & mitigations

Tooling/API drift (wallets/adapters): modular adapters; semantic versioning; upgrade notes; wallet test matrix (CIP-30).

Governance contention (e.g., QV): default simple majority; QV optional with clearly documented trade-offs; reputation/badge overlays; human-curated oracles for sensitive claims.

Capacity constraints: scoped specialist contracts + public bounties; if hiring slips, wrappers defer—SDK/CLI still ships.

Pilot timing: reference apps/docs ship independently; case studies can publish later.

Privacy/safety: consent prompts, minimal data, redaction/withdrawal; public anchor / private payload default; optional Midnight adapter when available.

AI dependency: AI features are post-grant; no milestone depends on them.

Budget governance & controls

Milestone-based drawdowns: internal payments only after acceptance evidence is public (repos, npm, demos, docs).

Why the plan is realistic (≤9 months):

Narrow, technical scope: no AI modules, staking/SBTs, or cross-chain mainnets inside F14 (those remain post-grant).

Leverages existing libs: integrate Lucid/Mesh/cardano-js-sdk instead of inventing a new tx stack.

Battle-tested patterns: design is distilled from IMS/HRDAO experience; we are packaging proven building blocks.

Bottom line: With a lean core team, named expert advisors (Damián Hryb on UTxO/SC patterns; Jimmy Londo on NFT/metadata standards), open repos from day-1, and rigorous milestone gates, we can deliver a high-quality Cardano DevKit on time and in the open—validated by tests, pilot results, external integrations, and transparent reporting.

[Milestones] Project Milestones

Milestone Title

Public foundations (repos, schemas, rubric, onboarding)

Milestone Outputs

Public GitHub org/repos with LICENSE/README/CONTRIBUTING/SECURITY.md/CODEOWNERS

Base attestation schemas + reference scripts

Attestation Profile & Evidence Envelope v1

Pilot Rubric v1 + Sample dataset

Contributor onboarding (env vars, seed scripts, ≥8 Good-First-Issues)

CI pipeline + unit tests (initial coverage)

Acceptance Criteria

Acceptance Critera:

• Public repo links with required files visible
• CI green; unit-test coverage ≥60% (badge/screenshot)
• Links to Rubric v1, Sample dataset, GFIs
• Forum update linking to all artifacts

Evidence of Completion

Evidence of Completion:

• Repo/CI links
• coverage badge/screenshot
• rubric/dataset/issue links
• Forum post URL.

Delivery Month

2

Cost

25000

Progress

30 %

Milestone Title

SDK/CLI v1 + adapters (Lucid/Mesh/cardano-js-sdk)

Milestone Outputs

TypeScript SDK: attest(), verify(), query(), tally()

CLI: init/attest/verify/vote --strategy simple|qv

Adapters for Lucid, Mesh, cardano-js-sdk

EAS→Cardano migration notes & sample vectors

30-min Quick Start tutorial

npm packages (semver) + tags/changelogs; CI green

Acceptance Criteria

npm package pages (SDK + CLI) with matching GitHub releases/tags

Quick-start tutorial URL + short demo clip showing end-to-end usage

CI matrix green on supported Node versions

Forum post linking to npm, releases, tutorial, demo

Evidence of Completion

Evidence of completion:

• npm links
• release/tag links
• tutorial URL
• demo clip
• CI screenshot
• Forum post URL

Delivery Month

4

Cost

30000

Progress

60 %

Milestone Title

Reference apps (testnet) + education

Milestone Outputs

IMS-lite (capture → attest → dashboard) with minimal onboarding

HRDAO-lite (propose → vote → tally), default simple majority; QV optional

i18n baseline (EN + 1 language)

Versioned docs site (guides, API refs, consent/privacy notes)

2 recorded tutorials, 1 live workshop + 1 live Q&A (recorded)

Acceptance Criteria

Public demo URLs + testnet TX IDs for IMS-lite and HRDAO-lite

Docs site URL (versioned) live

Links to tutorial videos + workshop/Q&A recordings

Forum post linking to demos, TX IDs, docs, and recordings

Evidence of Completion

Evidence of completion:

• Demo/transaction (TX) links
• documentation URL
• video links
• Forum post URL

Delivery Month

9

Cost

30000

Progress

90 %

Milestone Title

Integrations & project close-out (Final)

Milestone Outputs

≥3 external integrations (merged PRs or public case notes with code refs)

v1.1 polish (bug fixes, docs update) + maintenance plan

Close-out report (PDF) + 3–5 min video summarizing KPIs & lessons

Acceptance Criteria

Links to ≥3 integration PRs (or public case notes if partner PRs can’t merge)

GitHub v1.1 release tag + changelog; docs updated (version bump visible)

Published close-out report PDF + video

Final Forum post aggregating all links

Evidence of Completion

Evidence of completion:

• PR/case-note links
• v1.1 release link
• docs link
• report PDF
• video link
• final Forum URL

Delivery Month

9

Cost

15000

Progress

100 %

[Final Pitch] Budget & Costs

Please provide a cost breakdown of the proposed work and resources

Budget & Costs — for public reviewers and voters

Total request: ₳100,000

Purpose: deliver an open-source SDK/CLI, adapters, two testnet reference apps, and versioned docs that make attestations & simple governance easy on Cardano.

Razali Samsudin — project lead, partnerships, ethics/privacy, reporting.

Cole Bartlett — product & delivery, SDK/CLI implementation, CI/releases, docs/tutorials.

Teodor Petricevic — pilot rubric, indicator schemas, usability testing.

Gareth Farry — governance/legal notes (licensing/consent).

Targeted contractors (as needed): Cardano adapter engineers, QA/Security reviewer, tech writer/i18n.

Rationale: keep core in-house; hire narrowly for adapters/polish/QA.

Cost breakdown (value for money):

Engineering (SDK/CLI, adapters, ref apps, QA/CI): ₳65,000

Docs & developer activation (docs site, quick starts, 2 recorded tutorials, 1 workshop + 1 live Q&A, EN+1 i18n): ₳18,000

Interoperability/governance fit checks + lightweight security review: ₳12,000

CI/infra & small services (hosting, indexer overages, domain, video editing, bookkeeping): ₳5,000

Allocations:

Razali Samsudin: ₳14,000

Cole Bartlett: ₳16,000

Engineering contractors: ₳52,000 total (lead engineer ₳22k; full-stack ₳10k; governance/adapter ₳8k; adapter specialist ₳8k; security/QA reviewer ₳4k)

Docs/i18n & small services: ₳18,000 (tech writer ₳4k; i18n/design/video ₳2k; bounties ₳7k; infra/services ₳5k)

Milestone tranches:

M1 (Nov–Dec 2025, 2 mo): ₳25,000 (25%)

Public repos, base schemas, Evidence Envelope v1, Pilot Rubric, onboarding, CI/tests.

Evidence: repo links, CI green, coverage badge ≥60%, rubric/sample dataset, Forum post.

M2 (Jan–Feb 2026, 2 mo): ₳30,000 (30%)

SDK/CLI v1, adapters (Lucid/Mesh/cardano-js-sdk), npm releases, 30-min quick start.

Evidence: npm + release tags, tutorial URL + short demo clip, CI green, Forum post.

M3 (Mar–May 2026, 3 mo): ₳30,000 (30%)

IMS-lite & HRDAO-lite (testnet), versioned docs site, 2 tutorials + 1 workshop + 1 Q&A, EN+1.

Evidence: demo URLs + testnet TX IDs, docs URL, video links, Forum post.

M4 Final (Jul 2026, 1 mo): ₳15,000 (15%)

≥3 external integrations, v1.1 polish, close-out report + 3–5 min video.

Evidence: PR/case-note links, v1.1 tag + changelog, report PDF, video, final Forum post.

Third-party services (kept minimal)

Hosting/CD (Vercel/Netlify), GitHub Actions minutes.

Indexers/APIs for tests (Blockfrost/Koios/Maestro) — free tiers first; budget covers modest overages.

Domain, light video editing, bookkeeping.

Targeted security/QA review of verify() and schema tests (not a formal audit).

Governance & payout:

Milestone-based payouts only after public evidence.

Budget owner: Razali Samsudin; delivery verification: Cole Bartlett.

One Catalyst Forum thread updated per milestone; simple ledger of invoices summarized at close-out.

[Final Pitch] Value for Money

How does the cost of the project represent value for the Cardano ecosystem?

We would deliver a reusable, open-source DevKit—SDK/CLI + schemas + two testnet reference apps - that standardizes attestations (“digital receipts”) and simple governance on Cardano.

Why this matters for Cardano?

Removes repeated work: Teams now hand-roll proof & voting, causing delays, bugs, and inconsistent UX. The DevKit makes these drop-in and verifiable.

Faster pilots → more activity: Easier proofs and votes mean quicker demos, more wallets, first ADA txs, and auditable outcomes.

Public good with compounding effect: One toolkit used by many projects multiplies impact across funds and verticals (grants, education, credentials, DAOs, RWAs).

“Doesn’t this already exist?” — quick rebuttals

“We have Lucid/Mesh/CIP-68—done.”

Those are excellent transaction/tooling primitives. What’s missing is a cohesive attestation & governance layer: attest() / verify() / tally(), evidence envelopes, ready-made schemas, CLI flows, and versioned docs—plus reference apps that show end-to-end patterns.

“Just use EAS.”

Ethereum Attestation Service is chain-specific. We provide a Cardano-first implementation aligned with CIP-30/68/1694, wallet flows, and UTxO patterns—plus migration notes for teams coming from EAS.

“Not significant.”

Any Cardano app that says prove X happened or collect a fair vote benefits—dozens of teams each fund. Standardization improves safety, speed, and credibility across the ecosystem.

Why ₳100k is good value

Conservative ROI: If 20 teams each avoid 4 weeks of engineering at ~$75/hr, the community saves ~$240k—already >2× the grant—before counting user growth or TXs.

In-house first, targeted contracting:

Cole Bartlett implements SDK/CLI, CI/releases, docs/tutorials.

Razali Samsudin leads delivery, ethics/privacy, reporting.

Teodor Petricevic (pilot rubric), Gareth Farry (governance/legal).

Contractors only for wallet/indexer adapters, QA/security review, and i18n/tech writing.

Open from day-1: MIT/AGPL/CC-BY, tagged releases, searchable docs—no paywalls, easy to fork and extend.

Evidence you can verify (each payout):

M1 (25%) repos, base schemas, Evidence Envelope v1, Pilot Rubric, CI/tests.

M2 (30%) SDK/CLI v1, adapters, npm packages, 30-min quick start.

M3 (30%) IMS-lite & HRDAO-lite on testnet, versioned docs, 2 tutorials + 1 workshop + 1 Q&A, EN+1.

M4 (15%) ≥3 integrations, v1.1 polish, close-out report + 3–5 min video.

All linked publicly: repos/tags, npm pages, demo URLs with testnet TX IDs, docs, and recordings.

Bigger picture:

Strengthens Voltaire era: clean, auditable patterns for decisions & receipts.

Lower risk, higher trust: consistent verify() checks and consent guidelines.

Scaffolding for the future: once the rails exist, AI, credentials, and cross-chain adapters plug in faster and safer.

Build the rails, not bespoke tracks. For ₳100k, Cardano gains a durable toolkit many teams can ship on - saving time, raising quality, and translating directly into adoption and on-chain proof.

[Required Acknowledgements] Consent & Confirmation

Terms and Conditions:

Yes