Budget proposal ontology + deep enrichment of all three Budget 2026 proposals#45
Merged
Budget proposal ontology + deep enrichment of all three Budget 2026 proposals#45
Conversation
Models the structural requirements every Cardano Budget proposal must satisfy under the new BudgetProcess governance vocabulary. Classes: * BudgetProcess (subClassOf TreasuryBudgeting) — the annual cycle * BudgetProposal (subClassOf GovernanceArtifact) — a single proposal * Proposer (subClassOf org:Organization) — the applicant * WorkPackage / WorkPackageMilestone — delivery structure * CostCategory / BudgetLineItem — budget breakdown shape * StrategicPillar / StrategyKPI — Cardano 2030 framework anchors * RepaymentClause — treasury return commitments * ProposalComment — community feedback on the discussion thread Object properties: partOfBudgetProcess, proposedBy, administeredBy, alignsWithPillar, supportsKPI, proposesNewKPI, hasWorkPackage, hasWorkPackageMilestone, hasBudgetLineItem, lineItemCategory, lineItemPerformedBy, hasRepaymentClause, repaysToTreasury, hasComment. Datatype properties: requestedAdaAmount, requestedUsdAmount, adaUsdRate, estimatedDurationMonths, submittedOn, proposalIdentifier, applicantType, proposalNature, initiativeStatus, wpAdaAmount, lineItemAdaAmount, milestoneMonth, kpiCurrentValue, kpiTargetValue, commentBy, commentPostedOn. The next patches add the canonical Cardano Budget 2026 process node, the five strategic pillars, the Cardano 2030 KPIs, the cost categories, and the rich per-proposal instance data.
Adds the shared instance nodes that every budget-2026 proposal TTL
references:
* n:cardano-budget-2026 — the BudgetProcess instance, with
submission/voting window in the description and a 'succeeds'
edge into the existing n:treasury-budgeting node.
* n:pillar-1 .. n:pillar-5 — the five Cardano 2030 strategic
pillars (typed cardano:StrategicPillar).
* n:kpi-tvl, n:kpi-monthly-transactions, n:kpi-mau,
n:kpi-annual-protocol-revenue — the framework KPIs each
proposal claims to support, with current and target values.
* n:cost-category-{labor,development,infrastructure,
security-audits,legal-compliance,engagement-ecosystem} —
the budget breakdown categories used by the application form.
* n:org-intersect — the canonical administrator.
These nodes belong to cardano.ttl (the shared instance layer)
because all three proposal TTLs link to them.
Rewrites each budget-2026/*.ttl using the new BudgetProposal vocabulary:
* BudgetProposal subject typing + datatype properties: requested
ADA / USD, ADA-USD rate, estimated duration, submission timestamp,
proposal identifier, applicant type.
* Process / proposer / administrator edges via partOfBudgetProcess,
proposedBy, administeredBy.
* Strategic-pillar alignment edges (alignsWithPillar).
* Strategy KPI support and proposed-new-KPI edges (supportsKPI,
proposesNewKPI), with per-proposal rationale on reified statements.
* Work-package decomposition with budget breakdown:
- Indigo: 1 WP (RWA Compliance) + 3 line items.
- Serviceplan: 4 WPs (Enable, Kick-off, Scale, V2 Supply Chain)
+ 5 line items including Intersect fee.
- Partner Chain Factory: 8 WPs (Management, Tachys design,
System integration, Bridging, Tooling standards,
Documentation, Demonstrators, Dissemination) plus 9 programme
milestones (MS1-MS9) wired to the WPs that own them, and the
six-partner consortium (ES, WT, PNSol, AFF, HAL8, ETNL).
* Cost-category attribution per line item (lineItemCategory).
* Repayment clauses: Indigo's 10% perpetual revenue share via
V2030RS, Serviceplan's 30% ADA/EUR conversion-buffer surplus
return, PCF's surplus-FX-and-unspent return at project close.
* Comment threads: every recorded community/DRep comment
captured as a ProposalComment with author and timestamp.
Total store after the patches: 4068 triples / 200 gb:Node subjects /
3 BudgetProposals / 13 WorkPackages.
* 'Budget 2026 — Work Packages' — every WP with parent proposal,
milestones, budget line items, cost categories, and the partner
or role each line item is performed by.
* 'Budget 2026 — Strategy & KPIs' — pillar alignment and KPI
coverage (existing framework KPIs + proposal-introduced ones).
* 'Budget 2026 — Treasury Flow' — the budget process node, each
proposal, every repayment clause and the treasury they return to.
Also widens the existing 'Budget 2026 Proposals' view to use the
new vocabulary (proposedBy / administeredBy / partOfBudgetProcess
in addition to the original deliversArtifact / runsIn predicates).
This was referenced Apr 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Extends the Cardano domain ontology with the structural requirements of a Cardano Budget proposal, and rewrites each Budget 2026 proposal TTL to use the new vocabulary at full depth.
Ontology — `cardano.ontology.ttl` (commit 1)
New classes: `BudgetProcess`, `BudgetProposal`, `Proposer`, `WorkPackage`, `WorkPackageMilestone`, `CostCategory`, `BudgetLineItem`, `StrategicPillar`, `StrategyKPI`, `RepaymentClause`, `ProposalComment`.
New object properties: `partOfBudgetProcess`, `proposedBy`, `administeredBy`, `alignsWithPillar`, `supportsKPI`, `proposesNewKPI`, `hasWorkPackage`, `hasWorkPackageMilestone`, `hasBudgetLineItem`, `lineItemCategory`, `lineItemPerformedBy`, `hasRepaymentClause`, `repaysToTreasury`, `hasComment`.
New datatype properties: `requestedAdaAmount`, `requestedUsdAmount`, `adaUsdRate`, `estimatedDurationMonths`, `submittedOn`, `proposalIdentifier`, `applicantType`, `proposalNature`, `initiativeStatus`, `wpAdaAmount`, `lineItemAdaAmount`, `milestoneMonth`, `kpiCurrentValue`, `kpiTargetValue`, `commentBy`, `commentPostedOn`.
Canonical anchors — `cardano.ttl` (commit 2)
Shared instance nodes referenced by every proposal:
Per-proposal enrichment — `budget-2026/*.ttl` (commit 3)
Each proposal carries: requested ADA + USD + rate + duration; pillar alignments; KPI supports + any new KPIs introduced; full work-package decomposition with budgets and cost categories; repayment clause; community comments (author + timestamp).
Queries (commit 4)
Verification
```
total triples: 4068
gb:Node subjects: 200
cardano:BudgetProposal: 3
cardano:WorkPackage: 13
```
Test plan