<!--You can leave these HTML comments in your merged EIP and delete the visible duplicate text guides, they will not appear and may be helpful to refer to if you edit it again. This is the suggested template for new EIPs. Note that an EIP number will be assigned by an editor. When opening a pull request to submit your EIP, please use an abbreviated title in the filename, `eip-draft_title_abbrev.md`. The title should be 44 characters or less.-->
## Simple Summary
<!--"If you can't explain it simply, you don't understand it well enough." Provide a simplified and layman-accessible explanation of the EIP.-->
A standard interface for Human Capital Accounting tokens.
## Abstract
<!--A short (~200 word) description of the technical issue being addressed.-->
The following standard allows for the implementation of a standard API for HUCAP tokens within smart contracts. This standard provides basic functionality to discover, track and transfer the motivational hierarchy of human resources. While blockchain architecture has succeeded in the financialisation of integrity by way of transparency; correspondingly real world outcomes will be proportional to the degree of individualisation of capital by way of knowledge.
<!--The motivation is critical for EIPs that want to change the Ethereum protocol. It should clearly explain why the existing protocol specification is inadequate to address the problem that the EIP solves. EIP submissions without sufficient motivation may be rejected outright.-->
The Ethereum protocol architecture has a deterministic world-view bounded to the random reality of the human domain that supplies the intentions and logic. The yellow paper formally defines the EVM as a state machine with only deterministic parameters and state transition operators. Oracle requests to another on-chain contract, and/or off-chain HTTP lookups still make for multiple deterministic transactions.
A standard interface that allows the appraisal of individual capabilities concurrently with output and the overall knowledge-base will reduce market search costs and increase the autonomous insertion of mindful innovation into the blockchain ecosystem. We provide for simple smart contracts to define and track an arbitrarily large number of HUCAP assets. Additional applications are discussed below.
The Belief-Desire-Intention model is a plan-theoretic framework for establishing means-end coherence in agent based modelling system.
The blockchain's cryptographic security architecture reliably scales to a blockchain based PKI web-of-trust hierarchies.
ERC-20 token standard allows any tokens on Ethereum to be re-used by other applications: from wallets to decentralized exchanges.
ERC-721 token standard allows wallet/broker/auction applications to work with any NFT on Ethereum.
ERC-1155 Crypto Item standard allows a smart contract interface where one can represent any number of ERC-20 and ERC-721 assets in a single contract.
This standard is inspired by the belief–desire–intention (BDI) model of human practical reasoning developed by Michael Bratman as a way of explaining future-directed intention. A BDI agent is a particular type of bounded rational software agent, imbued with particular mental attitudes, viz: Beliefs, Desires and Intentions (BDI). The model identifies commitment as the distinguishing factor between desire and intention, and a noteworthy property that leads to (1) temporal persistence in plans and in the sense of explicit reference to time, (2) further plans being made on the basis of those to which it is already committed, (3) hierarchical nature of plans, since the overarching plan remains in effect while subsidiary plans are being executed.
The BDI software model is an attempt to solve a problem of plans and planning choice and the execution thereof. The complement of which tenders a sufficient metric for indicating means-end coherence and ascribing cost baselines to such outcomes.
## Specification
<!--The technical specification should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow competing, interoperable implementations for any of the current Ethereum platforms (go-ethereum, parity, cpp-ethereum, ethereumj, ethereumjs, and [others](https://github.com/ethereum/wiki/wiki/Clients)).-->
#### Main Interface
```
pragma solidity ^0.4.25;
pragma experimental ABIEncoderV2;
/**
@title ERC-**** Human Capital Accounting Standard
@dev See https://github.com/freeworkculture/kazini/issues/11
Note: the ERC-165 identifier for this interface is 0xf23a6e61.
*/
interface IERC_HUCAP {
/**
@notice Compute the index value of an Agents BDI in the ecosystem.
@param _address Set the stance of an agent
@dev For the purpose of
Throws on any error rather than return a false flag to minimize user errors
*/
function updateIndex() internal returns (bool);
/**
@notice Get the active/inactive and states of an Agent in the ecosystem.
@param _address Set the stance of an agent
@dev For the purpose of
Throws on any error rather than return a false flag to minimize user errors
*/
function iam() view public returns (bool iam_, IERC_HUCAP_TYPES.IS state_);
/**
@notice Fetch the bdi index value of an Agent in the ecosystem.
@param _address Set the stance of an agent
@dev For the purpose of
Throws on any error rather than return a false flag to minimize user errors
*/
function index() view public returns (uint8 index_);
/**
@notice Count of Public Keys in key ring of an Agent in the ecosystem.
@param _address Set the stance of an agent
@dev For the purpose of
Throws on any error rather than return a false flag to minimize user errors
*/
function ringLength() view public returns (uint ringlength_);
/**
@notice Get the PGP Public Key Id of an Agent in the ecosystem.
@param "" Set the stance of an agent
@dev For the purpose of
Throws on any error rather than return a false flag to minimize user errors
*/
function keyId() view public returns (bytes32 KEYID_);
/**
@notice Get the merit data of an Agent in the ecosystem.
@param "" Set the stance of an agent
@dev For the purpose of
Throws on any error rather than return a false flag to minimize user errors
*/
function merits() view public returns (
uint experience_,
bytes32 reputation_,
bytes32 talent_,
uint8 index_,
bytes32 hash_);
/**
@notice Get the accreditation of an Agent in the ecosystem.
@param "" Set the stance of an agent
@dev For the purpose of
Throws on any error rather than return a false flag to minimize user errors
*/
function kbase() view public returns (IERC_HUCAP_TYPES.KBase kbase_);
/**
@notice Get the desire of an Agent in the ecosystem.
@param _desire Pro-attitude
@dev For the purpose of
Throws on any error rather than return a false flag to minimize user errors
*/
function desire(bytes1 _desire) view external returns (bytes32);
/**
@notice Get the intention of an Agent in the ecosystem.
Throws on any error rather than return a false flag to minimize user errors
*/
function intention(bool _intention, IERC_HUCAP_TYPES.IS _state) external returns (IERC_HUCAP_TYPES.IS);
/* End of interface IERC_HUCAP */
}
```
#### User Defined Types Extension Interface
<!--The technical specification should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow competing, interoperable implementations for any of the current Ethereum platforms (go-ethereum, parity, cpp-ethereum, ethereumj, ethereumjs, and [others](https://github.com/ethereum/wiki/wiki/Clients)).-->
<!--The technical specification should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow competing, interoperable implementations for any of the current Ethereum platforms (go-ethereum, parity, cpp-ethereum, ethereumj, ethereumjs, and [others](https://github.com/ethereum/wiki/wiki/Clients)).-->
```
pragma solidity ^0.4.25;
pragma experimental ABIEncoderV2;
interface IERC_HUCAP_KEYSIGNING_EXTENSION {
bytes32 constant public _InterfaceId_ERC165_ = "CREATOR 0.0118 XOR OF ALL FUNCTIONS IN THE INTERFACE"; // Complies to ERC165
// KEY MASKING TABLE
// bytes32 constant public MASK = 0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff;
// bytes32 constant public KEYID = 0xffffffffffffffffffffffffffffffffff90EBAC34FC40EAC30FC9CB464A2E56; // EXAMPLE PGP PUBLIC KEY ID
// bytes32 constant public KEY_CERTIFICATION = 0x01ffffffffffffff <<192;//“C”KeyCertification
// bytes32 constant public SIGN_DATA = 0x02ffffffffffffff <<192;//“S”SignData
// bytes32 constant public ENCRYPT_COMMUNICATIONS = 0x04ffffffffffffff <<192;//“E”EncryptCommunications
// Clearance constant public Trust = 0x03ff <<192;//Trust:Unknown
// BYTES32 Value with
// Public Key Id, masking
// Key Certification masking
// Split Key masking
// Generic masking
// Ordinary masking
// Trust.Unknown masking
// bytes32 constant public DOER = 0x11ff10ff100f03ffff00ffffffffffffffff90EBAC34FC40EAC30FC9CB464A2E56;
bytes32 constant public KEY_CERTIFICATION = 0x01ffffffffffffff <<192;//“C”KeyCertification
bytes32 constant public SIGN_DATA = 0x02ffffffffffffff <<192;//“S”SignData
bytes32 constant public ENCRYPT_COMMUNICATIONS = 0x04ffffffffffffff <<192;//“E”EncryptCommunications
bytes32 constant public ENCRYPT_STORAGE = 0x08ffffffffffffff <<192;//“E”EncryptStorage
bytes32 constant public SPLIT_KEY = 0x10ffffffffffffff <<192;//Splitkey
bytes32 constant public AUTHENTICATION = 0x20ffffffffffffff <<192;//“A”Authentication
bytes32 constant public MULTI_SIGNATURE = 0x80ffffffffffffff <<192;//Heldbymorethanoneperson
bytes32 constant public TRUST_AMOUNT = 0xffffffffffff00ff <<192;
bytes32 constant public BINARY_DOCUMENT = 0xffff00ffffffffff <<192;//0x00:Signatureofabinarydocument.
bytes32 constant public CANONICAL_DOCUMENT = 0xffff01ffffffffff <<192;//0x01:Signatureofacanonicaltextdocument.
bytes32 constant public STANDALONE_SIGNATURE = 0xffff02ffffffffff <<192;//0x02:Standalonesignature.
bytes32 constant public GENERIC = 0xffff10ffffffffff <<192;//0x10:GenericcertificationofaUserIDandPublic-Keypacket.
bytes32 constant public PERSONA = 0xffff11ffffffffff <<192;//0x11:PersonacertificationofaUserIDandPublic-Keypacket.
bytes32 constant public CASUAL = 0xffff12ffffffffff <<192;//0x12:CasualcertificationofaUserIDandPublic-Keypacket.
bytes32 constant public POSITIVE = 0xffff13ffffffffff <<192;//0x13:PositivecertificationofaUserIDandPublic-Keypacket.
bytes32 constant public SUBKEY_BINDING = 0xffff18ffffffffff <<192;//0x18:SubkeyBindingSignature
bytes32 constant public PRIMARY_KEY_BINDING = 0xffff19ffffffffff <<192;//0x19:PrimaryKeyBindingSignature
bytes32 constant public DIRECTLY_ON_KEY = 0xffff1Fffffffffff <<192;//0x1F:Signaturedirectlyonakey
bytes32 constant public KEY_REVOCATION = 0xffff20ffffffffff <<192;//0x20:Keyrevocationsignature
bytes32 constant public SUBKEY_REVOCATION = 0xffff28ffffffffff <<192;//0x28:Subkeyrevocationsignature
bytes32 constant public CERTIFICATION_REVOCATION = 0xffff30ffffffffff <<192;//0x30:Certificationrevocationsignature
bytes32 constant public TIMESTAMP = 0xffff40ffffffffff <<192;//0x40:Timestampsignature.
bytes32 constant public THIRD_PARTY_CONFIRMATION = 0xffff50ffffffffff <<192;//0x50:Third-PartyConfirmationsignature.
bytes32 constant public ORDINARY = 0xffffffff100fffff <<192;
bytes32 constant public INTRODUCER = 0xffffffff010fffff <<192;
bytes32 constant public ISSUER = 0xffffffff001fffff <<192;
// EDGES MASKING TABLE
Clearance internal TRUST = Clearance({
Zero: 0x01ff <<192,
Unknown: 0x03ff <<192,
Generic: 0x07ff <<192,
Poor: 0xF0ff <<192,
Casual: 0xF1ff <<192,
Partial: 0xF3ff <<192,
Complete: 0xF7ff <<192,
Ultimate: 0xFFff <<192
});
/**
/// @notice Cycle through state transition of an Agent in the ecosystem.
function setAllPromises(bytes32 _serviceId) external onlyControlled;
/* End of interface IERC_HUCAP_TRACKUSERS_EXTENSION */
}
```
## Rationale
<!--The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages. The rationale may also provide evidence of consensus within the community, and should discuss important objections or concerns raised during discussion.-->
[WIP]
## Backwards Compatibility
<!--All EIPs that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity. The EIP must explain how the author proposes to deal with these incompatibilities. EIP submissions without a sufficient backwards compatibility treatise may be rejected outright.-->
[WIP]
## Test Cases
<!--Test cases for an implementation are mandatory for EIPs that are affecting consensus changes. Other EIPs can choose to include links to test cases if applicable.-->
[WIP]
## Implementation
<!--The implementations must be completed before any EIP is given status "Final", but it need not be completed before the EIP is accepted. While there is merit to the approach of reaching consensus on the specification and rationale before writing code, the principle of "rough consensus and running code" is still useful when it comes to resolving many discussions of API details.-->
[WIP]
## Copyright
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).