mirror of
https://github.com/ModernRelay/omnigraph.git
synced 2026-06-09 01:35:18 +02:00
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) <noreply@anthropic.com>
This commit is contained in:
parent
c221e67e1b
commit
d8451c3d33
1 changed files with 2 additions and 2 deletions
|
|
@ -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 |
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue