issues Search Results · language:Dune language:Python linked:pr language:Java language:JavaScript language:JavaScript
Filter by
5.8M results
Parent
#4
What to build
AuditHistoryRecord has a column named transaction_id that stores str(TransactionRecord.id) — the internal surrogate UUID
primary key, not the external transaction_id supplied ...
ready-for-agent
sfxdeve
Parent
#4
What to build
All 14 SQLAlchemy ORM models live in shared/records.py, a single 386-line file owned by no domain module. Every other
module imports from shared/. ADR-0011 mandates clear internal ...
ready-for-agent
概要
献立自動化アプリのバックエンド Phase 1 を実装する。
DB 設計（5テーブル）
-- ユーザー
CREATE TABLE users (
id BIGSERIAL PRIMARY KEY, email VARCHAR(255) UNIQUE NOT NULL,
password_hash VARCHAR(255) NOT NULL, name VARCHAR(100), ...
enhancement
shimo2000px
hwm31Parent
#4
What to build
PRD issue #4 specifies Module 1 as: IngestTransaction(raw_payload: dict) → Result[Transaction, ValidationError].
Currently, transaction validation happens implicitly through ...
ready-for-agent
Parent
#4
What to build
The PRD (issue #4, Alert Object Contract) specifies transactionId, accountHolderId, accountId, and counterpartyId as
direct fields on the Alert object. The current AlertDetailResponse ...
ready-for-agent
Parent
#4
What to build
Several files exist as dead weight after out-of-scope endpoints were removed (per issue #183). None are registered in
main.py, none are imported by live code paths. Delete them ...
ready-for-agent
Parent
#4
What to build
In the no-alert branch of scoring/engine.py, risk_score is hardcoded to 8 regardless of what the supervised or anomaly
models returned. The PRD (issue #4) specifies that Risk ...
ready-for-agent
Parent
#4
What to build
severity_rank is defined twice with divergent signatures:
- scoring/types.py — takes a Severity enum value, returns int(severity.value[1:]). The docstring explicitly calls ...
ready-for-agent
Parent
#4
What to build
complaints/api.py contains a logic bug in _apply_complaint_reevaluation: the return score_and_upsert_alert(...) call is
indented one level too deep, placing it inside the for ...
ready-for-agent
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.
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.