July 31 — One week ago, Tally was an empty repository.
Today, it is a working, tested system integration that connects DataHub’s metadata graph to repository evidence from workspace.json.
I have been building Tally independently as a solo project. The goal is simple: help an agent move from “this dataset matters” to “this is the exact code responsible,” while making uncertainty and missing evidence impossible to hide.
In the first seven days, the project progressed from its initial scaffold to a complete path that can:
- Read dataset context and lineage through the official DataHub MCP Server
- Resolve a DataHub dataset to its exact dbt source file at a pinned Git revision
- Join that result with workspace.json repository evidence
- Compare an agent plan with and without the joined context
- Trace every plan change back to supporting evidence
- Write a narrowly scoped enrichment back to DataHub
- Reread the catalog and verify that the intended state became observable
- Render the full story in a judge-facing React cockpit
The integration has been tested against public, pinned dbt corpora in both root-level and nested-project layouts. The nested case matters because it reproduces the original failure that inspired Tally: a plausible zero caused by two systems describing the same file in different coordinate systems.
The current system passes 669 root tests and 152 cockpit tests. The browser suite exercises the experience across Chromium, Firefox, and WebKit, with accessibility, responsive-layout, clean-room, lint, type, and production-build checks included.
I also ran a 13-part adversarial audit program covering:
- acceptance criteria and proof traceability
- contract and invariant enforcement
- independent lineage reconstruction
- GraphQL and MCP parity
- nested-corpus recovery
- clean-clone reproducibility
- causal plan differences
- writeback transaction integrity
- fault injection and degraded states
- golden-package provenance
- cockpit truth rendering
- cross-repository compatibility
- DataHub integration-surface coverage
All 13 audit tracks now pass.
The repository currently records 88 commits and 69 merged pull requests, all authored through this solo build effort. Those numbers are less important than what they produced: one public, reproducible path from DataHub context to exact code, an evidence-backed plan, and an observed writeback receipt.
There is still polish and demo work ahead, but the central technical question is no longer hypothetical. The integration works end to end, its claims are tied to inspectable evidence, and its failure states are treated as product behavior rather than hidden exceptions.
That feels like a good first week.
Log in or sign up for Devpost to join the conversation.