Six repos, 270 sessions: taxonomy engine ships with 670 tests
2026-04-06
Signal
The heaviest multi-project day yet: six repos touched across 270 sessions, headlined by the jobs-apply taxonomy classification engine shipping with 670 passing tests and the internal audit pipeline v2 spec locking in a 4-channel agentic architecture.
Evidence
- rusty-dakka: 78 sessions overhauling wiki indexing, full-text search, and Markdown rendering for the vault integration layer
- jobs-apply: Taxonomy classification engine built on BLS SOC and O*NET role families, 670 tests passing; integrated into AI build chain
- jobs-apply: Node.js version pinned to >=20 <24 for Vercel build compatibility; DOM snapshots added to error paths
- internal audit pipeline: Pipeline v2 spec written: agentic crawl integration with 4-channel architecture (SERP, direct, social, partner)
- internal audit pipeline: Layer 6.5 time repair gate wired between L6 and L7: hard gate rejecting placeholder times at 1% tolerance
- oil: v22 CHANGELOG updated covering v19.1 through v22 model iterations
- vault audit skills: All 16 audit skills upgraded to v2.1 with content length checks;
content-length-spec.yamlcreated as shared config - rusty-bloomnet: 34 sessions of continued development and refinement
So What (Why Should You Care)
The taxonomy engine is the missing link between raw job postings and intelligent scoring. Until now, J-Score weighted every role the same way: a data analyst and a machine learning engineer got identical feature importance. With BLS/O*NET role families baked into the classifier at 670 tests, adaptive weights per family become possible, which should push interview conversion rates up without changing the application volume.
The internal audit pipeline v2 spec is equally consequential. Moving from a single-channel scrape-and-score loop to a 4-channel agentic architecture means the audit system can finally cross-reference sources against each other, catching the attribution and false-positive problems that caused six major incidents over the past six weeks. The Layer 6.5 time repair gate is the first hard quality gate in the pipeline that rejects bad data instead of patching it downstream.
Upgrading all 16 vault audit skills to enforce content length checks closes the last major gap in automated wiki quality. Without minimum length enforcement, audit passes were silently approving stub entries that looked structurally correct but contained no real substance.
What’s Next
- Wire adaptive J-Score weights per BLS role family and run A/B comparison against flat weights on the next application batch
- Build the Kaggle JD dataset pipeline (6 build scripts) to complete the taxonomy engine data layer
- Execute the internal audit pipeline v2 spec: stand up the 4-channel agentic crawl and validate against the existing single-channel baseline
- Monitor Layer 6.5 time repair gate rejection rates across the next full pipeline run to calibrate the 1% tolerance threshold
- Run the refreshed vault audit skills end-to-end and triage any new content-length failures surfaced by v2.1
- Continue rusty-dakka wiki integration toward full vault search and rendering parity with Obsidian
Log
Session 1: rusty-dakka (78 sessions, ~1.7MB)
- Wiki system improvements: indexing, search, rendering
- Integration with vault content
Session 2: Jobs Apply (86 sessions, ~3.4MB)
- Taxonomy classification engine: BLS/O*NET role classifier, 670 tests
- Node.js version pinning (>=20 <24) for Vercel build compatibility
- DOM snapshots in error paths + auto-provision email alias on signup
- Taxonomy integrated into AI build chain
Session 3: rusty-bloomnet (34 sessions, ~1.7MB)
- Continued development and refinement
Session 4: internal audit pipeline (21 sessions, ~1MB)
- Pipeline v2 spec: agentic crawl integration + 4-channel architecture
- Layer 6.5 time repair gate: hard gate for placeholder times (1% tolerance)
- Time repair gate wired into full pipeline between L6 and L7
Session 5: Vault Audit Refresh (49 main sessions, ~52MB)
- All 16 audit skills updated to v2.1 with content length checks
- content-length-spec.yaml created
- voice/tone overhaul baseline snapshot
- Compliance gaps closed: ADRs, sunset projects, topics, research
Session 6: Oil (2 sessions)
- CHANGELOG and memory updates for v19.1-v22