From d8451c3d33a69cb66a615db515c0956c98152b51 Mon Sep 17 00:00:00 2001 From: Andrew Altshuler Date: Sat, 30 May 2026 10:08:14 +0100 Subject: [PATCH] docs(readme): add header labels to hero tables (#126) Fill the empty second-column header cell in both tables: "What it means" for the AS CODE table, "What it's for" for Core Use Cases. Co-authored-by: Claude Opus 4.8 (1M context) --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 89464da..8ae8af0 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,7 @@ Omnigraph acts as operational state & coordination layer for agents - VPC, On-prem, hybrid deployment - Lance format as storage layer -| AS CODE | | +| AS CODE | What it means | |---|---| | **Schema AS CODE** | Typed `.pg` schemas, planned, applied, enforced | | **Context AS CODE** | Linted queries & agentic nudges, versioned and reusable | @@ -23,7 +23,7 @@ Omnigraph acts as operational state & coordination layer for agents ## Core Use Cases -| Use case | | +| Use case | What it's for | |---|---| | **Company brain** | Org knowledge unified into one queryable graph | | **Context graph** | Decision traces and codified tribal knowledge |