Branch main Interface IPlatformMutationAdapter

Interface: Iplatformmutationadapter

Back to Branch Overview

Field	Value
Branch	main
Source	specs/interfaces/IPlatformMutationAdapter.pseudo.md
Commit	a8bea152e7f9
Synced (UTC)	2026-05-08T05:16:43Z

Visual Context

Interface pages describe adapter boundaries that platform repos implement without changing base semantics.

flowchart LR
  Base["Aeostara contract"] --> Interface["Interface boundary"]
  Interface --> Native["Platform-native module"]
  Native --> Result["Contract result"]
  Result --> Diagnostics["Diagnostics and audit"]

Loading

Reading Checklist

Question	Where to look
What must the adapter provide?	Read purpose and boundary rules.
Which contracts flow through it?	Look for named input/output schemas.
Where can platform behavior vary?	Only behind the boundary, never in base semantics.

---

Source Content

IPlatformMutationAdapter

Purpose

Applies approved JsonMutationOperation and recovery steps after precondition, policy, backup, and verification planning gates.

Contract Rules

• The interface is platform-neutral and specifies boundary behavior only.
• Downstream platform repos provide native implementations.
• All decisions, failures, blocked actions, and safety transitions must emit diagnostic references and audit events.
• Implementations must consume the schemas in specs/contracts/ without changing base semantics.