Value Statement

1. Spike Investigate/learn SpiceDB and
2. draw the sequence diagram of interactions and API calls needed (Use Spice db sandbox).
3. How could spiceDB be packaged in MCGH (including basic license checks etc)

Note, as of today, GH does not have a REST API unless Mgmt Fabric comes through. 

This spike is intended to give the engineers an idea about SpiceDB and not get familiar with additional work Authz team has done. That will covered in a separate story.

Definition of Done for Engineering Story Owner (Checklist)

• ...

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.