Skip to content
View dev-belly's full-sized avatar

Block or report dev-belly

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
dev-belly/README.md

I'm dev-belly, a Data Science & Big Data Technology student at Central University of Finance and Economics. I build tools for credit risk, financial data analysis and quantitative research.

把金融问题拆成能运行、能检验、能追溯的系统:从 SQL 客群分析和人工复核,到决策时点的数据、财报指标与组合风险。

New here? Change one invoice timestamp in your browser, install a project from an empty directory, or review a business decision and its code. 新访客可先在浏览器核对三次固定决策,再改一个时间;招聘与面试审阅可沿业务问题、结果和代码查看。

Start with a business question

Pick a route: credit & data → CreditVintage / PITBridge; quantitative research → AlphaForge / TradeForge / StressAtlas; accounting & audit → AuditLens / ControlTrace / LedgerX. The complete project directory connects all public projects to their README, methods, demos and data boundaries.

Question Open the result Follow the code
Does a model hold up on later funding cohorts? 35,000 observed SBA loans Training and refitting · Protocol
Which credit cohorts need attention? SQL credit analysis Cohort SQL · Review workflow
Do the inputs meet explicit coverage rules? Policy check · Coverage and delays Rules and replay · Contract
What could a decision know before a late correction arrived? Run three decisions in your browser Three-decision example
How does clustered default change portfolio losses? Stress report Tail math and uncertainty

A useful result includes its limits. The SBA study uses real funding dates and a native 24-month recorded charge-off target. Logistic AUC is 0.6723 on 10,000 later loans; calibration improves Brier while reducing ranking performance. The final snapshot cannot establish historical first-publication times. Separate UCI static and synthetic event experiments retain their own targets. Project evidence connects each claim to inputs, code and validation.

Flagship projects

CreditVintage — 35,000 observed SBA loans across separate funding cohorts and mature 24-month charge-off horizons; retrospective validation.

01 · CreditVintage — Credit analysis with evidence you can refit.

35,000 笔 SBA 真实放款跨期研究:2 万训练、5 千校准、1 万测试,阶段间等待完整 24 月记录内核销表现期。四项批准时输入只在训练集拟合预处理;测试 AUC 0.6723,同 1,000 个复核名额找到 26/89 个事件。保留校准后排名下降、逐年结果和 300 次配对月份重采样;原始官方 CSV 可完整重建,安装包可离线重拟合。

最终快照没有历史首次发布或特征修订记录,因此作为回溯放款研究;原合成时点控制实验和静态 UCI 目标分开解释。核验成功不代表生产部署或避免损失。

Observed-loan report · Run it · Source · Checked v0.8.0

More experiments: static credit, input quality and human review

公开信用卡实验覆盖 30,000 条 UCI 记录、五次固定划分和四种方法,保留 12 万个模型分数、三档相同复核预算及无标签队列;历史单一客群的随机切分与 SBA 放款分期研究及合成时序验证分开解释。

合成事件流程用 SQL 按放款月份和客群对照预测与成熟事件;固定容量队列不含未来标签。SQLite 复核记录认领、结案、理由和材料引用,并处理并发版本冲突与重复请求。

可编辑 CSV 样例在训练前按文件、行号诊断;早期预检无需当前结果标签。两表输入诊断覆盖、迟到和分布,显式整体/月度规则保留失败与证据不足;宽松规则通过仍不等于评分就绪。

30,000-account comparison · Coverage policy · Input distributions · SQL analysis · Synthetic lineage


PITBridge — event and knowledge time, revision-safe snapshots, rolling financial features and independent Python replay.

02 · PITBridge — Reconstruct what a decision could actually know.

同时考虑事件、发布、入库时间与历史修订;构造决策时点快照和 7/30 天滚动特征。每个聚合值保留源记录成员,SQLite 结果与独立 Python 实现逐项核对。先试一张发票,再接 CSV 或可选的 pandas。

Source · Run in browser · Invoice / CSV example · Snapshot report · Rolling features


StressAtlas — correlated defaults, discrete-tail VaR and expected shortfall, sector attribution and paired bootstrap uncertainty. Diagram is schematic.

03 · StressAtlas — A tail estimate should come with its uncertainty.

用借款人层面的相关违约路径比较基准与压力情景;计算离散尾部 ES 和行业贡献,再用成对重采样检查估计精度。相同借款人的多笔贷款共享一次违约事件;不把平均损失的标准误当作 VaR 的置信区间。

Source · Stress report · Tail precision · Method

Examples identify their public-filing, public static-credit or synthetic inputs. Static and synthetic experiments do not establish future borrower risk or live investment performance.

More financial systems

Explore financial statements, execution, accounting and audit tools
Project What to inspect Result / walkthrough
StatementTrace Public filings → availability cutoff → exact fiscal periods → financial metrics Live report · SEC source ledger
NetworkClear Counterparty shocks, exact debt clearing and outside-loss reconciliation Live report · Clearing method
AlphaForge Trading-session splits, rolling returns and factor covariance Archived comparison and protocol correction · Synthetic sample run
TradeForge C++ execution events checked against an independent Python reference Public-quote matching case · Synthetic demo
ControlTrace Audit conclusions tied to the current evidence version Case study
AuditLens Anomaly detection → an explainable review item Workpapers
LedgerX Trading fills, accounting entries and valuation reconciled exactly Valuation example

Know the data boundary: StatementTrace uses curated public-filing excerpts. AlphaForge's archived price and synthetic runs used calendar-day buffers for trading-session labels; they have not been refitted under the corrected splitter and do not establish leakage-free out-of-sample performance. Historical membership/publication records are also incomplete. TradeForge's public depth capture powers hypothetical fills. CreditVintage's dated-event demonstrations, StressAtlas and NetworkClear remain synthetic. Its SBA study is retrospective funding-cohort validation with absent historical publication/revision records. UCI card and German experiments retain their distinct native targets; random customer splits do not establish future-period performance. Read the matching assumptions before quoting a market cost.

Core tools: Python, SQL, C++20, scikit-learn, LightGBM and NumPy.

Research in public

Inspect recent changes and their validation

Recent changes connect the demonstrations to concrete operational checks:

  • Maintenance and application repairs · 2026-10-27: validation record connects fixed Action source commits with invalid-session rejection, recoverable initialization, consistent pagination and a dated-source review.

  • Financial correctness · 2026-10-27: close six concrete failures across AlphaForge #5–7, AuditLens #9, ControlTrace #8 and TradeForge #21: trading-session separation, complete rolling windows, rectangular factor exposures, decimal digit boundaries, missing approval identities and rejected-fill rollback. Changes and checks · Practice the counterexamples.

  • Observed loans across time: CreditVintage #35 reconstructs 35,000 loans from two complete official SBA CSVs, retains mature calendar gaps and separate calibration, and refits its full portable evidence. All methods, both test years and weaker calibrated ranking remain visible. Run it · Method and limits.

  • Check explicit coverage rules: CreditVintage #34 checks retained diagnostics with exact overall/monthly counts, preserves failed/insufficient rules and separates policy outcome from evidence replay. An independently saved digest can pin approved rules. Run it · Validation.

  • Diagnose unavailable inputs: CreditVintage #33 keeps every expected feature slot and separates visible late arrivals, post-decision observations and still-unseen events. Its evidence replays without outcomes or fitting, while strict scoring/distribution gates retain their missing-feature failures. Run it · Validation.

  • Explain input changes before fitting: CreditVintage #32 adds two-table feature monitoring without any outcome file: four numeric KS distances, segment total variation, monthly sample gates and replay from retained decision-time events. Run it · Validation and scope.

  • Check early monitoring before training: CreditVintage #28 adds model-free preflight --as-of: mature historical populations, a visible label-free current cohort and explicit future-application counts. Exact source and validation retain the 273-test result and installed-wheel replay.

  • Consistent calendar inputs: CreditVintage #26 applies the same YYYY-MM-DD contract to CSV diagnostics, monitoring cutoffs and saved report evidence. The fix is included in the checked v0.3.2 release; validation and upgrade notes connect installation to its evidence.

  • Observed data, explicitly bounded: AlphaForge #4 retains all 22 historical-price comparison cases and independently rechecks reported returns. Its split-protocol correction leaves those figures archived pending refitting. TradeForge #14 replays public quote packets offline into 18 hypothetical matching/fee/latency scenarios. Neither proves a tradable edge or actual order fills.

  • Installed packages: CreditVintage #12 and PITBridge #13 replay built wheels in clean environments outside their source trees on Linux and Windows.

  • Credit review: CreditVintage #11 adds ownership, recorded reasons and retry protection; #14 delivers evidence that replays without the database.

  • Failure paths: LedgerX #4 stages whole retriable batches; AuditLens #5 refuses conflicting master records; WeCom #3 keeps queries on one index generation.

  • Evidence and report access: ControlTrace #5 binds conclusions to evidence versions; TradeForge #13 confines report requests to the configured directory.

Build history · Validation evidence and exact commits · Business walkthrough and interview practice

准备面试可先用 60 秒讲解与五个追问,再沿实际操作、失败场景和代码展开。

Experiments & earlier work
Experiment What it explores
Investor Network GNN Graph ablations and three-seed saved predictions.
High-dimensional Causal Allocation Lab Simulated causal estimation and robust allocation; interactive example.
Interval Financial Risk A retained negative result: distributional features reduced AUC in this synthetic experiment.
FactorLab A-share factor evaluation and purged validation; 中文文档.
WeCom Agent Platform Contract filtering and currency-aware holding totals; offline business trial.
Personal AI Chat Local chat plus a separately configured private model connection.

Earlier builds: Digital Craftsman · Ranxin · Goose Leg Auntie.


想试用或参与:先选项目目录,运行问题到对应仓库反馈;主页导航、文字或证据链接问题可用主页问题表单。贡献说明 · 安全报告说明。

Start here · All projects · Project evidence · Business walkthrough · Open-source roadmap · Portfolio review · Project adoption · Design references · Profile CI

Financial questions. Runnable code. Evidence you can inspect.

Pinned Loading

  1. CreditVintage CreditVintage Public

    Point-in-time credit evaluation, SQL cohort analysis and transactional label-free review workflows with replayable evidence.

    Python 1

  2. PITBridge PITBridge Public

    Availability-aware financial feature snapshots with SQLite, revision-safe temporal joins, source lineage and independent Python replay.

    Python 1 1

  3. StatementTrace StatementTrace Public

    As-of financial statements from public SEC filings: period and unit contracts, financial-ratio lineage, and semantic evidence replay.

    Python 1

  4. StressAtlas StressAtlas Public

    Credit portfolio stress scenarios with borrower-level defaults, global/sector factors, exact empirical ES and paired Monte Carlo comparisons.

    Python 1

  5. alphaforge alphaforge Public

    Python tools for factor research, walk-forward evaluation, portfolio optimization, and cost-aware backtesting. Synthetic sample data included.

    Python 1

  6. TradeForge TradeForge Public

    Event-driven market microstructure and execution research platform: C++20 limit-order-book core, Python research layer, and a TCA stack that refuses to report a number it cannot justify.

    Python 1