Styxis
Company
Knowledge

Which department reviewed the source record used by a public-service AI answer?

Public-service guidance needs a route to the source and responsible institution as well as a generated answer.

An answer may still leave the user stranded

A public-service AI explanation does not finish the task if the user cannot reach the relevant form or institution. A moved or archived source needs another confirmation route. Truthound can check required references and states in the knowledge register. It does not verify actual URL reachability, read the answer for factual truth or establish that the resulting service is accessible to every person.

The official account identifies sources and limits

Hong Kong’s 28 October 2026 parliamentary reply describes departmental review of a knowledge base and an AI Assistant. It discusses old links and page changes while saying the government lacks the requested link-percentage statistics. Do not invent that rate to quantify index quality or accessibility. The described operating structure and its evidence limits provide the appropriate starting point for the proposed check.

Give the register a minimum obligation

A proposed register separates source URL, owning department, review date, archive state and service reference. Retain a route to a readable original and the responsible institution. A single current label should not conceal the difference between archived material and operative guidance. The service owner defines which evidence is acceptable, rather than having a validator interpret the authority of government information from its address alone.

Explain the requiredness check narrowly

Truthound Core Python SDK 3.3.4 (open-source SDK, Polars backend) documents NotNullValidator for required source and owner references, with InSetValidator for approved review or archive states. Define null handling and the vocabulary first. A populated URL does not establish that it opens or reaches the necessary form. Actual access testing remains another control, and a valid reference does not establish that its text supports a particular generated answer.

Leave a route when the original is unsuitable

Where a page moved or the guidance scope is uncertain, retain an appropriate institutional route for clarification. Examine whether repeating the AI answer alone provides a useful alternative. This is a proposed service-design condition, not a finding that a particular user was excluded. The owner should be able to explain both review state and the next inquiry route, rather than using the register as the only assurance.

Keep a small existing missing-value check

pandas 3.1.1 (general-purpose DataFrame library with project-owned checks) isna can remain where it already checks required references. Define additional cases explicitly: empty strings and infinity are not basic NA values under the documented defaults. Compare Truthound through contract and correction-route ownership. Neither product reads the source into a truth judgement or guarantees a usable answer for every citizen simply because required metadata is populated.

Preserve the source beside the next action

Choose one guidance entry and examine the explanation linking its source, current service and responsible institution. Hold admission to automated guidance when archive status or source scope cannot be established. Make the next confirmation step understandable to the user. Shared knowledge becomes useful through clear ownership and available grounds for further inquiry, rather than through the size of a register alone.

Conditions

Define source owner, document, review and archive states in an approved knowledge register.

Alternatives

Keep pandas 3.1.1 missing-value checks with explicit additional state definitions.

Limitations

  • Register checks do not establish URL reachability or factual correctness of an AI answer.

Evidence

Event checked
Subject checked
Modified