Skip to content

Manifests: declare the actual execution kind of every capsule #184

Closed as duplicate

Description

@andersalm

Part of #173 (isolation plan).

Home and app manifests say type: wasm with execution web-projection, because elastos/crates/elastos-common/src/manifest.rs:769-777 requires it. Provider manifests say type: microvm, but they run as native processes (the provider entries in components.json are substrate native). The manifests do not state what actually runs.

Done means

  • The manifest validator accepts an honest type for web projections and for native providers.
  • Every first-party manifest states its actual execution.
  • Regression test: the validator rejects a manifest whose type contradicts its execution.

Activity

  1. added this to the 0.7.3 milestone on Oct 1, 2026
  2. andersalm commented on Oct 1, 2026

    @andersalm
    ContributorAuthor

    Merged into #170 so this concern has one place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions