Why

The AppStudio (the HAS component) has a requirement to store application deployment manifests in Git under some folder structure.  Instead of reinventing the wheel, we should extend kam to expose the feature as a "library" so that we have an unified folder structure and the consumers need not to concern about it.

What

We should identify the exact requirement from HAS.  We are looking to expose kam as some generic APIs for client code to perform create, read, write operation on application manifests.

Acceptance Criteria

• Details the requirements of the kam library
• Document some high level approaches to make kam to provide the APIs.