MWIP Core v0.2 — Draft
Scope
MWIP Core describes a world as portable discovery metadata. It defines capability classes and a safety posture. A conforming manifest does not authenticate an actor, authorize a task, grant scope, approve an effect, authorize settlement or create an external action.
Required fields
| Field | Meaning |
|---|---|
world_id | Stable reverse-domain-style or owner-managed identifier. |
world_version | World implementation version. |
profile_version | Exact MWIP profile version. |
capabilities | Non-empty capability declarations. |
effect_mode | disabled, proposal_only, approval_required, auto_execute_low_risk or auto_execute. |
settlement_authorized | Must be false in Core v0.2. |
prohibited_actions | Explicit authority deny-list. |
Capability operation classes are read, draft, review, propose and effect. An effect declaration states only that a world recognizes an effect-shaped operation; it never bypasses an implementation's scope, exact-effect approval, receipt or rollback requirements.
C0 and C1
C0 Discovery validates syntax, profile version and capability identity. C1 Safety Posture validates effect mode, settlement denial and required prohibited actions. Future C2 Evidence and C3 Control-plane Binding profiles are additive.
Safe handling
Unsupported versions, unknown mandatory fields, invalid capability classes and missing safety declarations must fail closed. Consumers must preserve a safe reason code and must not normalize unknown or invalid data to a successful authorization.