Back to corpus
proposalexperiment writeup candidatescore 26

Plan IR v1.1 Specification

1. **Policy Hashing**: Replace inline policy configs with pre-computed hash references 2. **Compile-Time Type Checking**: Enforce binding type compatibility during compilation 3. **ForEachAnchor**: Atlas generation via anchor iteration 4. **SelectAnchor**: Single anchor extraction from sets 5. **Evidence Authority Gating**: Prevent lifecycle promotions from simulated evidence 6. **Slice Provenance Chain**: Propagate source_slice_id through downstream bindings

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Version**: 1.1.0 **Status**: Provisional **Effective Date**: 2026-01-01 **Supersedes**: Plan IR v1.0 Plan IR v1.1 extends the base Plan Intermediate Representation with six critical enhancements: 1. **Policy Hashing**: Replace inline policy configs with pre-computed hash references 2. **Compile-Time Type Checking**: Enforce binding type compatibility during compilation 3. **ForEachAnchor**: Atlas generation via anchor iteration 4. **SelectAnchor**: Single anchor extraction from sets 5. **Evidence Authority Gating**: Prevent lifecycle promotions from simulated evidence 6. **Slice Provenance Chain**: Propagate source_slice_id through downstream bindings These changes transform the Plan IR from a narrative description into a **compilable, fingerprintable, replayable, auditable** execution contract. **Problem**: Policy configurations contain floating-point values (e.g., `distance_decay: 0.9`). JSON serialization of floats can produce different representations across platforms, causing non-deterministic plan fingerprints.

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.