Open Issues Need Help
View All on GitHubLightweight orchestration harness built for your AI agents. The unfiltered truth about where your project stands.
Lightweight orchestration harness built for your AI agents. The unfiltered truth about where your project stands.
Lightweight orchestration harness built for your AI agents. The unfiltered truth about where your project stands.
Lightweight orchestration harness built for your AI agents. The unfiltered truth about where your project stands.
Lightweight orchestration harness built for your AI agents. The unfiltered truth about where your project stands.
Lightweight orchestration harness built for your AI agents. The unfiltered truth about where your project stands.
AI Summary: This GitHub issue proposes implementing a synchronization mechanism between Veritas Kanban and GitHub Issues to eliminate manual data entry for developers. It outlines two main approaches: a simpler one-way sync from GitHub to Veritas, or a more comprehensive bidirectional sync that keeps issue status, labels, assignees, and potentially comments updated across both platforms. The discussion also covers implementation details such as using webhooks versus polling and selectively syncing issues based on labels.
Lightweight orchestration harness built for your AI agents. The unfiltered truth about where your project stands.
AI Summary: This issue proposes abstracting direct file system (fs) imports behind a `StorageRepository` interface. The current system has 24 services directly importing `fs`, making it difficult to switch to alternative storage backends like databases or cloud storage. The solution involves defining the interface, implementing a `FileStorageRepository` that wraps existing `fs` behavior, and refactoring all 24 services to use this new repository for file operations.
Lightweight orchestration harness built for your AI agents. The unfiltered truth about where your project stands.
AI Summary: This issue proposes standardizing all API responses into a consistent JSON envelope format for both success and error scenarios, including pagination metadata. The goal is to eliminate current inconsistencies where responses vary widely in structure and error messaging. Implementation involves creating helper middleware, defining standard HTTP status codes, updating all existing API routes, and ensuring backward compatibility during the transition.
Lightweight orchestration harness built for your AI agents. The unfiltered truth about where your project stands.
Lightweight orchestration harness built for your AI agents. The unfiltered truth about where your project stands.
Lightweight orchestration harness built for your AI agents. The unfiltered truth about where your project stands.
Lightweight orchestration harness built for your AI agents. The unfiltered truth about where your project stands.
Lightweight orchestration harness built for your AI agents. The unfiltered truth about where your project stands.
Lightweight orchestration harness built for your AI agents. The unfiltered truth about where your project stands.
Lightweight orchestration harness built for your AI agents. The unfiltered truth about where your project stands.
Lightweight orchestration harness built for your AI agents. The unfiltered truth about where your project stands.