Concepts

Sketches of what could exist.

Short future-state provocations. Each one is a concept, clearly labelled: not a product, not a service on sale, and not a claim that anyone has built it. They are here to be questioned, improved or rejected.

Concept · not a product

The Decision Receipt

Every automated decision about a person arrives with a receipt.

A plain-language record, issued with any decision a model makes or shapes about a person: what was decided, the main reasons, what could change the outcome, how to respond, and a named point of human contact with the authority to look again.

It is the simplest possible expression of what POPIA section 71 asks for: a voice and an explanation. Designed as a receipt, it becomes something people can keep, share with an adviser and use to make representations.

What would it take for your institution to issue one for every automated decision it makes about a customer or citizen?

Concept · not a product

The Institutional Change Log

Institutions version their decision rules the way engineers version code.

A living register of who may decide what, and under which rules, with every change recorded: what changed, when, why and on whose authority. Each automated step links to its human owner and the decision it serves.

Boards, auditors and regulators could read the institution's operating system directly, rather than reconstructing it from minutes and memory after something has gone wrong.

If a regulator asked you tomorrow why a decision rule changed last year, how long would it take to answer?

Concept · not a product

The Living Asset

Every public asset publishes its own service record.

A public, continuously updated account of how a piece of infrastructure is performing as a service: availability, planned and unplanned maintenance, open faults and what is being done about them, written for citizens rather than engineers.

The underlying information layer is designed at project inception and owned by the public authority, so that it survives every contract and every change of administration.

Who owns the information about your infrastructure today, and would it survive the end of the contract that created it?

Concept · not a product

Shariah by Design

Compliance is a property of the workflow, not an audit after it.

Shariah screening and governance rules encoded directly into the workflows that originate, approve and service products, versioned and reviewable, with the Shariah supervisory function holding a defined step in the process rather than reviewing a sample afterwards.

The same pattern applies to any values-based or regulated rule set: make the rule explicit, make it testable, give its guardians a seat inside the process, and keep a record of every change.

Where in your process do your governing principles actually act, and where are they only checked?

Your turn

Have a concept that needs imagining?

Tell us the institution, the problem and the future you would rather have. We read every note.