Look into splitting policy reasoning apart from koreagrafeye

Open
#19 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
backend, security

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.

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.

Dominant language
TypeScript
Stars
9
Forks
4
Avg merge
4d 21h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SolidLabResearch/user-managed-access

All issues in SolidLabResearch/user-managed-access

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.