AIP-15: Runtime Extension Framework (Expanded)

Abstract#

Defines how safe runtime extensions integrate without bypassing core guarantees.

Motivation#

Extensions are necessary for:

new device bridges,
new tool transports,
specialized enterprise controls,
specialized domain-specific skills, without fragmenting the protocol.

Normative Requirements#

Extensions MUST declare capability and risk impacts.
Extensions MUST NOT bypass policy gate.
Extensions MUST preserve audit and tracing guarantees.
Extensions MUST remain backward compatible or declare breaking changes.

Minimal Extension Interface (Reference)#

An extension MUST declare:

extension_id
version
required capabilities
hook points
schema contracts
security posture

Example manifest:

{
  "schema": "gao.runtime.extension.manifest.v1",
  "extension_id": "ext.device.bluetooth",
  "version": "1.0.0",
  "description": "Adds Bluetooth device bridge capabilities",
  "capabilities_added": [
    "device.bluetooth.scan",
    "device.bluetooth.connect",
    "device.bluetooth.read",
    "device.bluetooth.write"
  ],
  "hook_points": [
    "bridge.register",
    "policy.enrich",
    "toolrouter.route"
  ],
  "risk_profile": {
    "default_tier": "MEDIUM",
    "high_risk_actions": ["device.bluetooth.write"]
  },
  "schemas": {
    "device.bluetooth.scan": "sha256:...",
    "device.bluetooth.write": "sha256:..."
  },
  "signing": {
    "required": true,
    "issuer": "domain",
    "trust_anchor": "Gao Domain key"
  }
}

Hook point semantics:
	•	bridge.register: registers new bridge handlers; MUST still enforce envelope and policy.
	•	policy.enrich: MAY add additional constraints; MUST NOT downgrade risk tier.
	•	toolrouter.route: MAY add routing targets; MUST preserve schema validation and audit span emission.