Verification and traceability

Platform spec article

Verification and traceability

Back to Project manifest contract ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

ADRs (2)

1. 0001-hub-authority Hub authority Accepted

   Hub authority

   Context

   Consumers need one contract.

   Decision

   Hub owns Project.proj normative text.

   Consequences

   Mod/Template on hub.

   Verification anchors

   manifest tests.

   Open full ADR page

2. 0002-mod-and-template-project-types Mod and Template types Accepted

   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.

   Open full ADR page

Articles

• Contracts and edge cases Strict guarantees and failure modes for Mod project manifests. article Standard Reviewed Wed May 20
• Design model Conceptual model for `Project manifest contract` and its subsystem boundaries. article Standard
• Examples Concrete examples for `Project manifest contract` decisions and usage patterns. article Standard Reviewed Wed May 20
• FAQ and troubleshooting Project manifest tooling FAQ. article Standard
• Flow and algorithm Manifest validation and Mod package discovery flow. article Standard Reviewed Wed May 20
• Project link libraries Normative project.link block for Extern library resolution at link time (v0.3). article Standard Reviewed Wed May 20
• Verification and traceability Verification for tooling-side project manifest contracts. article Standard

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKfeature · 5 SpecSection(s) · 0 H2 heading(s)

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).

Related spec docs

• Feature
  Project manifest contract (compiler)

  implements — diagnostic and graph tests

Compiler tests

Topic	Path
Corelib + manifest helpers	compiler/crates/beskid_tests/src/projects/corelib/mod.rs
Mod manifest validation	Compiler-mod test suites + parser unit tests
Pack profile from manifest	beskid_pckg/src/pack.rs tests

Tooling traceability

Tooling rule	Verification
Mod type routing	detect_pack_profile + graph ProjectKind::Mod
Template packageKind	pckg server template integration tests
Readme injection	Pack tests + PackagePublishDocumentationTests
Corelib opt-out forbidden	reject_corelib_opt_out_keys parser tests

Spec maintenance

Manifest vocabulary changes must update: tooling design model, compiler project-manifest feature, Diagnostic code registry, and any template scaffolds under beskid_templates/.

CI

Run cd site/website && bun run verify:trudoc -- --preset ci after MDX edits; compiler cargo test for touched parser/graph modules.