Skip to content

Define the source-pinned Krad component graph - #5

Draft
keys-i wants to merge 1 commit into
bootstrapfrom
sources
Draft

Define the source-pinned Krad component graph#5
keys-i wants to merge 1 commit into
bootstrapfrom
sources

Conversation

@keys-i

@keys-i keys-i commented Aug 12, 2026

Copy link
Copy Markdown
Owner

Closes #1

Motivation

Establish the smallest auditable package boundary for the researched compiler, utilities, libc, and runtime libraries without vendoring upstream source trees.

Changes

  • create a private Node workspace for packages/*
  • define krad-clang, krad-utils, krad-musl, and krad-libs
  • pin each component to an HTTPS origin, full commit, license, and focused source paths
  • validate metadata and produce deterministic dependency order with missing/cycle failures

Verification

  • all component JavaScript passed node --check
  • the completed stack passed npm test with 3/3 tests
  • the completed stack verified all four exact local research revisions

Risk and rollback

This is metadata and validation only; it does not publish packages or vendor/build upstream code. Roll back by reverting commit 2abfc51.

Stack

Base: bootstrap. The verifier PR targets this branch.

Sign up for free to 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.

Define the source-pinned Krad component graph

1 participant