displayName
a5c Unified Core (current) — unified agent loop
agentVersionId
packageRef
loopIteratorPolicy
custom
loopIteratorNotes
a5c's core is modeled as a native compatibility layer for agent loops, not
as a wrapper built on top of Pi or any single backend. It can present the
Pi-compatible serialized tool-use loop while also normalizing Claude Code,
Codex, Gemini, OpenCode, LangGraph/custom graph, and agent-mux style loop
semantics behind the same AgentCoreImpl contract.
contextManagementStrategy
platform-managed
compactionTriggerNotes
a5c owns the compatibility contract for context and compaction metadata at
the platform boundary. Individual backends may use provider-managed,
rolling-summary, server-managed, or user-managed context; a5c maps those
postures into one platform-managed profile so legacy Pi-style definitions
and newer graph/custom-agent definitions remain comparable.
subagentInvokerPolicy
platform-mediated
subagentInvokerNotes
Subagent dispatch is mediated by the a5c platform contract. Pi-style
tool-call handoff, Claude-style subagents, LangGraph subgraphs/supervisors,
and skill-as-tool execution all normalize to platform-mediated child work
without making a5c depend on any one mechanism.
resultSynthesisPolicy
post-processed
resultSynthesisNotes
a5c synthesizes a normalized result envelope from backend-native terminal
messages, graph terminal state, streamed text, tool results, and generated
artifacts. Pi's model-direct final text is a supported profile, not the
base implementation.
stopDetectionStrategy
structured-end-event
transportClientLibrary
a5c-unified-transport
supportedTransportProtocols
parallelToolCallHandling
native
streamingFidelity
full
thinkingChannelHandling
model-dependent
streamingBlocks
effortLevelDelegation
passthrough-to-harness
notes
This node is intentionally the Layer-4 unified contract for a5c. It is
capability-compatible with the legacy Pi wrapper's core definition
(Anthropic/OpenAI transports, tool-use loop, structured end events,
sequential tool handling) while also covering same-layer alternatives that
expose parallel tool calls, graph-defined loops, server-managed loops, or
provider-specific thinking channels. Pi is a compatibility target, not an implementation base. Compatibility is modeled as a native a5c contract; there is no depends_on edge to Pi.