Budget 2026: IO slate + Critical Integrations + SKOS classification#49
Merged
Budget 2026: IO slate + Critical Integrations + SKOS classification#49
Conversation
Pulls in the per-source named-graph loader, optional graphSources labels, and the Sources sidebar panel with per-source visibility toggle (upstream issues #70 and #74).
The new graph-browser Composed graphs UI surfaces each graphSource as a toggleable entry in the Sources panel; without a label it falls back to the raw path. Adds a label per source so the panel reads as a domain table of contents.
Adds cardano:BudgetProposalScheme with two independent axes: - Workstream (8): Consensus, L2 Scalability, Smart Contracts, DeFi, Tooling, Maintenance, Infrastructure, Ecosystem - Status (4): Submitted, Voting, Approved, Rejected Proposals declare membership via dcterms:subject. The two axes are independent — a proposal can sit on multiple workstreams and exactly one status. Risk axis is intentionally excluded; it is a judgment that will live with technical assessments when those land.
…+ status Each proposal carries dcterms:subject triples for SKOS classification: - Partner Chain Factory: Workstream-L2 + Workstream-Infrastructure (it ships an L2 partner-chain factory and a production-grade bridge) - Indigo V2030RS: Workstream-DeFi (iUSDt stablecoin, Bitcoin DeFi markets, shielded iAssets) - Serviceplan Demand Engine: Workstream-Ecosystem (enterprise marketing pilot — demand generation, no protocol work) All three are currently Status-Voting (DRep window open, deadline 2026-05-24).
…Budget
Adds stub BudgetProposal nodes for the rest of the 2026 cycle, each
tagged with its workstream and current Status-Voting:
IO 9 (proposer: Input | Output Global)
- bp-io-developer-experience Tooling
- bp-io-cardano-upgrades SmartContracts
- bp-io-consensus-leios Consensus
- bp-io-l2-scalability L2
- bp-io-high-assurance SmartContracts
- bp-io-maintenance Maintenance (62.1M ADA)
- bp-io-plutus SmartContracts
- bp-io-pogun DeFi
- bp-io-blockfrost Infrastructure
Coalition
- bp-critical-integrations Infrastructure + Ecosystem
(70M ADA; IOG + EMURGO + CF +
Intersect + Midnight Foundation)
Shared proposer / co-lead organisation nodes co-located in
budget-2026/proposers.ttl so individual proposal files stay focused on
their own facts.
Each new TTL is registered as its own labelled graphSource in
data/config.json — one toggle per proposal in the new Sources sidebar
(Decision A from the design discussion: per-proposal source granularity).
Stub-grade: lead names, descriptions, and workstream classification are
captured; ADA amounts and milestone breakdowns are intentionally left
out where IO has not yet published per-proposal numbers. Will be
enriched as proposals progress.
This was referenced Apr 29, 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.
Closes #48.
Scope
Five-commit stack rolling out the Budget 2026 cycle in the graph and putting every proposal under a SKOS classification.
labelto everygraphSourcesentry indata/config.jsonso the new Sources sidebar reads as a domain table of contents instead of raw paths.cardano:BudgetProposalSchemeSKOS concept scheme to the ontology with two independent axes: Workstream (8 concepts) and Status (4 concepts). Risk axis intentionally excluded — it is a judgment, not a description, and will live with technical assessments when those land.dcterms:subjecttriples for workstream + status.budget-2026/proposers.ttl.Result
13 proposals now visible in the graph, each as its own
graphSourcetoggle. SPARQL summary verified locally:All proposals are currently
Status-Voting(DRep window open, deadline 2026-05-24).Design decisions encoded
The implementation reflects the design discussion captured in the issue:
Out of scope (follow-up issues)
Proposals by Workstream,Proposals in Voting)Stale PR
PR #32 is fully obsolete — its description still talks about migrating away from
graph.ttl, which has long since been split. Will close it after this lands.Validation
Sources