SolidLabResearch / SolidLabResearch/user-managed-access
Look into splitting policy reasoning apart from koreagrafeye
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 4
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 3
Description
This is more modular, allowing us to exchange the policy reasoner separate from the orchestrator. Whatever policy reasoner then feeds its conclusions to whatever orchestrator.
Contributor guide
No contributing guide indexed for this repository
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 repository's koreagrafeye implementation and tracing how policy reasoning currently reaches the orchestrator. Clarify the boundaries needed so a policy reasoner can be exchanged independently and its conclusions can be consumed by an orchestrator; done means those responsibilities are modular and replaceable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100