Core Engine Build Status
Delivery ledger for GamiWays Core, reviewed from the development repository. It distinguishes what is actually delivered from priorities that remain open.
Delivery ledger for GamiWays Core, reviewed from the development repository. It distinguishes what is actually delivered from priorities that remain open.
A working headless runtime with persistent sessions, asynchronous orchestration, bounded context, operational authoring and a public player surface.
Persistent users, scenarios, avatars, sessions, conversations and messages; direct synchronous and SSE turns with interruption-safe persistence.
Post-turn planning, routing proposals, runtime events and guarded decisions without making the avatar reply wait.
Bounded working, episodic and user-fact memory; typed knowledge ingestion, profile-aware pgvector retrieval and deterministic context assembly.
Admin scenario builder, read-oriented console and public web player with scenario discovery, SSE updates and text fallback.
An authenticated external CLI compares model configurations with semantic judging and runtime latency, token and cost reports.
Optional, provider-neutral speech input and output are available without making audio persistence or a single provider mandatory.
Optional Deepgram speech-to-text behind a provider-neutral contract, including cancellation and a hands-free client loop.
Gradium and OpenAI TTS adapters; PCM delivery can begin playback while synthesis continues, with a text-preserving fallback.
Health checks, runtime metrics, bounded traces and safe inspection actions make delivery observable without exposing prompts or secrets.
Make retrieval quality measurable and keep code, contracts and operational boundaries maintainable as the Core evolves.
Six-fixture recall@k/MRR harness, 1536-dimension embeddings, lexical fallback, incremental reindexing and explicit selection ownership.
Legacy compatibility paths were removed; fresh deployment uses the documented PostgreSQL bootstrap and current contracts.
Canonical owners and explicit boundaries were documented while dead code, stale TODOs and unsupported workarounds were removed.
These are open backlog items from the repository, not commitments or a calendar. Their order should be chosen against a concrete scenario.
No standalone engine exists beyond current GM heuristics and scenario-goal handling.
A future path could select canonical, retrieval-backed, constrained or live generation responses and measure the choice.
The repository does not record this real-content validation milestone as complete.
The external-demo packaging milestone remains open in the delivery ledger.
Some actions exist, but a dedicated, auditable recovery milestone has not been closed.