Skip to content

v2 Stage 0: Scalpel / toolchain spike - #76

Closed
rahlk wants to merge 1 commit into
feat/level3-dataflow-sdgfrom
feat/v2-stage0-scalpel-spike
Closed

v2 Stage 0: Scalpel / toolchain spike#76
rahlk wants to merge 1 commit into
feat/level3-dataflow-sdgfrom
feat/v2-stage0-scalpel-spike

Conversation

@rahlk

@rahlkrahlk commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Part of #69. Stack base:feat/level3-dataflow-sdg.

Stage 0 — Scalpel / toolchain spike. Verified python-scalpel is viable as the L4 may-alias oracle (SSA + copy/const facts consumed behind a frozen may_alias, type-guided branch, with TypeBasedAliasOracle as automatic fallback; installed + probed on CPython 3.12.13). Decision recorded in .claude/SCHEMA_DECISIONS.md. Docs-only — no product code.

Closes#70.

@rahlk

Copy link
Copy Markdown
ContributorAuthor

Landed on main via the stacked chain's top merge — PR #88 (merge commit d477207, released as v1.0.0). Every commit of this stage is in that history.

@rahlkrahlk closed this Jul 15, 2026
@rahlk
rahlk deleted the feat/v2-stage0-scalpel-spike branch July 15, 2026 00:27
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@rahlk