Connect intent, implementation and evidence.

A useful answer needs a source you can check. AKDB’s project-scoped retrieval connects documented decisions with their project context. The retained demonstration below shows an actual search returning a manually authored decision.

The image is from Product Host 0.6.0-alpha.1 and uses fictional data. It is a historical search demonstration, not a view of the later inspection work or evidence of customer results.

Source review on 6 September 2026 includes comparison of reviewed intended and inspected behavior, with conditions and computed values retained. Outcomes distinguish differences from unknowns when the investigation is incomplete. This is bounded analysis, not proof of universal program equivalence.

AKDB 0.5.0 is the tagged baseline; the newer work belongs to active 0.6 development. Internal server checks and synthetic component tests support their recorded scope, not acceptance of a complete Y-Knowledge service. A working package still has to be qualified for the intended evaluation.

Acceptance checks bind design judgments and implementation judgments to the exact inputs assessed, the delivered source and its verification evidence. A result from another version is not automatically evidence for the current delivery.

Existing decision documents can also be previewed and registered by an authorised human owner, with content and revision checks. Conflicts refuse silent replacement. Registration records the action; it does not grant design approval.

The Product Host presents human-readable outcomes while retaining raw results and operation receipts for inspection. Native workspace work has progressed to visible local owner setup and protected, database-bound access configuration.

These are recorded implementation and local-candidate advances, not just interface plans. Physical-device qualification and an integrated native write service remain open. The direction is shared knowledge that people and AI tools can use, without claiming availability on every device.

Agree one task, permitted sources and the questions to answer. Check source coverage and versions, answer correctness, unresolved questions and reviewer effort. Include setup and ongoing maintenance in the cost comparison, and agree when to stop if the case is unsuitable.

There is no production write access in this proposed evaluation. Data location, model access, retention, responsibilities and timing must be agreed before using real information. A standard delivery duration is not promised.

Complete impact analysis, autonomous gap repair and active third-party integrations are not promised capabilities. Adapter packages and remediation plans remain development work; they do not mean your external accounts are connected.

Native-device work is a separate qualification track, not a finished server product on every device. The decision-registration tests do not establish full enterprise deployment or PostgreSQL concurrency acceptance. Independent customer outcomes and repeatable delivery remain to be established.