Proof of Supervision with Blockchain
The proposed frames to handle stamping engineered
Last updated
The proposed frames to handle stamping engineered
Last updated
The licensing boards will be constructed from the collective pallet.
We will also introduce a working group technical committee. Working groups define the standard of care for each category of work on the network.
Scope<Standard of Care::Electrical>
A standard of care working group organized around the objective to establish a standard of care for a discipline type. In this case, Electrical.
It is the responsibility of the working group to establish a minimum standard of care for electrical design in a manner that
helps assure public safety
without imposing erroneous administrative work on the community that would discourage engagement in compliance
members of the working group should propose a standard_of_care and internally vote on the final version.
this final version would then go to the network as the proposed standard of care for the network
submissions will implement the staking mechanism (ie the group would collectively bond the proposal, receiving the bond back if adopted by the community
only one formal standard_of_care may exist per category.
standard_of_care era is set to six months and is voted for adoption by network every six months. Any working group may submit an updated standard of care during that time if they have a better version. The network will vote on the standard of care.
The professional engineering license is modeled using the identity pallet. This pallet allows a user to put forth a proposed identity and ask for a review by any number of registrars.
An engineering board of directors may become a registrar on the network.
Adding registrars are currently done through the master admin (sudo); but will eventually be converted to a council decision.
Registrar has the authority to review the identity and validate it.
A user may assign an identity to their prime account which would represent their main user information (name, email, etc).
When applying for a license, a user creates an account and adds it as a sub-account. The user then submits the sub-account to the board to make a judgment (approve) the identity. The board can change the state of the identity.
Once the license (sub identity) is approved, the engineer uses this license address to seal drawings.
The contracts pallet allows for the distribution of generic smart contracts which deploy into the blockchain and represent the professional interactions for each licensed activity on the network.
Each professional enters into a Contract of Supervision when they begin working on a project.
This connects the licensed agents to the record of supervision for the project.
Because many jurisdictions require both the firm and the individual to be licensed, this contract may require authorization by both licensed parties: the firm and the individual.
Each individually permitted document should be deployed as a separate contract.
This Contract of Supervision should also store the state of the work contract including
deliverables - the list of deliverables and their state (percent completion).
discipline - the discipline associated with the supervision (elec, mech, etc)
standard_of_care - the standard of care implemented for the supervision
For the sake of practical implementation, we will limit the record of work to any substantial deliverable sent from professional outward which would increase the amount of completed effort by a minimum of 10 percent.
The Record of Work is a record of all major deliverable points, who performed the design, who checked the work, and who verified proof of the standard of care for the block entry.
For each record of work parties sign:
the designer submits work for review under a Minimum Standard of Care Configuration Trait
a reviewer checks work against theMinimum Standard of Care Configuration Trait
the professional signs that the document has been designed and backchecked per the Standard of Care
The contact may also be capable of recording payment history and terms. In the event of payment default, the contract would set the state of record drawings to invalid thereby prohibiting continued use of the construction documents (ie they would no longer be permitted for use in construction.
In the event of default, any queries to construction document status would
return an Error: Invalid Contract, Payment Default. NOT FOR CONSTRUCTION and
the contract would also engage the IPFS storage utility to encrypt the data to prevent further download until payment is remedied.
The contact may also be capable of recording payment history and terms. In the event of payment default, the contract would set the state of record drawings to invalid thereby prohibiting continued use of the construction documents (ie they would no longer be permitted for use in construction.
In the event of default, any queries to construction document status would
return an Error: Invalid Contract, Payment Default. NOT FOR CONSTRUCTION and
the contract would also engage the IPFS storage utility to encrypt the data to prevent further download until payment is remedied.
Documentation on how to implement.
Creates an origin that requires multiple parties to sign before authorizing a transaction.
This pallet tracks the reported offenses.
The community itself could check on the implemented standards of care and any violation would be reported as an Offense.
example: PermitZIP requires checklists as part of the process for every project, every deliverable. If the reviewer Validated a design without completing the checklist, this would be an Offence.
Allows account recovery if lost credentials based on M-of-N social recovery.
When a license is lost or stolen, this Pallet provides for a means of recovery which also secures the license.
The recovery process is protected by trusted "friends" and a specific threshold of that list is required to recover.
This helps to address the idea of an engineer losing "control" of their license.
the board could temporarily lock the license
any use of an illegal or invalidated license would notify the board
the engineer could go through the recovery process, and notify the board when recovered
when the account is recovered, the engineer can request it to be re-authorized (paying board fees as needed)
