Define RA

[tessmichi]

📝 Description

Document in GitHub:

• What is an RA?

• What is an example of an RA? Does the size matter?

• How to make a new RA?

  • What pieces should an RA always have? Optional?
  • Standardization: make a template or checklist
  • CAIRA users should have a consistent experience across RAs, regardless of the included resources or when said RA is added.
  • Criteria for qualifying a proposed RA should be documented and accessible. This documentation will likely need to be internal as it shall be driven by customer signal.
  • Minimum required components and any/all specific guidelines about what makes a quality RA should be included in the contributing docs in the CAIRA repo. This will allow anyone creating or updating an RA (and those reviewing such things) to have easy access to the details.

• Currently we have a platform technology focus. Is that still the case?
  For all Records to Create, check the following:

• Decisions have been logged

• Team has been looped in via design session with quorum - async is fine if timing is a struggle and quorum can't be achieved, but following up with responses is needed

• In scenarios where multiple options are evaluated, comparisons have been done and shared, published to GitHub where applicable

• Decisions have been presented to leadership for review

• Make new backlog items that reflect any new work scoped out as part of this story, or not finished upon closure of the story.

🔰 Code of Conduct

• I agree to follow this project's Code of Conduct.