diff --git a/astro.config.mjs b/astro.config.mjs index 620bdd0..44a8f0d 100644 --- a/astro.config.mjs +++ b/astro.config.mjs @@ -92,6 +92,7 @@ export default defineConfig({ { label: 'Showcase', items: [ + { label: 'Tally: Change Impact Cockpit', link: '/showcase/tally/' }, { label: 'Tally: Proof', link: '/showcase/tally/proof/' }, ], }, diff --git a/public/favicon.png b/public/favicon.png deleted file mode 100644 index 0382af5..0000000 Binary files a/public/favicon.png and /dev/null differ diff --git a/public/favicon.svg b/public/favicon.svg index f044172..5b2cbbb 100644 --- a/public/favicon.svg +++ b/public/favicon.svg @@ -1,4 +1,34 @@ - \ No newline at end of file + + diff --git a/src/components/overrides/Footer.astro b/src/components/overrides/Footer.astro index ef10344..6fd2075 100644 --- a/src/components/overrides/Footer.astro +++ b/src/components/overrides/Footer.astro @@ -23,6 +23,7 @@
{productIdentity.hero}
-{productIdentity.supporting}
- -Showcase
++ DataHub knows lineage and schema. Git knows which files change together. + The join sounds trivial: a dbt model is a file. But when a dbt project + lives in a subdirectory, every lookup misses and the join returns zero + rows, silently, with no error. Tally is a + Change Impact Cockpit that resolves the mismatch, joins catalog context + with repository evidence, and attaches a bounded receipt to every claim. +
++ Read the Tally showcase for the five-act + narrative: the silent failure, the mechanism, the evidence that changed + the plan, the verifiable receipt, and the honest evidence boundary. +
+- Tally resolved the dataset to its exact repository-relative path, joined - lineage and code impact, and surfaced three declared evidence gaps. -
-+ Tally resolved the dataset to its exact repository-relative path, joined + lineage and code impact, and surfaced three declared evidence gaps. +
+