The Future Role of Policy Engineers

After this lesson, the reader should understand:

• 01Describe the competencies of a policy engineer.
• 02Locate the role within existing institutional structures.
• 03Identify the professional standards the field still lacks.

Where does the role sit?

Legal, engineering, or a function of its own?

Placed under legal, the role tends to produce documents. Placed under engineering, it tends to produce systems that quietly make policy. The productive placement is adjacent to both, reporting to whoever holds the authority being compiled^[1] — because the defining act of the role is not writing structure, it is forcing the authority holder to answer questions the prose allowed them to avoid. The role has an older history than the title suggests. In the 1980s a team at Imperial College formalised the British Nationality Act 1981 as a logic program^[2], and one of its most cited results was not the program but what writing it exposed: places where the Act was ambiguous, incomplete, or silent — questions about the status of abandoned infants among them — that nobody had noticed while it existed only as prose. Expert-system builders of that era were called knowledge engineers^[3], and the best of them did exactly what this lecture describes. What is new is not the activity but its stakes: then the program advised a person; now the artifact may authorise an agent. The strongest objection is that language models will automate the role before it is established. They already draft decompositions, propose rule structures, and flag inconsistencies, faster than any person. Concede the drafting. The defining act of the role was never drafting; it is accountability for the translation — putting a named person between the source and the artifact who must answer for each choice and who carries the unresolved questions to the authority holder. A model can propose that 'continuous service' is ambiguous. It cannot be the one the institution holds responsible for how the ambiguity was resolved, and it cannot make the authority holder decide. The role's composition will shift toward review, specification, and test design; its core does not automate, because it is an assignment of responsibility rather than a task. The limit is that the profession does not yet exist in the sense that matters. There is no body that certifies competence, no settled standard of care, and no clear answer to who is liable when a compiled artifact causes harm — the engineer, the authority holder who signed, or the vendor whose tooling compiled it. Legislative drafting offices have spent generations building such standards for prose^[4]. Until policy engineering has the equivalent, the role will be defined by whoever employs it, which is a reason for the field to define it first.

• Should policy engineering be a certified profession?
• What liability attaches to a badly compiled artifact?
• What training route produces this competency today?
• If a model drafts the decomposition, what exactly is the policy engineer accountable for?
• Who should be liable when a compiled artifact causes harm — the engineer, the signing authority holder, or the tooling vendor?

No responses yet. Be the first to answer one of the questions above.

Write the job description.

1. 01State the purpose of the role in one sentence.
2. 02List five responsibilities.
3. 03State who the role reports to and why.
4. 04List the competencies you could not currently hire for.
5. 05Mark which responsibilities a model could draft and which require a named person to answer for them.