Document whether/how to include decision/transfer docs in the repo

[samglover]

Perhaps a decisions, transfer, or handoff folder? Or if they should be private, perhaps simply including a link to a project folder in the LIT Lab's OneDrive?

[samglover]

This will have to be a generalized guide. For LIT Lab projects, each project has its own channel in the LIT Clinic Teams team for discussions, files, etc. Perhaps include how other interview building teams do it?

[samglover]

On reflection I think the primary place to document transfer information should be the README. If there needs to be more extensive documentation, information about where to find it should be included in the README.

[samglover]

From #472:

For more complex interviews, it can be useful to start with a flowchart that can be approved by stakeholders. Then the interview can be tested against the flowchart.

Perhaps more critically, some jurisdictions have complex e-filing logic. Documenting this logic as a Mermaid flowchart in the repo would make it possible for the court or org to request changes like any other pull request, and give the developer(s) clear guidance for implementing those changes in the code.

I think we should probably add a docs folder in interview repos when they contain flowcharts or other documentation (such as transfer memos).