vyre-megakernel
Use this crate through the contract and checked-in example below.
Crate contract
This section is generated by python3 scripts/crate_readmes.py --write from
the crate manifest, release train, ownership registry, and crate-guide metadata.
Purpose
Explore and select legal whole-ProgramGraph fusion schedules under explicit SearchBudget bounds, expose selected modules and canonical ABI to registered target compilers, then emit canonical Artifact and ArtifactEnvelope records without owning admission, execution, or lifecycle policy.
Boundaries
The megakernel-compiler owner maintains this compiler-boundary crate at vyre-megakernel.
Its allowed internal production dependencies are: vyre-foundation, vyre-lower.
Any other normal or build dependency requires an ownership-registry change.
Minimal real example
Run the checked-in behavior from vyre-megakernel/tests/artifact_contract.rs:
CARGO_BUILD_JOBS=1 ./cargo_full test -p vyre-megakernel --test artifact_contract
Features
- Manifest features: None
- Default feature members: None
Errors and unsupported behavior
Invalid program shape, unsupported whole-graph lowering, and artifact construction failures stop before a partial Artifact is emitted.
Testing
Use docs/testing/vyre-megakernel.md for exact commands, Cargo targets, hardware
requirements, evidence outputs, expected skips, and failure semantics.
Release status
vyre-megakernel@0.7.2 is a publishable crate on the current Vyre release train. Publication still requires the release evidence and user-approval gates.
Ownership
docs/CRATE_OWNERSHIP.toml is authoritative for this crate's responsibility
and allowed internal edges. Regenerate docs/CRATE_GRAPH.md and
docs/OWNERSHIP.md after changing that registry.
License
Licensed under either of
- Apache License, Version 2.0, or
- MIT license
at your option. See the workspace LICENSE-APACHE and LICENSE-MIT files.