Consumers need one contract.
Examples
Platform spec article
Examples
Spec standingStandard
-
Hub authority
Context
Decision
Hub owns Project.proj normative text.
Consequences
Mod/Template on hub.
Verification anchors
manifest tests.
-
Mod and Template types
Context
Discriminate project kinds.
Decision
May declare type Mod or Template; hosts use Host + corelib.
Consequences
Links to mods/scaffolding.
Verification anchors
project fixtures.
- Contracts and edge cases Strict guarantees and failure modes for Mod project manifests.
- Design model Conceptual model for `Project manifest contract` and its subsystem boundaries.
- Examples Concrete examples for `Project manifest contract` decisions and usage patterns.
- FAQ and troubleshooting Project manifest tooling FAQ.
- Flow and algorithm Manifest validation and Mod package discovery flow.
- Project link libraries Normative project.link block for Extern library resolution at link time (v0.3).
- Verification and traceability Verification for tooling-side project manifest contracts.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
| Section id | Required | Found |
|---|---|---|
what-this-feature-specifies | yes | yes |
implementation-anchors | yes | yes |
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
Illustrative Mod project manifest
Section titled “Illustrative Mod project manifest”project { name = "serialization-mod" version = "0.1.0" root = "Src" type = Mod mod { maxGeneratorRounds = 6 capabilities = [read_project_sources, emit_syntax] }}
dependency "compiler-sdk" { source = registry version = "..."}Mod projects must not declare host target blocks. Discovery is contract-based; scope narrowing is implemented in Collector contracts, not manifest attach fields.
Host app depending on a mod package
Section titled “Host app depending on a mod package”project { name = "demo-app" version = "0.1.0"}
target "main" { kind = App entry = "Main.bd"}
dependency "serialization" { source = registry version = "..."}The compiler auto-loads transitive Mod dependencies (for example serialization-mod referenced by serialization) and runs their contracts during host compilation.
Mod artifact management commands
Section titled “Mod artifact management commands”beskid mod rebuild— clean and rebuild mod artifacts for the active workspace slice.beskid mod clean— remove cached mod artifacts under the object store.
See Compiler Mod SDK and Compiler Mods for contract and host execution details.
Template authoring project
Section titled “Template authoring project”project { name = "beskid-templates-console" version = "0.0.0" type = Template template { shortName = "console" identity = "beskid.templates.console" }}Pack publishes packageKind: template and .beskid/template.json. See Project templates.
Instantiated console app (template output)
Section titled “Instantiated console app (template output)”Template-generated host project (no corelib opt-out; corelib resolved on beskid lock):
project { name = "MyApp" version = "0.1.0" root = "Src"}
target "app" { kind = App entry = "Main.bd"}