#Embedded Inference Architecture

Power treats inference as a bounded operation whose identity and effects can be verified. It does not treat a model name as an execution contract.

#Derive the boundary from first principles

#One core, three surfaces

revision-locked bundle       model-owned graph       API client
          |                         |                     |
    provisioner                 embedded               service
          \                         |                    /
           +----------- shared runtime core -----------+
                                  |
              admission / placement / cancellation
                                  |
                    devices / weights / state
                                  |
                   evidence / canonical receipt
                                  |
                      independent verification

The embedded library and hosted service are entry points into the same contracts, not two model implementations. Artifact provisioning is independent because downloading and installing a reviewed bundle is a different authority from executing it.

#Ownership is explicit

This boundary keeps Power model-neutral. Language, vision, OCR, embedding, and future model crates can share resource and evidence machinery without moving their semantics into a central model switch statement.

#The runtime contracts

#Bounded execution

Admission limits active and queued work. Device admission prevents independent models from overcommitting the same accelerator. Cancellation is checked before admission and remains safe while a request waits or executes.

#Verified weights

Weight descriptors bind tensor ranges to storage identities. Complete and partial mirrors retain that identity across storage tiers. Placement and residency evidence record the actual selected path rather than the preferred path alone.

#Accelerator evidence

Execution receipts can include the concrete device, fallback, fused-batch, or multi-device mesh selected for a declaration-bound execution. Evidence must match the model, runtime device, input digest, and output digest before it can be attached to a receipt.

#Recoverable state

Authenticated sealed-state envelopes bind model and runtime identity to warm state. Recovery policy distinguishes primary and backup sources, authorizes export scopes, detects rollback, and zeroizes sensitive material.

#Private observability

Digest-only receipts and telemetry make execution inspectable without requiring prompt or response content. Opaque renderer paths omit claims they cannot derive instead of fabricating deterministic evidence.

#Execution lifecycle

declare limits and identity
          |
          v
admit model + device capacity
          |
          v
resolve storage + placement
          |
          v
execute reviewed model plan
          |
          v
commit input/output/device evidence
          |
          v
release permits and verify receipt

The detailed design includes tensor batches, residency budgets, partial mirrors, prefetch hints, heterogeneous meshes, sealed state, and tuning evidence. Read the canonical architecture document for the complete APIs, invariants, and validation gates.