Public-record boundary
The source-of-record hierarchy and retention obligations must be defined by the council, not inferred from this example.
Assembling route context
Loading…
Context for Local government
One public question can cross five departmental worlds.
A resident-facing answer may touch a bylaw, an operational note, a delegation and a date. CGI makes that organisational context explicit before consistency becomes a content problem.
Illustrative scenarioCORE / private beta
A consequential local government decision reaches the next corner while authority, effective time and retained conflict shape the evidence packet.
Static motion alternativeLocal government / context field
01 / The context failure
Relevance is not enough.
Councils publish information through many departments and channels. The page a resident finds first may not be the instrument that governs the answer, and the correct answer may depend on application date.
What retrieval seesTwo relevant sourcesWhat CGI must resolveScope · authority · time
Interactive scenario / illustrative data
Which source should the AI use?
A public channel asks when a permit rule changed. A current service page repeats the old threshold; the adopted instrument contains the revision. Which source applies?
No source selectedRelevance alone cannot settle it.
Choose either source. The evidence path, not visual position, will explain what applies and why.
Conceptual walkthrough using authored example data. Not a customer record, product screenshot or legal determination.
02How CORE assembles it
The organisational state travels with the question.
This is the product logic the scenario activates, not a claim that the workflow is deployed at a named organisation.
- Stage
Infer service and date
Resolve the service domain, public audience, jurisdictional scope and effective date.
- Stage
Retrieve channel and authority
Bring the service page, governing instrument, amendment and relevant delegation into one candidate set.
- Stage
Resolve source hierarchy
Use authority and lineage to distinguish public explanation from the adopted source of record.
- Stage
Answer and flag drift
Hand off the current context and preserve the stale public page as an actionable contradiction.
03Trust before rollout
Three boundaries the pilot must name.
The sector does not supply these answers automatically. The organisation’s accountable people and systems define them.
Privacy boundary
Public and internal workflows require distinct eligible source domains and requester identities.
Service boundary
CORE supplies context to a chosen channel; it is not presented as a citizen-facing chatbot or decision-maker by itself.
Design partnership / Local government
Bring the public answer that changes by department or date.
Start with one question, a bounded source slice and explicit success, access and claim boundaries.
Build with Loriq