Targeted knowledge discovery

A decision depends on information held across organisations and public sources. A name in a search result does not reveal everything each source knows about it.

How this work runs.

The run as one route: which tools get involved, in what order, and where the chain is not mechanised yet.

HELD, FOUND BY NOBODYFOUND AND PAYABLEVerified sourcesConformedrecordsHub recordFindable recordWho may query itThe useracquires itPUBLIC / THIRD-PARTYSOURCECRAWLSCRIBESPINENOT MECHANISED YETCONSUMER REACHES THEDATAHUB DATAQUERY RESULTFORGETHE USER'S OWN STOREEXTERNAL CONTRIBUTORSPINENOT MECHANISED YETSPINENOT MECHANISED YETNOT MECHANISED YET

One run, start to finish. A box with an accent tick is a tool acting and opens its own page; a rounded box is an artefact or a record; a diamond is a decision the work cannot pass without. A dashed line is a hand-off the suite has not mechanised yet.

reads what the other publishes
Nothing is sent. The next tool reads what the one before it has published, at the moment it needs it.
updates the current record
The record is overwritten with what is true now. The old value is replaced, not kept beside it.

What this work delivers.

Relevant evidence brought together around a subject, with a clear distinction between what can be discovered and what the holder allows someone to access.

  1. Define the question

    Start from an organisation, location or activity and the decision the evidence must support.

  2. Resolve the subject

    Use shared identifiers and conformed records to recognise the same subject across sources.

  3. Find the evidence

    Query the connected sources and follow relevant relationships. Public information and restricted information retain their own access conditions.

  4. Access or acquire

    Read what is available. Where a user needs a record in their own system, acquisition is a separate, deliberate action under the holder’s terms.

The Spine example uses a bundled public-data extract. It illustrates discovery; it is not a production service for private-data transactions.

Explore the data example

Which tools, in what capacity.

actuate

Crawl

Verifies the source

actuate

Scribe

Renders the source into records in one shared standard shape

actuate

Spine

Makes the records findable, permissioned and auditable

actuate

Forge

Builds the screen where a user finds the data and takes it into their own store

Put this to work in your context.

Tell us what you need to achieve and what you already have.