---
# System prepended metadata

title: 'Issuing Mines Act Permits from CORE:'
tags: [Digital Trust]

---

# Issuing Mines Act Permits from CORE:

## Issuing to OrgBook
18 months ago a feature was added to TEST CORE that allows admin users of CORE, to publish individual permit amendments to OrgBook. This feature was never migrated to production. 

If there is a desire to promote this functionality to production, I would strongly recommend consulting with the BC Digital Trust Services Applications Team (Headed by Emiliano Sune) to see if there a new recommended approach to publishing to OrgBook.


## Issuing to Business Wallets
If there is a desire to expand on this functionality to enable publishing to the propoents' Business's Organizational wallets, the only existing artifacts that could be re-used, would be the schema definition itself. which can be found here on the production ledger Sovrin MainNET. https://indyscan.io/tx/SOVRIN_MAINNET/domain/58160


### Work Item List: 

#### BCDT Applications Team (Emiliano Sune): 

- Have a production instance of Traction, that is setup to write to an appropriate production ready ledger (e.g. Sovrin MainNET, or CAN-dy Production if that exists)
    - **Approx Effort**: Unknown (0-2wk?)

- Provide integration instructions and credentials for direct API access from CORE-API to Traction
    - Assumption:
        - Security features exists to provide integrators direct access to manage their tenant within traction
    - **Approx Effort**: Unknown (0-2wk?)

- Provide a traction tenants in Dev, Test, and Prod to represent the appropriate authority that can issue mines act permits (e.g. Chief Inspector Of Mines) this wallet represents the entity outlined in the laws/acts that has been given the authority to issue this Authority (e.g. Mines Act Permit), expect this wallet to persist through ministry re-organizations and changes in staff. 
    - Assumption:
        - Prod instance exists
    - **Approx Effort**: 2 hours 



#### BCDT Startup Team (Aaron Unger and Kyle Robinson)

- Advise MDS team on any revisions to the existing schema (https://sovrin-mainnet-browser.vonx.io/browse/domain?page=1&query=mines&txn_type=101)
- Support creation of goverance documentation
- Educate on the steps required to establish the trust needed BEFORE issuing the credential
    - Establishing a connection
    - Requesting proof of business license
- Discuss if revocation is required?
- Educate/onboard the MDS team to use the Tenant UI
- OPTIONAL: Establish a credential for the Issuing Wallet to hold, that represents it's authority to issue a mines act permit.

**Approx Effort: ??**


#### MDS Team:

- Clarify security and business requirements for these actions before development.
    - Which subset of users should actually be able to execute these actions?
    - Should they be integrated into existing application application workflows?
    - What level of auditing is required to know who execute certain actions in the past?

- Understand the usability requirements and limitations of VC's 
    - Organizational vs Personal wallets
    - Active internet connection

- Understand Tenant UI and relevant features.
    - Schema Creation 
    - Credential Definition Creation
    - Revocation?
    - If needed
        - Connection establishment
        - Present-proof requests
        - Credential Offers
    
- Integrate 3 actions into the CORE application that must be completed in this order. **Any or all of these steps could be done through the Tenant UI, but integration with all three of these steps is the goal**. 
    1. Connection invitation (and visibility of state, [none, requested, active])
        - Assumptions: 
            - 1 proponent business wallet per mine OR permit
            - business have business wallets
        - Approx Effort: 1 wk
    1. Request proof of business license (and visbility of state, [none, requested, verified, not-verified, error])
        - Assumptions:
            - Proponent wallet has BC Registries Business Licence credential 
            - Not required to re-do this action
            - Only done once per connection
        - Approx Effort: 2 wks
    1. Offer Mines Act Permit Credential (and visibility of state, [none, offered, issued, acked, error])
        - Assumptions: 
            - One issuance per Permit or Amendment (permit_amendment record in MDS)
        - Approx Effort: 2 wks
    1. Revocation of Mines Act Permit
        - Assumptions: 
            - Revocation is required
        - Approx Effort: 1 wk