Flow and algorithm

Platform spec article

Flow and algorithm

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

  Parent feature hub

Validation flow

1. Parse Project.proj into ProjectManifest.
2. Classify project type. If Mod, validate optional project.mod keys (maxGeneratorRounds, capabilities, artifactPolicy).
3. Insert node into workspace/project graph; reject invalid Mod dependency topology.
4. For host builds, resolve transitive Mod dependencies and ensure AOT artifacts are available (build or cache hit).

Host compilation flow

1. Build CompilePlan for App/Lib/Test host target.
2. Resolve transitive Mod packages from dependency graph.
3. Load/build mod AOT artifacts (mod.load).
4. Run Collector → Generator → semantic → Analyzer → optional Rewriter per Stage ordering.

Lockfile and materialized dependency roots for mod packages use the same workspace materialization path as ordinary projects.