apl-cpex 0.2.1

APL ↔ CPEX runtime bridge — per-hook PluginInvoker implementations.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52

// Location: ./crates/apl-cpex/src/lib.rs
// Copyright 2025
// SPDX-License-Identifier: Apache-2.0
// Authors: Teryl Taylor
//
// apl-cpex — bridge between APL evaluator (`apl-core`) and CPEX runtime
// (`cpex-core`).
//
// `apl-core::PluginInvoker` is string-typed by design (so `apl-core`
// stays free of CPEX deps). The actual typed boundary lives in this
// crate: one `PluginInvoker` implementation per `HookTypeDef`. The
// payload type is locked at the impl level — e.g. [`CmfPluginInvoker`]
// can only dispatch to CMF hooks because every internal call goes
// through `invoke_named::<CmfHook>`, and the compiler enforces that
// the payload is `MessagePayload`.
//
// # v0 simplification — single-view-per-Message
//
// CMF spec §4.2 distinguishes two messaging patterns:
//   - LLM wire format — bundled multi-part Messages (thinking + text +
//     tool_call(s)) — many MessageViews per Message.
//   - Framework/protocol format (MCP, A2A, LangGraph) — single
//     ContentPart per Message — one view per Message.
//
// v0 only handles request-side flows (outbound LLM call from the user,
// outbound MCP tools/call from the agent). Both are single-part, so the
// route → MessageView matching collapses to "one route fires per
// Message." When response-side handling lands, this assumption breaks
// and apl-core's route-matching layer needs to switch from
// routes-as-map to routes-as-list with a `match:` block filtering on
// MessageView attributes. See the APL implementation memory's
// "list-with-matchers" deferred item.

pub mod cmf_invoker;
pub mod delegation_invoker;
pub mod dispatch_plan;
pub mod parallel_safety;
pub mod pdp_router;
pub mod register;
pub mod route_handler;
pub mod session_resolver;
pub mod session_store;
pub mod visitor;

pub use cmf_invoker::CmfPluginInvoker;
pub use delegation_invoker::DelegationPluginInvoker;
pub use dispatch_plan::{DispatchCache, RouteDispatchPlan, RoutePluginEntry};
pub use pdp_router::PdpRouter;
pub use register::{register_apl, AplOptions};
pub use route_handler::{AplRouteHandler, Phase};
pub use session_store::{MemorySessionStore, SessionStore, SessionStoreError, SessionStoreFactory};
pub use visitor::AplConfigVisitor;