Proposed specificationSource-located exemplarH1

Functional core and steering queues

Separate transitions from live control.

JOIN POINTtransition_core_with_live_inputRECORD STATUSCandidate · v0.1.0

UML class view

The proposed contract drawn as participant roles, received calls, and numbered dependencies.

Object interactions

The same roles and calls as a class collaboration and a numbered message sequence.

Object interaction diagram for Functional core and steering queues, showing role collaboration and a numbered message sequence — FIG. P06 / OBJECT INTERACTIONS
Open full SVG Download PDF

Pointcut

Where the mechanism applies. All four dimensions belong to the proposed match, not just its vocabulary.

Context: A run accepts steering or queued input while transitions continue.
Trigger: A new steering message or input item is enqueued.
Structure: A transition core plus queued control messages and defined application points.
Effect: The transition consumes or defers steering with explicit ordering semantics.

Protected contract

The obligation that clients, operators, and auditors should be able to rely on.

Requires: Steering messages have identity and a defined queue boundary.
Ensures: Transition state changes only through the core and replayable control inputs.
Invariant: Live input cannot mutate shared state nondeterministically outside the queue.
Violation: Queue overflow, conflict, or replay produces explicit policy outcomes.

Negative control

A mutable global message list without transition semantics is insufficient.

Variation & lifecycle

The hot spot is admitted only where the protected semantics survive.

Permitted variation

In-memory or durable inbox, priority, coalescing, and effect handlers.

Test obligation

Test injection timing, duplicate steering, replay, and conflicting messages.

Evolution question

Did steering evolve from prompt text to durable typed control?

Prompt + code design

An illustrative prompt and a small design sketch for the proposed contract. Names and APIs are invented; this is not a repository excerpt.

PROMPT SKETCH

Keep the transition core pure. Admit steering messages through a queue with stable identity, apply them as explicit inputs, and perform side effects only through declared effect handlers.

CODE DESIGN / PYTHON

def step(state, steering, effect_handler):
    message = steering.pop()
    if message is None:
        return state
    next_state, effects = reduce_transition(state, message)
    for effect in effects:
        effect_handler.request(effect)
    return next_state

Illustrative design sketch. Replayability comes from the input log, not from mutating shared state in place. This example is a teaching aid, not implementation evidence or a conformance claim.

Detection & matching

The frozen rule that retrieves this record, the canonical source exemplar, and the control that should stay unmatched.

Join point: transition_core_with_live_input
Source locator: Barbaste et al., §6.2, p. 15 (Pi, “Functional Core with Steering Queues”); source label
Lexical cue: (?i)\bsteering\b|\beffect\s+handler\b|\bfunctional\s+core\b|\bsteering_queue\bFrozen expression, v0.1.0. A match is a retrieval cue, not a confirmed implementation.
Aliases: None
Canonical exemplar: anomalyco/opencodepackages/core/src/session/inbox.ts:54Support: packages/core/test/session-runner.test.ts:1
Negative control: A mutable global message list without transition semantics is insufficient.

Scope-anchored review. pohe-agent analyze <repo> --pattern P06 anchors the cue to its enclosing declaration and checks a separate operational signature for all four pointcut dimensions. Missing roles and negative-control risks remain visible; a structural match is not E2/E3. Calibration report ↗

Repository files

Up to five public files retrieved by the frozen cue and pinned to the audited commit. A match is a place to inspect, not a confirmed implementation.

01anomalyco/opencodepackages/core/src/session/inbox.ts:54CANONICAL SOURCE 02aaif-goose/goosecrates/goose/src/acp/server_factory.rs:198RETRIEVAL CUE 03agno-agi/agnolibs/agno/agno/os/job_queue.py:2827RETRIEVAL CUE 04bytedance/deer-flowbackend/app/gateway/auth/oidc.py:143RETRIEVAL CUE 05cline/clinesdk/packages/agents/src/agent-runtime.ts:1796RETRIEVAL CUE

Evidence & provenance

Each layer answers a different question. Do not substitute retrieval for review.

Source-located exemplar

A concrete source anchor is available for this proposed record. It is one exemplar, not evidence that all repositories—or every contract field—conform.

Review boundary: this candidate and its specification come from an AI-assisted study. Independent human validation remains open.

ANY-EVIDENCE FAMILY COVERAGE25/36

69.4% of repository families in the frozen panel have at least one current cue, historical cue, or canonical source layer. This is not confirmed prevalence.

Current lexical-cue repositories: 26 / 41

Canonical source anchoranomalyco/opencode 885df74024b6packages/core/src/session/inbox.ts:54

Supporting surfacepackages/core/test/session-runner.test.ts:1

Durable steering/input inbox variants.

Exploratory retrieval cue Regex / v0.1.0

(?i)\bsteering\b|\beffect\s+handler\b|\bfunctional\s+core\b|\bsteering_queue\b

This expression is a discovery instrument only. A match is a retrieval cue—not a confirmed implementation, pointcut match, or contract proof.