# Issue 1508 Platform Hardening Contract

Issue #1508 originally owned the connector field-mapping write substrate. That
substrate is on main via PR #1644: connector field-mapping rows have
direction-aware identity, validation before SQL, deterministic writer identity,
connector-pack ownership, runtime apply, and legacy direction isolation.

The remaining items discussed during review are platform hardening items. They
do not reopen the INT-06 connector field-mapping substrate contract, but they do
need explicit ownership so they do not remain hidden in issue comments.

## Current Ownership

| Item | Current owner | Status |
|---|---|---|
| ProtectedFlowExecution / source-parameter trust | L0 automation runtime | Protected standard-action flow contexts now carry a protected execution marker. Connector runtime adapters are explicitly prevented from forging that marker. |
| Install-time metadata-name validation | L0 metadata/install validation | Successor hardening. This must be schema-aware and shared across validation rules, flows, standard actions, connector mappings, and future component kinds. |
| Pack-global SortOrder across components | L0 pack install ordering policy | Successor hardening. SortOrder is currently component-local; any pack-global ordering rule must be introduced as a platform-wide policy, not only for connector field mappings. |

## Boundary

#1508 should close on the INT-06 substrate. Future work for metadata-name
validation or pack-global SortOrder must be filed as separate platform issues
with their own acceptance criteria and tests. L1/L2 packs may depend on those
rules after L0 publishes them, but they must not define parallel validation or
ordering semantics.