Resource type
Resource types are abstract entities, representations of actual resources or categories of resources. If two things that are used in a process are interchangeable, they belong to the same resource type.
NRP-CAS and NDO, part of OVNi, implement resources as resource types, based on the REA ontology, further developed as Valueflows language. For example, a real Microscope is represented in the NRP-CAS by a Resource Type, which can have elements like "inverted microscope", "stereomicroscope", "USB microscope" etc., all physical things in a physical lab space.
How to think about Resources and Resource Types from the VDML perspective - Ampie's doc
Resource Type vs Resources
Information systems that handle resources to assist in economic activities use a clear differentiation between ResourceSpecification and EconomicResource
ResourceSpecification example:
pub struct ResourceSpecification {
pub name: String,
pub description: String,
pub category: String,
pub image_url: Option<String>,
pub tags: Vec<String>,
pub is_active: bool,
}
This is the knowledge layer in ValueFlows terminology: the type or template of a resource. It corresponds to the OVN concept of "Resource Type", an abstract representation that groups interchangeable concrete instances.
EconomicResource example:
pub struct EconomicResource {
pub quantity: f64,
pub unit: String,
pub custodian: AgentPubKey,
pub current_location: Option<String>,
pub state: ResourceState,
}
This is the observation layer: a specific instance of a resource at a point in time, held by a specific custodian.
Resource governance
Governance Rules are linked to ResourceSpecification rather than EconomicResource as rules belong to the type, not the instance.
GovernanceRule example:
pub struct GovernanceRule {
pub rule_type: String, // free-form string (e.g., "access_requirement")
pub rule_data: String, // JSON-encoded, completely untyped
pub enforced_by: Option<String>,
}
Economic rules governing access and use. Can be entirely untyped, rule_data is a free-form JSON string with no schema enforcement.
With respect to blockchain, resources are represented as RWA (real world assets) and resources types can be used in ricardian contracts, which become the basis of the onchain governance of resource. This reduces the transaction cost for accessing / using / consuming resources shared across a network. See more on the economic model.
NDO treats Governance as an operator on Resources, changing the state of Resources, based on the type of Economic Event, according to rules of validation.
See also Physical resource governance.
Properties and characteristics
From a value chain perspective, lifecycle
Resources can be specific to a certain stage of development or maturity. Responds to the question "How far is this from the final usable state?"
- Ideation - Conceptual, idea, informally described but not yet physical, needs to be documented and contextualized
- Specification - More formal, a requirements and specification doc, a formal design, ex. CAD file for 3D modeling, SPICE file for electronics, ...,
- Development → Prototype - Being developed/iterated (in R&D, not yet stable), a tangible thing that is somewhat fulfilling an intended function.
- Stable → Distributed → Active - as a usable artifact, deployed, in circulation, being used by the community, a tangible thing that represents a solution to a problem, in traditional terms, a product.
- Hibernating → Deprecated → EndOfLife or Retired - removed from circulation
Ideas and designs are immaterial but tangible, see below. Prototypes and usable artifacts can be material artifacts, goods.
Complexity economics note: A resource's governance complexity should match its value-chain maturity. An Ideation-stage resource (someone's declared intent) requires near-zero governance. A Stable design that is being distributed for fabrication requires full governance, integrity verification, and versioning. The NDO's pay-as-you-grow layer activation model directly implements this, it is why the three-layer model (identity -> specification -> process) is correct.
From a production process perspective
Some resources are specific to production. They would respond to the question "What do you need in order to do that?"
From Sensorica's experience with NRP-CAS we can think of:
- Human labor (time spent doing something, work)
- Usables and consumables (can be material like a hummer and screws, or immaterial like a computer program)
- Space (can be physical, like a lab, an office space, or virtual, like a website)
- Method (a protocol, a recipe, a sequence of steps)
- Current-see (symbolic system that organizes flows)
- Monetary Currency (tokens of value used by people in value exchange processes, can be $, bitcoins, time-based credits,...)
These resources have features, which make them more or less suitable for a particular process.
In NDO, the most significant gaps here are Method (documented processes, recipes, protocols) and Space (physical locations with governance, scheduling, and access control needs). Both are important in commons-based peer production settings.
- Method resources are particularly interesting in the NDO context: a fabrication method (how to assemble a CNC machine) is a non-rivalrous digital resource, it can be copied freely. But it is also a governance-bearing resource: it defines the conditions under which physical resources should be used, encoding safety requirements, quality standards, and attribution requirements. In NDO terms, a Method would be a Digital NDO whose Layer 1 (specification) includes both the documented process and governance rules referencing it.
- Space resources are rivalrous (only a few agents can use it at the same time) and require scheduling/booking mechanics. A future generic NDO should be able to express temporal availability as a dimension of resource governance.
Complexity economics note: Resource nature and method resources matter because the governance architecture for a documented protocol is fundamentally different from the governance architecture for a physical tool. A method (recipe, process, protocol) is non-rivalrous, can be forked and adapted, should be versioned and attributed, and its quality affects every physical process it governs. Modelling methods as first-class resources enables the network to track method provenance, quality, and evolution, and to connect method quality to the physical resource outcomes produced using those methods.
Accessibility
Accessibility is related to ''property regime'' and rights. See more on the Physical resource governance page.
Main categories of accessibility
- Free - Public, anyone can use/consume
- Protected or regulated - Requires some credentials based on skills, role, reputation, payment, ... Can also be regulated based on priority, scarcity, ...
- Formally restricted - Requires formal procedures for approval.
See Sensorica/Ouishare Blockchain-based access management to physical resources project. Rights and the RAE model.
Availability
- Abundant. Example: ideas. Have very low marginal costs, once it is produced, it can be reproduced at low cost.
- Scarce. Example: a microscope. Have high marginal costs.
This distinction is important for the design of the contribution accounting system, which defines incentive/rewards mechanisms.
They can also be
- Rivalrous - access to use is limited by other use, access can be restricted
- Non-rivalrous - multiple agents can have use access to the same resource at the same time.
Rivalry determines optimal governance strategy more directly than any other property. Non-rivalrous resources should default to open access (information wants to be free); rivalrous resources require access scheduling, usage tracking, and maintenance governance.
Complexity economics note:
- Benkler's entire argument for commons-based peer production rests on the distinction between rivalrous and non-rivalrous resources. A P2P governance system that does not formally model this distinction will produce governance rules that are either too restrictive for non-rival resources (inefficient) or too permissive for rival resources (destructive).
- Rivalry matters because it determines the fundamental economic logic. Non-rivalrous resources exhibit positive sum dynamics, sharing them creates more value, never less. Rivalrous resources exhibit zero-sum dynamics in the short term, access by one agent genuinely prevents access by another. Conflating these in a governance system produces either over-restriction (damaging information flows) or under-restriction (depleting physical commons). No other classification has more direct governance consequences.
Transferability
When the notion of private property is involved, i.e. transfer of property ownership
- Transferable. Example - currency, consumables
- Non-transferable. Example - social capital, space (to a certain extent)
When the notion of private property is irrelevant, i.e. commons or shareables
- Shareable. Example - all commons or items from a pool of shareables, i.e. document under Creative Commons license, not belonging to anyone, but openly shared; this also applies to material resources
Some things are not transferable and /or not tradeable (can't be sold or exchanged against something else). Farmer - Kidtrade paper emphasizes the difference between tradeable and non tradeable goods. For example, someone's reputation score based on good service, good deeds what have you cannot be passed to someone else. Allowing this would in fact destroy the reputation system, as its meaning would be called into question.
There is is an opportunity for tools like NRP-CAS to chase after and define metrics or metacurrencies for valuables that are not transferable or tradeable.
Complexity economics note: Transferability determines what kind of market or exchange system applies to a resource. Non-transferable resources require non-market coordination mechanisms (gifting, contribution tracking, reputation systems).
Quantifiability
Intangible resources cannot be measured. Noubel goes so far as to say there are some things that aren't even measurable, like love, but they can in fact be acknowledged.
For example, reputation is arguably not tradeable but is it measurable? We can approach quantification using proxies. In the case of reputation, which can be seen as an individual asset, attempts are Klout.
Convertibility
Some resources are readily converted into others. Some conversion paths are not possible.
Scope
Related to the domain a resource can affect. Responds to the question "Who benefits?"
- Project or Venture specific: some resources are intended for a specific venture and benefit mostly those involved in that particular venture. Examples: a chemical solution that can only be used to produce a specific thing.
- Network specific: some resources are intended for a wider domain, for a group of ventures or for an entire network constituted around a broader mission like Sensorica. Examples: a website used by the entire network, like [www.sensorica.co Sensorica's website], or a microscope that can be used for many ventures by affiliates of a network.
- Public: some resources can benefit the entire world. This is the case of commons: designs, documented methods, etc.
Complexity economics note: Scope matters because it determines information propagation. Benkler's analysis of networked information environments shows that scope determines who needs to know about a resource for it to produce value. A method that benefits the entire world should propagate globally; a specialised tool scoped to one project should not create noise in the global discovery layer. Scope-driven discovery anchors reduce the information overhead of the global DHT.
Property regime
Resources are treated in society under a given property regime, which confers rights and responsibilities over resources, which in turn leads to governance.
- Private property of affiliates or partners of the network. Can also be shared private property such as condominium. Examples: an academic lab used by affiliates of the collaborative venture for some projects, some equipment or physical space.
- Pool of shareables. In general, these are material resources such as a lab, a CNC machine, a 3D printer, but can also be immaterial, like a website or a forum.
- Commons. In general, these are immaterial resources such as designs, pictures, documented methods, …
- Nondominium. Assets that cannot be owned by anyone in particular.
This distinction is very important from a resource stewardship and governance standpoint. Resources that are part of the commons are in the public domain and are accessible by everyone on this planet. There is no governance around them. Some licenses governing use might be formulated.
The use of material resources that are part of the pool of shareables and that have high maintenance costs needs to be regulated. Other material resources, like equipment, require some level of training. Some form of governance needs to be put in place. Moreover, a resource management system needs to be put in place to monitor their ware and tare, as well as their whereabouts, allocation, etc.
Resources owned by affiliates or partners of the network are governed by rules imposed by the owner. The community might also impose some generic rules on them.
Operational State
This answers: what is happening to this resource right now?
The current process acting on the resource instance, associated with resources in_use, in_processes.
Example:
- Available / Active — no active process, can be requested
- Reserved — committed to a future process (a Commitment exists, no Event yet)
- InTransit — a transport process is active
- InStorage — a storage service commitment is active
- InMaintenance — a repair/maintenance process is active
- InUse — actively being used (a Use event is open)
- PendingValidation — awaiting peer validation
A change in operational states are triggered and cleared by the governance, when processes begin and end. For example, a rule can be invoked to shift the state of a Resource from Active to InTransit, when a transport Commitment is accepted; clears it back to Available when the corresponding Claim is created.
In strict ValueFlows, operational state is derived from the open event stream (a Move action without a matching Accept implies the resource is in transit). The NDO's governance-as-operator pattern takes the alternative approach: explicit state transitions under governance control. Both are valid. The explicit approach makes queries simple (WHERE operational_state = InTransit) and in NDO it makes the governance zome the clear single authority for state changes.
Source
Provenance of resources. Responds to the question "Where does it come from?"
- OVN - Usually part of the pool of shareables, commons or nondominium)
- Partners - Might be shared with limitations
- Purchased - Acquired through an exchange process
We can also talk about the flow of resources into processes within the network: inward (from the OVN) or outward (from partners or purchased).
Resource flows
About flows of resources as in: transactions, distribution, etc.
See also Valueflows project, which describes the flows of valuables within organizations. including networks. Note that the name Valueflows is a misnomer in our opinion, as value is not a substance that can flow or even be stored.
Behavior of resources
We can classify resources by their behavior is use.
- Material (ex. a microscope, a lab space)
- In economic processes they get created, consumed, used, destroyed, transferred (exchanged, shared). They have design, creation, distribution and storage costs, have a higher cost of reproduction. Some material resources are part of the pool of shareables, others are the property of affiliates and partners.
- From a resource management perspective they can get depleted, worn, replaced, replenished, maintained/repaired, stored, transported, shared. They also must have a physical location associated with them and/or if they are integrated into more complex material resources, to point to the item they are pat of...
- From a governance perspective access to them may be restricted (need training, certification, to be a member, to justify the use,...)
- Immaterial (an idea, a design, a website)
- In economic processes they can get created, cited, forked, mixed, transferred. They are not consumed during their use, have lower storage costs, can be copied indefinitely at very small costs. Some immaterial assets are non-transferable (ex. consultancy services) and the cost of reproduction scales with volume.
- From a resource management perspective they can get maintained, stored, shared. They also must have a virtual location associated with them (or a physical if we talk about a printed document, or a CD or flash stick) and/or if they are integrated into more complex immaterial resources, to point to the item they are pat of...
- From a governance perspective access to them may be restricted (sensitive information)
Sensorica puts immaterial resources under commons
- Tangible (doesn't necessarily mean material. Examples: a lab space, a piece of equipment, a document, a design, a website...)
- Intangible
- brand (for the network and for its deliverables, produced artifacts)
- social capital (someone can use social capital to open a new market, to drive a crowdfunding campaign, etc.)
- group dynamics (someone can deliver an increase in activity for a venture, by animating, coordinating and energizing a group around a venture)
- members and customers loyalty (focus attention, inform, service, personalize attention and approaches, ...)
- synergy (linking ventures within the value system)
- internal structure and relationships (weaving networks of agents)
- incentive systems (identifying incentives, building incentive systems, communicating incentives, embedding purpose in ventures)
- competencies (improving individual skills, increasing group competency, build know how)
- cultural values (help establish and maintain a culture)
- business practices (establish sustainable business practices)
- social responsibility (inject social responsibility into value network goals and activities)
- data, information and knowledge system (improve the capture, storage, analysis, contextualization, translation into actionables, exchange... of data, information and knowledge)
- governance (help with decision making, improve decision making mechanisms)
- sense of community (animate, inject purpose, help, nurture a sense of community)
- trust (by members in the value network, in all the risk metrics used, in evaluation processes, in sustainability, in the ethical fabric of the OVN, by users with respect with usable artifacts, services, future improvements, continuity, compatibility)
Complexity economics note: Intangibles matter negatively, as a design constraint: governance systems that ignore social capital, trust, and community sense will inadvertently destroy them through surveillance, commodification, or capture. The NDO's design choices (peer validation rather than central authority, private PPRs rather than public scoring, permissionless access rather than gatekeeping) are intangible-preserving choices. They should be recognised as such, so that future design decisions are evaluated against the same standard.
Reliability
Material resources, mostly usables, should have a parameter if reliability, which is related to the risk associated with their use. In other words, is that piece of equipment going to brake during the fabrication process? Is that sensor going to present acuate data? Is that tool available with high probability?
Reliability is a fact like Reputation for agents and can be taken into consideration by systems of prioritization, choice of a resource to be included into a process. Reliability should also reflect desirability, and perhaps cost of use. Cost of use can be justified for highly reliable resources, because they require maintenance.
Complexity economics note: Reliability matters because it is information. In a P2P system with no central quality control, agents making decisions about which resources to access, which tools to borrow, which methods to follow, need reliable information about the track record of those resources. A resource with a high failure rate imposes hidden costs on the network, missed deadlines, wasted materials, unsafe working conditions. Making reliability visible and queryable converts hidden costs into explicit governance inputs. In information theory, reliability is a measure of signal-to-noise ratio. A governance system that cannot distinguish reliable from unreliable resources is processing high-noise information, i.e. it cannot direct maintenance effort, access restrictions, or replacement decisions to where they are most needed.
Related to use of physical resources
- Consumables (glue, paper, screws) - Need to be replenished -
- Usables (tools, equipment, space). Get worn in use, need maintenance or repairs. Space is treated a bit differently
They have costs associated with their creation, maintenance, storage, sharing or distribution, consumption, governance, etc.
They present a liability. Safety and security concerns, requires risk management (access restrictions by credentials, protocols of use), might require insurance. See more on Physical resource governance.
NOTE: include this parameter field in the NRP-CAS, related to potential to induce harm, which is important from a resource management point of view and related to the governance of certain resources. See Github issue.
Acquisition and distribution of funds
As a resource, funds are tangible, scarce and depletable. They are also seen as a vital resource, and in the traditional economy and whoever controls the funds controls the organisation. In a collaborative environment funds should be shared and administered according to clear and transparent rules, which should be adopted in advance in order to eliminate future conflicts. It is very important to maintain a good balance of power or influence, by putting in place provisions to avoid accumulation of power through accumulation of vital resources.
Two propositions have been recorded in Sensorica.
- No central budget: redistribute funds as soon as they are acquired to all active affiliates and stakeholders, based on a value equation, in proportion to their respective fluid equity. Let these active affiliates use it as they see fit.
- Budget with a forward-looking contribution accounting system: the funds are held by a trust (a custodian) and are redistributed based on a development plan, using budgeting and cost management tools. The role of the trust can be automated using blockchain-based smart contracts and escrow wallets for example.
add others if you are aware of...
Fundraising is an important activity that needs be incentivised. If there are no incentives to drive a fundraising campaign everyone will wait for others to do it. This behavior has been observed in Sensorica. Tibi proposed to form fundraising groups and fundraising ventures with the goal to deliver funds to the community (through classical funding initiatives or crowdfunding). The deliverable of this team is the fund, which would go to a custodian and distribute it according to one of the methods described above. A % of the fund will automatically be subtracted and given to the fundraising group. That is their recompense, and at the same time, this is what justifies the transfer process, from the fundraising group to the custodian who will administer it for the community.
NOTE that funds raised for OVN ventures or for infrastructure development or maintenance must belong to the community, because the brand of the OVN and the OVN's capacity and potential, all part of the commons, are used to get the funds. The fundraising process is regulated by the rules about the use of the brand, which is part of the commons. If someone raises funds only using his own assets, capacity and potential, with no reference to the OVN, the funds only belong to him/her.
Physical space
Physical spaces are part of the physical infrastructure.
Physical spaces can have various functions: storage, working, transit, etc. They possess features that make them more or less suitable for a particular process: size, location/proximity, accessibility, security, ventilation, layout or plan, etc. They can come under various property regimes: private (including shared ownership), shared, condominium.
Building a new space is an important activity that needs be incentivised. If there are no incentives to drive it almost everyone will wait for others to do it. This behavior has been observed in Sensorica. Tibi proposed to create a venture and form a group around this activity, with the goal to deliver the space to the community. The deliverable of this team is the space, which would go to a custodian to be administered according to a charter adopted by active affiliates. During the process, those involved in the building a space activity, which is an infrastructure development type of activity, will log their contributions. These contributions can be in time (meetings, documentation, giving presentations, visiting, etc.) in cash (paying for rent, repairs, etc.), in materials (sharing renovation tools with the group for repairs and maintenance, etc.). The promise is that once the space will generate ventures that in turn generate revenue, the initial investment will be rewarded. There are different ways to reward this initial investment. Tibi proposed one guiding principle: those who invest in infrastructure development cannot hope to get a % from all commercially successful ventures using this infrastructure, for as long as they exist, because this kind of investment has a great multiplication factor that makes is unjust compared to contributions to ventures (for example, writing a document that helps infrastructure development or writing a document that helps an R&D project, in the second case the contribution generates fluid equity for one venture, in the first, for all ventures).
One way to reward infrastructure development contributions is to calculate the market equivalent price (ex. if spent one hour doing something, how much the labor market would reward for the same hour of the same activity?) and whenever the new space becomes sustainable to be repaid back the equivalent plus x%, which represents the risk incurred. The x% is fixed based on supply and demand: it is slowly raised until enough resources become available to build the space.
If fundraising is done for building a space, see the section on fundraising above.
Some examples
Material
- components (laser diode, screws, ...)
- prototypes (a sensor prototype)
- usable artifact (a ready to use material good, in traditional term, a ready to use product)
- tools (screwdriver, ... )
- equipment (microscope, computer, ...)
- consumables (glue, chemical solutions, printing ink and paper, ... )
- space (physical: a lab, an office space; virtual: website, forum, shared folder/drive)
Immaterial
- designs (CAD files or 3D models, SPICE files, ZMAX files, drawings and sketches)
- methods (optical fiber coating, copper etching, marketing schemes, etc.)
- publications (posts, articles, videos, ...)
Resource types and the NRP-CAS
In the NRP-CAS resources are grouped into Resource types. See Sensorica's Resource Types list.
Some Resource types have recipes associated with them. Recipes are essentially a group of processes that lead to the creation of a family of resources (a resource type). Recipes are used in planning and provide context to work.
The NRP-CAS gives the possibility to group Resource types into Resource type lists. Only resource types with recipes can be included in Resource type lists. Lists are used in planning. They essentially allow us to group together different recipes.
Resources and Blockchain
Representing material assets in the virtual space, in a way that is usable by open / permissionless networks.
- Use ricardian contracts -> see Matterium
- Sensorica knows how to steward material assets as an open network
- DAOs know how to perform secure onchain operations
A sea of material resources accessible by free agents in dynamic processes. Material assets need to be:
- Permissionless Access: Anyone can Access Resources under defined governance rules
- Organization Agnostic: Exist independently of any single organization. Not owned or controlled by any single Agent or organization.
- Capture Resistant or Unenclosable: Uncapturable and resilient to monopolization. No Agent or group of Agents can control or delete Resources.
- Self-governed: Rules driven associated directly with the Resources, which govern interactions or Actions that Agents can take, as defined by the system.
- Roles: Set of Activities or types of interactions that an Agent can perform with respect to the Resource. Also related to Custody (responsibility), maintenance or improvements (obligations).
- Access control: Rules associated with Roles of Agents, membranes, to grant permissions to interact with Resources in specific ways, Role-related. Is pseudonymous.
- Self-regulated: Peer reviewed, verified and tested (quality control)
- Shareable by Default: Resources are designed for sharing from inception
- Credentials and Reputation-enabled: Built-in accountability through cryptographically-signed participation tracking
- Process-aware: Supporting structured Economic Processes (Use, Transport, Storage, Repair)
- Fully specified: Machine readable in terms of function, design architecture, standards (dimensions, tolerances, quality), etc.
- Composable: Resources can be combined into come complex resources, allow fork and remix
- Hard to Clone: Governance, set of rules and incentives to make unnecessary copying of a resource unlikely.
- Lifecycle Managed: Resources have managed lifecycles from creation through validation to end-of-life.
- Traceable: Full provenance and economic activity tracking, affiliation to component resources.
Future additions: accommodate various property regimes, including nondominium (no one owns but everyone has access under certain rules), which is an implementation of the pools of shareables concept.