Humboldt
Docs

Coding harness designed for long‑running async work

Humboldt is designed for long running async work. Give it a task, and it will execute in the background. If it needs you, it will find you.

Install Humboldt Commands
$ hum
▄▄ ▄█▘ hum 0.1.58
▄▄▟▙███▙▖ kimi-k3 · abhishek@metaphi.ai
▀▜█▛▙▚▖ ~/authdomain
› You are a senior COBOL developer. Read README.md and docs/HLD.md, then implement the Authorization Domain. Ask me before you decide anything I would want to decide.
● I'll read the HLD and survey the current repository state first.
● reading docs/HLD.md
● reading core_mainframe_layer/src/progs/OAUT001.cbl
● plan Define Authorization data model and DB2 DDL · Define Common Format copybooks · Four validators · Orchestrator · TCP connector · Log management · EOD reconciliation · Tests
╭ Scope
│ ? How much of the Authorization Domain backlog should I implement in this pass? (1 of 4)
│ 1. Full backlog — All 12 backlog items, in the HLD's build order (default)
│ 2. Core slice only — DB + 4 validators + Orchestrator + logging; defer OAUT002, EOD recon and tests
│ 3. DB + validators only — Data model, tables, and the four validators; stop before the Orchestrator
│ a number picks · type an answer · enter takes the default
╰
⠙ waiting for your answer · 8m 39s
$ hum resume
› The whole Authorization feature list in the HLD. A first phase is acceptable only if it says what is left, and the first phase is real: it compiles, it runs, CICS, DB2.
● writing core_mainframe_layer/DB2/DAUT001.sql
⎿ wrote 4028 bytes

Close the terminal and it keeps going. hum resume brings you back to the question it is waiting on, from any terminal. Every session teaches the next one how you want work done.