Frontmatter test
hsp: 107
title: <max 44 characters>
description: <max 140 characters>
author: <name(s) and contact info>
discussions-to: https://hos-fe-staging-4may-updates-staging.up.railway.app/proposals/107
status: Review
track: <Sensing|Decision>
type: <Simple Majority|Supermajority>
category: <category name>
stakeholders: <see section "Stakeholders">
created: 2026-05-07
requires: <HSP number(s)> (optional)
Abstract
Synthesize what is proposed, why it matters, and the expected outcome. Max 120 words.
Payload
When a proposal contains executable code or text intended for formal adoption, include the payload using the format below.
<details>
<summary> Payload title </summary>
Proposal's code or text
</details>
Context
Describe the background that makes this proposal relevant. Explain what prior proposals or decisions relate to this, what discussions or working group outputs informed it, and what recent events or conditions make this timely.
Problem
State the problem this proposal addresses and why it matters.
Approach
Describe the high-level solution and how it addresses the stated problem. Compare how the proposal solves the problem in relation to other potential approaches, and explain the benefits and limitations of the proposed alternative. Avoid implementation details, timelines, or metrics.
End-to-end Value Hypothesis
The proposal shall demonstrate how it, on a standalone basis, delivers complete and meaningful value to the NEAR House of Stake and the NEAR ecosystem, without omission of essential components, deferral to follow-up proposals, or reliance on undefined or uncommitted third-party deliverables. All implementation steps necessary to realize the proposed value shall be specified within the proposal, and any external dependencies shall be explicitly identified, confirmed, and evidenced in the Dependencies subsection. This section defines the logic of value creation inherent to the proposal and does not address success measurement, evaluation metrics, or execution sequencing.
Objective
The proposal shall clearly state the specific change or improvement it intends to achieve. Shall not restate expected benefits, outcomes, or performance measurements, which are addressed in other sections.
Outcome
The proposal shall describe the observable benefits or changes experienced by affected stakeholders once the stated objectives are achieved, focusing on the resulting impact rather than implementation, process, or measurement.
Dependencies
List and detail all external components, infrastructure, systems, or conditions required for the Objective and Outcome to be achieved that are not part of the payload. For each dependency, provide evidence of existence. Do not include implementation steps; they belong in the Implementation Plan. Do not list people or organizations; they belong in the Stakeholders.
Key Performance Indicators (KPIs)
KPIs define what success looks like. They specify the methods for collecting qualitative or quantitative data and for evaluating impact, taking into account the nature and scope of the proposal.
Technical Specification
Clearly describe the technical side of the proposal for reviewers to assess feasibility and correctness, including code, policies, documentation, or any other digital component of the proposed execution.
Backwards Compatibility
State whether this proposal conflicts with existing governance rules, technical systems, or processes. If conflicts exist, explain how the proposal aims to resolve them, and if no conflicts exist, briefly explain how the proposal is compatible with the current state of operations.
Security Considerations
Identify relevant technical, governance, economic, or operational risks, and include mitigation alternatives for each. If no security considerations apply, state “No security considerations identified.”
Stakeholders
List all parties required for the proposal to succeed, including external service providers and Governance Body Members. Clearly specify who is Responsible, Accountable, Consulted, and Informed for each activity or decision, ensuring that every activity has exactly one Accountable party.
| Activity / Decision | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|
| Activity 1 |
Implementation Plan
Outline a clear Definition of Done that includes all necessary implementation steps to achieve the proposed positive impact, including completion criteria and the ways and pace that progress will be reported. This section describes how work is done, not how success is measured (KPIs) or why it creates value (End-to-end Value Hypothesis).
Milestones
Break the proposal into trackable checkpoints that specify when and how critical development steps are achieved. Each milestone must produce a tangible output and, where applicable, reference the KPIs used to evaluate success.
| Milestone name | Target date | Deliverable | Success criteria |
|---|---|---|---|
| Milestone 1 | YYYY-MM-DD |
Budget & Resources
Details and funding sources, with specific use of requested resources and funding (if applicable), including milestone completion-based fund distribution, subject to compliance. If no funding or resources are requested, state “Not applicable.”
Conflict of Interest
The author(s) must state that they’ve read and agree with the House of Stake Conflict of Interest policy, and must state any conflicts of interest, if relevant.
Copyright
Copyright and related rights waived via CC0 1.0.