correx

kami/correx

Fork 0

Commit Graph

Author	SHA1	Message	Date
kami	d69cb12ce9	refactor: decomposition WIP (orchestrator/server/execution-plan) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DhFXmKe4WisSSPf9LrmmTg	2026-07-15 13:17:01 +04:00
kami	15248cae8a	feat(recovery,context): tier-2 intent-holder arbiter + remaining-delta pinning + surfaced signal events - recovery: two-tier repair ladder — owner then arbiter (recovery stage recast as intent-holder, holds initial intent, reconciles cross-file contract disputes) with independent INTENT_ROUTE_BUDGET; RecoveryRoutingTest coverage - context: remaining-delta checklist pinning (RemainingDelta{Pinning,Entry}Test) - surface write-only events (session name, quality signals) into stats/browse - parseToolArguments lenient-Json fallback for bare-key drift - tools: ChildProcess seam	2026-07-11 23:56:52 +04:00
kami	595ec187bc	refactor: rename the router subsystem to Talkie The 'router' name was misleading — it's the always-on conversational front-end (CHAT triage + STEERING into a running workflow), not a routing layer, and it's distinct from InferenceRouter. Rename core:router -> core:talkie, package com.correx.core.router -> com.correx.core.talkie, and RouterFacade/Config/State/ Repository/ContextBuilder/Projector/Reducer/Response -> Talkie*. Config section [router] -> [talkie] (legacy [router] still read as fallback). Persisted wire formats are preserved: ChatTurnRole.ROUTER and the RouterNarrationEvent @SerialName("RouterNarration") stay, so existing event logs still replay. RouterNarrationEvent the class is now TalkieNarrationEvent.	2026-07-03 13:26:00 +04:00

Author

SHA1

Message

Date

kami

d69cb12ce9

refactor: decomposition WIP (orchestrator/server/execution-plan)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DhFXmKe4WisSSPf9LrmmTg

2026-07-15 13:17:01 +04:00

kami

15248cae8a

feat(recovery,context): tier-2 intent-holder arbiter + remaining-delta pinning + surfaced signal events

- recovery: two-tier repair ladder — owner then arbiter (recovery stage recast
  as intent-holder, holds initial intent, reconciles cross-file contract disputes)
  with independent INTENT_ROUTE_BUDGET; RecoveryRoutingTest coverage
- context: remaining-delta checklist pinning (RemainingDelta{Pinning,Entry}Test)
- surface write-only events (session name, quality signals) into stats/browse
- parseToolArguments lenient-Json fallback for bare-key drift
- tools: ChildProcess seam

2026-07-11 23:56:52 +04:00

kami

595ec187bc

refactor: rename the router subsystem to Talkie

The 'router' name was misleading — it's the always-on conversational front-end
(CHAT triage + STEERING into a running workflow), not a routing layer, and it's
distinct from InferenceRouter. Rename core:router -> core:talkie, package
com.correx.core.router -> com.correx.core.talkie, and RouterFacade/Config/State/
Repository/ContextBuilder/Projector/Reducer/Response -> Talkie*. Config section
[router] -> [talkie] (legacy [router] still read as fallback).

Persisted wire formats are preserved: ChatTurnRole.ROUTER and the
RouterNarrationEvent @SerialName("RouterNarration") stay, so existing event
logs still replay. RouterNarrationEvent the class is now TalkieNarrationEvent.

2026-07-03 13:26:00 +04:00

3 Commits