You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Goal: Get Q&A pairs from Argilla into access-qa-service (pgvector) so they're searchable via semantic search.
Discovery: access-qa-service already had a /admin/sync endpoint and argilla_sync.py — but the code was scaffolded with placeholder logic that didn't match the actual Argilla v2 API or the record schema created by access-qa-extraction.
The core idea: There is no "lifecycle event" entity. An "Initial Assessment" or "Vision Development Session" is just a session template that a coach creates, fills with whatever drills and metrics they want, and optionally tags (once #63 ships) as milestone, onboarding, etc. The system doesn't know what an "Initial Assessment" is. It knows what a session template is, what a tag is, and what a due date is. The coach defines the meaning.
The flow, using only what exists today
Coach builds a session template in the library — specific drills, specific metrics (could be court drills with numeric metrics, reflection exercises with text prompts, or a mix)
Coach instantiates it for a player → creates a real session with snapshotted drills, session_template_id recording lineage, a due_at for the deadline
Player (or coach) does the work, records measures
Coach clicks "Mark Complete" → completed_at is set once, permanently
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters