Difference between revisions of "Accountability"
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[Accountable]] and [[accountability]] should be grounded on information [[symmetry]] or some form of traceability of causal relations. It can be also considered as a way to perform [[abstract counting]]. | [[Accountable]] and [[accountability]] should be grounded on information [[symmetry]] or some form of traceability of causal relations. It can be also considered as a way to perform [[abstract counting]]. In [[PKC]], the accountability is assigned to three account types: | ||
# [[Externally Owned Account]] | |||
# [[Contract Account]] | |||
# [[Project Account]] | |||
==Accountability and Project Management== | ==Accountability and Project Management== | ||
To combine accountability with project management or time-like/process-based structures can be technically grounded in [[entropy pool]] as a way to make all projects accountable. In other words, accountability comes from having a reliable source of data that can be used to judge whether certain results have been met or not. | To combine accountability with project management or time-like/process-based structures can be technically grounded in [[entropy pool]] as a way to make all projects accountable. In other words, accountability comes from having a reliable source of data that can be used to judge whether certain results have been met or not. | ||
==Accountability and Resource Governance== | |||
The nature of governance is about making everything [[accountable]] through reliable data. To guarantee reliability of data, the technique of using a consistent [[namespace]] that shares a common [[entropy pool]] is the technical hypothesis. | |||
===Project Management and Governance=== | |||
To bound the spacetime perimeter of a project, accountability is decided by whether the data collected has [[soundness]], [[precision]], and [[terminability]]. In other words, [[accountability]] can be measured and analyzed using these technical parameters. In general, one can relate project decisions to be made by three sources: | |||
# Human decisions, based on the respective human agents or agencies' respective [[Externally Owned Account]]s. | |||
# Algorithmic decisions, made by the source code, are associated with an explicitly defined hashcode, which is considered to be a [[Contract Account]]. | |||
# Experiential decisions, mostly derived from prior execution trace data, stored in relevant [[Project Account]]s. | |||
<noinclude> | |||
{{PagePostfix | |||
|category_csd=Logic Model,Accountability,RLHF | |||
|semantic_labels=Part of:[[Part of::Logic Model]] | |||
}} | |||
</noinclude> | |||
Latest revision as of 06:39, 27 May 2023
Accountable and accountability should be grounded on information symmetry or some form of traceability of causal relations. It can be also considered as a way to perform abstract counting. In PKC, the accountability is assigned to three account types:
Accountability and Project Management
To combine accountability with project management or time-like/process-based structures can be technically grounded in entropy pool as a way to make all projects accountable. In other words, accountability comes from having a reliable source of data that can be used to judge whether certain results have been met or not.
Accountability and Resource Governance
The nature of governance is about making everything accountable through reliable data. To guarantee reliability of data, the technique of using a consistent namespace that shares a common entropy pool is the technical hypothesis.
Project Management and Governance
To bound the spacetime perimeter of a project, accountability is decided by whether the data collected has soundness, precision, and terminability. In other words, accountability can be measured and analyzed using these technical parameters. In general, one can relate project decisions to be made by three sources:
- Human decisions, based on the respective human agents or agencies' respective Externally Owned Accounts.
- Algorithmic decisions, made by the source code, are associated with an explicitly defined hashcode, which is considered to be a Contract Account.
- Experiential decisions, mostly derived from prior execution trace data, stored in relevant Project Accounts.
References
Related Pages
Part of:Logic Model