issues Search Results · language:Dune language:Python language:HTML language:HTML language:JavaScript language:JavaScript
Filter by
47M results
[Docs]: Study Sync Project Duplication
Related Issue
None
Description
There are currently two folders in the repository:
- Stydy Sync (without a README.md file)
- Stydy-Sync (appears in code but ...
documentation
Parent
#799
What to build
Rewire Orchestrator to use the first-class Pool module for admission state, candidate projection, Pool size observation,
and Match Verdict application. This is a structural ...
ready-for-agent
refactor-slice
Proposal ticket. See backlogs/proposal/LKPR-62-memory-splitting.md on main for full spec.
S:Proposal
Currently:
% curl http://central-dev.localhost:8989/v1/projects/1/actor-properties \
-u $ODK_EMAIL:$ODK_PASSWORD
[{ name : department },{ name : region }]
% curl http://central-dev.localhost:8989/v1/projects/1/app-users ...
Parent
#799
What to build
Move Match Verdict application behind the Pool interface. Given judge verdicts, the Pool applies them in Rank order,
recovers Card content and URL data, writes Daily Top-5 ...
behavior-slice
ready-for-agent
Parent
#799
What to build
Make candidate projection a Pool-interface behavior. After listings enter the Pool, callers can ask the Pool for Match
Judge candidates; the Pool reads Card Store records and ...
behavior-slice
ready-for-agent
Parent
#799
What to build
Introduce as the first-class owner of run-scoped Pool admission state. This slice is structural only: it creates the
module and the narrow admission/state surface that can ...
ready-for-agent
refactor-slice
Parent
#799
What to build
Update CONTEXT.md so the Pool vocabulary matches the PRD: Pool remains the run-scoped set of rediscovered/current-run
matched listings, but it is also a first-class in-process ...
docs-slice
ready-for-agent
Prerequisites
- [x] I searched open issues and this has not already been proposed.
- [x] I searched discussions and this is not already being debated there.
- [x] This is a concrete, actionable ...
enhancement
ready for review
Summary
The reconcile station s parse_error path re-prompts the SAME provider (#68) but never advances to the NEXT provider in
the reconcile chain. When the lead reconcile provider emits unparseable output ...
bug

Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip! Restrict your search to the title by using the in:title qualifier.