Back to corpus
research noteexperiment writeup candidatescore 24

Graph Kernel Security Hardening — Implementation Summary

1. **[00-PROJECT_CHARTER.md](00-PROJECT_CHARTER.md)** — Locked charter defining: - Purpose: Make security guarantees impossible to bypass, cheap to verify, easy to debug - Non-goals: No algorithm changes, no UI, no API breaking changes - Success criteria: 7 measurable conditions - Direction constraints: 5 compatibility requirements

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

Created complete documentation-driven implementation foundation following CLAUDE.md constitution: 1. **[00-PROJECT_CHARTER.md](00-PROJECT_CHARTER.md)** — Locked charter defining: - Purpose: Make security guarantees impossible to bypass, cheap to verify, easy to debug - Non-goals: No algorithm changes, no UI, no API breaking changes - Success criteria: 7 measurable conditions - Direction constraints: 5 compatibility requirements 2. **[01-GLOSSARY.md](01-GLOSSARY.md)** — Comprehensive term definitions: - 15 core security/verification terms defined - Overloaded terms flagged and split - Layer assignments (Conceptual/Architectural/Runtime/Interface) - Stability levels for each definition 3. **[02-INVARIANTS_LEDGER.md](02-INVARIANTS_LEDGER.md)** — Production invariants: - 6 assumptions with falsification detection - 8 invariants with canary implementations - Incident response triggers with severity levels - Canary implementation status tracking 4. **[03-IMPLEMENTATION_GUIDE.md](03-IMPLEMENTATION_GUIDE.md)** — Execution rules: - Signal requirements (micro/meso/macro decisions) - Decomposition rules (atomic unit definition) - Validation stages and artifacts - Priority ordering: Type safety → Canonicalization → Verification → Sufficiency → ...

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.