[Docs] Document protocol used by Flyte CoPilot

[kumare3]

Motivation: Why do you think this is important? When new users are using CoPilot, the protocol used to communicate should be clearly documented.

Goal: What should the final outcome look like, ideally? Any user should be able to refer to this documentation and use coPilot

Describe alternatives you've considered NA

Flyte component

• [x] Overall
• [ ] Flyte Setup and Installation scripts
• [x] Flyte Documentation
• [ ] Flyte communication (slack/email etc)
• [ ] FlytePropeller
• [ ] FlyteIDL (Flyte specification language)
• [ ] Flytekit (Python SDK)
• [ ] FlyteAdmin (Control Plane service)
• [ ] FlytePlugins
• [ ] DataCatalog
• [ ] FlyteStdlib (common libraries)
• [ ] FlyteConsole (UI)
• [ ] Other

[Optional] Propose: Link/Inline NA

Additional context NA

Is this a blocker for you to adopt Flyte This is a blocker to use CoPilot

[kumare3]

The design for flyte copilot is available here. this should be converted to the documentation

[kumare3]

@SandraGH5 FYI

[github-actions[bot]]

Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏

[github-actions[bot]]

Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏

[davidmirror-ops]

Is this still a need? Also the referenced design doc is not accesible

[github-actions[bot]]

Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable. Thank you for your contribution and understanding! 🙏