OAI / OAI/Arazzo-Specification
Actor-in-the-loop
- Dominant language
- JavaScript
- Stars
- 471
- Forks
- 69
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 19
Description
I am "renaming" this issue from the reference link below to continue forward with the name that we seem to all agree on. Shout out to Jay Hamilton for suggesting the more appropriate name given the proliferation of AI in pretty much everything and will likely be a stronger target for who would be the "in the loop" entity.
While no definitive release is on the agenda, we'd like to move this up pretty quickly as more and more tooling is in the works and this feature in particular has been brought up more often due to the growth of AI.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the reference issue #353 and the open pull request #568, which continues work on this proposal. Clarify the actor-in-the-loop scope and acceptance criteria in those discussions; done means the agreed feature is specified and represented by the associated work.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100