jason.woltje
193479b52d
Mosaic concepts pages now own the adapted content; source/license metadata under docs/reference/concepts. Adds ACT-1 agent-context planning capture, pinned concept test package + preparation utility, foundation observation notes (durability, evidence, federation, onboarding, workflow), and the #1495 consolidation assessment. TOOLS.md updated for the host-dev launcher.
46 lines
2.1 KiB
Markdown
46 lines
2.1 KiB
Markdown
# Agent runtimes and adapter ownership
|
|
|
|
Status: Pi is the reference harness; additional harness support must be established
|
|
through pinned adapter contracts and tests.
|
|
|
|
| Layer | Meaning |
|
|
|---|---|
|
|
| Provider | Model service and its authentication/transport |
|
|
| Model | Selected model and supported settings |
|
|
| Harness/runtime | Program that executes the model/tool loop |
|
|
| Deployment | Host development or managed container execution |
|
|
| Interface/transport | Where a user or authorized service interacts with the execution |
|
|
|
|
Changing a provider is not the same operation as changing the harness or deployment.
|
|
|
|
## Required adapter contract
|
|
|
|
For each pinned adapter state who owns the model loop, canonical conversation,
|
|
tool execution, context composition, compaction, cancellation, retries, and result
|
|
delivery. Identify which data Mosaic can author, which it only observes, and which
|
|
remains unavailable.
|
|
|
|
Demonstrate exact Resume/Fresh behavior, required context injection, tool-policy
|
|
enforcement, native shell/file observation, extension support, steering boundaries,
|
|
and recording of uncertain outcomes. Mark unsupported and untested behavior
|
|
explicitly. A successful startup is only startup evidence.
|
|
|
|
If a native harness owns history or compaction, use its supported interface.
|
|
Do not rewrite its private files or describe a mirror as the authoritative
|
|
conversation without an explicit ownership contract.
|
|
|
|
## Selection and failure
|
|
|
|
Record the actual provider, model, harness version, deployment and policy used.
|
|
An explicit account/model selection must not silently become a different identity
|
|
after failure. Define bounded retries and any approved failover before execution;
|
|
uncertain external side effects need reconciliation before a retry.
|
|
|
|
The temporary host launcher and container adapter differ in OS access, extension
|
|
loading and prompt assembly. Neither name nor tool allowlist alone proves equal
|
|
isolation. Preserve those distinctions in diagnostics and tests.
|
|
|
|
ACT-C07 tests interpretation of a capability matrix. It does not certify an
|
|
adapter. See [prompt composition](system-prompt.md),
|
|
[steering](queue-steering.md), and [adapter contract](../../adapters/README.md).
|