Back to corpus
proposalexperiment writeup candidatescore 32

Python (rag_plusplus.slice)

1. [Overview](#1-overview) 2. [Architecture](#2-architecture) 3. [Core Concepts](#3-core-concepts) 4. [Graph Kernel Service (Rust)](#4-graph-kernel-service-rust) 5. [RAG++ Slice Client (Python)](#5-rag-slice-client-python) 6. [Slice-Conditioned Retrieval](#6-slice-conditioned-retrieval) 7. [Provenance Chain](#7-provenance-chain) 8. [Production Hardening](#8-production-hardening) 9. [API Reference](#9-api-reference) 10. [Deployment](#10-deployment) 11. [Testing](#11-testing) 12. [Migration Guide](#12-migration-guide

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

> **See Also**: [Production Invariants](./PRODUCTION_INVARIANTS.md) for non-negotiable rules. 1. [Overview](#1-overview) 2. [Architecture](#2-architecture) 3. [Core Concepts](#3-core-concepts) 4. [Graph Kernel Service (Rust)](#4-graph-kernel-service-rust) 5. [RAG++ Slice Client (Python)](#5-rag-slice-client-python) 6. [Slice-Conditioned Retrieval](#6-slice-conditioned-retrieval) 7. [Provenance Chain](#7-provenance-chain) 8. [Production Hardening](#8-production-hardening) 9. [API Reference](#9-api-reference) 10. [Deployment](#10-deployment) 11. [Testing](#11-testing) 12. [Migration Guide](#12-migration-guide) This integration makes `cc-graph-kernel` the **sole authority** for determining what context is allowed to influence meaning in RAG++ retrieval. The core principle is: > Nothing downstream is allowed to read "raw graph neighborhoods" directly. Everything must be mediated by `SliceExport` from the Graph Kernel. | Benefit | Description | |---------|-------------| | **Determinism** | Same anchor + policy → same slice_id → byte-for-byte reproducible results | | **Provenance** | Full chain of custody: query → slice → results → semantic artifacts | | **Admissibility Gating** | Only slice-scoped results can promote to semantic artifacts | | **Replay Capability** | Any retrieval can be replayed by citing (slice_id, query_hash, policy_hash) |

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.