glowkeeper / glowkeeper/feedbacker

Decide the model, provider, and deployment architecture

Open
#7 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
CSS
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Define an architecture that preserves institutional control while allowing models and providers to evolve.

### Deliverables
- Provider abstraction and model-selection boundaries
- Prompt and policy versioning approach
- Deployment, tenancy, security, and observability options
- Decision record covering build-versus-buy trade-offs

### Done when
The architecture supports traceability, privacy, portability, and educator control.

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named. Start by mapping the provider and model-selection boundaries, then document prompt and policy versioning alongside deployment, tenancy, security, and observability options. Done means a decision record covers build-versus-buy trade-offs and the architecture supports traceability, privacy, portability, and educator control.

Written by the indexing model from the issue text.

Assessment

Domain
ai, cloud, observability, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.