Where the real screen comes from
The engineering view on the home page is a simplified redraw of a real screen in the current Living Beta. This page explains where it comes from, what was simplified and which engineering records sit behind it. The original records are in private repositories and not public yet, so you will find checked summaries here, not links.
Living Beta 0.3 · author’s machine, single user
The screen
The screen is “Engineering outcomes → System architecture (incl. API) → Architecture overview”. The author provided the screenshot on . The screen itself states: the scope is a fixed case; the current runtime is not verified, with the last reliable observation on ; the engineering judgements are candidate data, not formal Knowledge.
The home-page version drops version numbers, external model services, the access entry point and detailed network and deployment settings. It keeps only the app service, the two databases, the on-demand maintenance task and two kinds of host data. It does not show the health of any service.
Architectural decision · proposed, adoption not recorded
Where online knowledge is read from
The recorded question is “Where is online business knowledge read from?”. The choice: retire the knowledge SQLite; serve all online business knowledge from OpenSearch and FalkorDB; keep the frozen dataset as an offline basis only; keep beta.db, which stores quotas and feedback. The alternative considered was to keep reading knowledge from SQLite online — the way it worked before.
The decision is recorded as “proposed”: its adoption is known only second-hand, without the original wording, so it was not recorded as final. The home page states this status as it is.
· done in the experiment environment
Retiring the knowledge SQLite
The change log states the purpose: the dataset becomes the offline authority only, and all online business knowledge comes from OpenSearch and FalkorDB. The work removed the knowledge SQLite implementation, configuration, build and mount, kept beta.db, and the online app was restarted and checked without the dataset mounted.
One open item recorded at the time: releasing the two databases is not one atomic operation. The “open item” on the home page refers to it.
· GraphRAG case Beta environment switched
Switching to two databases
The GraphRAG project’s Beta environment switched to the new set of services; the app, OpenSearch and FalkorDB all passed readiness checks, and the old version was stopped but kept for rollback. The log also lists remaining risks, such as having no off-machine backup yet.
Pinned versions
What these summaries are based on
These summaries are based on the GraphRAG project’s change logs LOG-097 and LOG-110 (private repository, pinned commit fc2c6d6) and the same project’s design note on online access to the two databases.