Beskid-native template engine schema
Platform spec ADR
Beskid-native template engine schema
Spec standingStandard
- Contracts and edge cases Normative MUST/SHOULD rules for template instantiation, updates, yanked packages, and post-actions.
- Decisions record (legacy index) Migration index pointing to per-decision ADR files under adr/.
- Design model `beskid.template.v1` schema, symbols, sources, placeholders, GUIDs, and corelib policy.
- Examples Sample `beskid.template.v1` manifests and first-party `beskid.templates.*` packages.
- FAQ and troubleshooting Common questions about Beskid templates and `beskid new`.
- Flow and algorithm End-to-end lifecycle for install, update check, and instantiate.
- Verification and traceability Tests, CI, and registry checks for template conformance.
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).
Context
Section titled “Context”Foreign template engines would split validation and documentation across ecosystems.
Decision
Section titled “Decision”The platform must use beskid.template.v1 only. Foreign engine schemas are forbidden in spec, CLI, and pckg.
Consequences
Section titled “Consequences”Single parser and validator in tooling; template docs stay in-repo.
Verification anchors
Section titled “Verification anchors”CI grep excluding foreign schema identifiers under compiler/ and platform-spec tooling tree.