Back to corpus
proposalexperiment writeup candidatescore 18
Graph Kernel Deployment Guide
The Graph Kernel is the **admissibility authority** for the semantic system. It defines what evidence is allowed to exist for any operation that mutates the semantic ledger.
Full HTML reader
Read the full artifact
Extracted abstract or opening context
The Graph Kernel is the **admissibility authority** for the semantic system. It defines what evidence is allowed to exist for any operation that mutates the semantic ledger.
**Critical Understanding**: While HTTP arrows point from RAG++ to the kernel, **authority flows the other way**. The kernel is the judge that issues admissibility warrants; RAG++ is the attorney that can only present evidence the judge has allowed.
| Regime | Authority Source | Can Mutate Ledger? | |--------|------------------|-------------------| | **Admissible** (slice mode) | Graph Kernel | Yes - promotions, lexicon mutations, phase advancement | | **Non-Admissible** (global mode) | None | No - read-only notes browsing |
Without a kernel-issued slice and attestation token, retrieval results are **non-admissible by definition** and cannot: - Promote atoms or proposals - Mutate the lexicon - Advance lifecycle phases - Affect the semantic ledger in any way
1. **HMAC Secret**: Generate before deployment 2. **Database**: PostgreSQL with `content_hash` column on `memory_turns` 3. **Supabase URL**: Same database as RAG++
Promotion decision
What has to happen next
Attach run IDs, datasets, metrics, and reproduction commands.
Why this is not always a full paper yet
Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.