GamiWays
05·The Project

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.

Synced from repository2026-10-10
gami-lab/gamiways-core
Delivered foundation · open priorities
The repository records a conversational runtime, optional voice, admin/player surfaces, measured retrieval and contract hardening — 860 commits over 177 days. Next capabilities are a backlog to prioritise, not a calendar commitment.
Ledger viewDelivered foundation · open priorities
11 delivered capabilities
0 recorded workstreams
5 open priorities
Delivery-group breakdown
Delivered conversational runtimeReviewed 10 October 2026
5/5 · 100%
Voice delivery and observabilityReviewed 10 October 2026
3/3 · 100%
Retrieval quality and contract hardeningReviewed 10 October 2026
3/3 · 100%
Documented open prioritiesTo prioritise after the delivered state
0/5 · 0%
GROUP 01Reviewed 10 October 2026

Delivered conversational runtime

A working headless runtime with persistent sessions, asynchronous orchestration, bounded context, operational authoring and a public player surface.

5/5
epics
2.xAvatar, sessions and streaming turnsDone

Persistent users, scenarios, avatars, sessions, conversations and messages; direct synchronous and SSE turns with interruption-safe persistence.

4.xAsynchronous Game MasterDone

Post-turn planning, routing proposals, runtime events and guarded decisions without making the avatar reply wait.

4.2–5.2Memory, knowledge and contextDone

Bounded working, episodic and user-fact memory; typed knowledge ingestion, profile-aware pgvector retrieval and deterministic context assembly.

6.1–7.1Authoring and player applicationsDone

Admin scenario builder, read-oriented console and public web player with scenario discovery, SSE updates and text fallback.

8.6Scripted conversation evaluationDone

An authenticated external CLI compares model configurations with semantic judging and runtime latency, token and cost reports.

GROUP 02Reviewed 10 October 2026

Voice delivery and observability

Optional, provider-neutral speech input and output are available without making audio persistence or a single provider mandatory.

3/3
epics
9.1Speech inputDone

Optional Deepgram speech-to-text behind a provider-neutral contract, including cancellation and a hands-free client loop.

9.2–9.4Text-to-speech and streamed playbackDone

Gradium and OpenAI TTS adapters; PCM delivery can begin playback while synthesis continues, with a text-preserving fallback.

3.1 / 4.3Health, metrics and safe diagnosticsDone

Health checks, runtime metrics, bounded traces and safe inspection actions make delivery observable without exposing prompts or secrets.

GROUP 03Reviewed 10 October 2026

Retrieval quality and contract hardening

Make retrieval quality measurable and keep code, contracts and operational boundaries maintainable as the Core evolves.

3/3
epics
5.1eRetrieval Quality HardeningDone

Six-fixture recall@k/MRR harness, 1536-dimension embeddings, lexical fallback, incremental reindexing and explicit selection ownership.

10.1Clean-slate contract baselineDone

Legacy compatibility paths were removed; fresh deployment uses the documented PostgreSQL bootstrap and current contracts.

11.1–11.2Code and comment auditDone

Canonical owners and explicit boundaries were documented while dead code, stale TODOs and unsupported workarounds were removed.

GROUP 04To prioritise after the delivered state

Documented open priorities

These are open backlog items from the repository, not commitments or a calendar. Their order should be chosen against a concrete scenario.

0/5
epics
5.4Guided Progression EnginePlanned

No standalone engine exists beyond current GM heuristics and scenario-goal handling.

5.6 / 6.4Hybrid response pathPlanned

A future path could select canonical, retrieval-backed, constrained or live generation responses and measure the choice.

6.2AVA scenario validationPlanned

The repository does not record this real-content validation milestone as complete.

6.3Stakeholder-ready prototype packagePlanned

The external-demo packaging milestone remains open in the delivery ledger.

3.3Dedicated replay and recovery toolsPlanned

Some actions exist, but a dedicated, auditable recovery milestone has not been closed.

Editorial note — This page is manually synced from the development repository gami-lab/gamiways-core . It reflects the actual project state as of the portal's last update date.