Constitution

Podcast 2 — In conversation

Speaker A: I had an interesting conversation this week about why the United Kingdom has no single written constitution. Someone insisted this made Britain somehow less constitutional than other democracies, and I was not sure how to respond.

Speaker B: That is a common misconception. The UK absolutely has a constitution, it is just not codified into a single document. Constitutional arrangements here emerge from statutes like the Human Rights Act, from parliamentary conventions, from judicial decisions, and from centuries of common law. The constitution exists; it simply does not live in one place.

Speaker A: So when people say Britain has an unwritten constitution, they mean it is distributed rather than absent.

Speaker B: Precisely. And some scholars argue that an uncodified constitution is actually more flexible and more responsive to change than a single entrenched document that requires a supermajority to amend. The American constitution is extraordinarily hard to change by design. Whether that is a strength or a weakness depends very much on which change you are discussing.

Speaker A: I also notice constitution used in a completely different context sometimes. Someone at the office said their grandfather had the constitution of an ox. That is the bodily sense, is it not?

Speaker B: Yes, that is the older physical meaning, and it is still very much in everyday use. If someone has a strong constitution, they are naturally hardy, rarely ill, and able to endure harsh conditions or a great deal of food and drink without suffering. You can also speak of a delicate constitution, meaning someone who is constitutionally prone to illness or fragility.

Speaker A: So the word carries two very different lives: the legal and the biological. And yet they both come from the same root idea of fundamental structure.

Speaker B: Exactly. What is your constitution? Whether you are asking about a person or a polity, you are asking: what are the deep structural principles that make this thing what it is? The word is remarkable in its generality.

Speaker A: How does constitution differ from charter? I see the two used near each other sometimes.

Speaker B: A charter is typically a document granted by a higher authority to a lower one: a monarch granting privileges to a city, a government chartering a corporation. It flows downward. A constitution is more self-constituted: it describes how a body has organised itself. The United Nations has a charter; nations have constitutions. The distinction is not absolute, but the connotation of origin matters.

Speaker A: That is helpful. And when we say this company has an unusual constitution, we mean its structure or composition is unusual, not necessarily that it has a formal governing document.

Speaker B: Right. Constitution in the sense of composition or make-up is perfectly natural. The committee resolved to review the constitution of its membership, meaning who was in it and how they were selected. Quite ordinary usage. The word moves comfortably between the grand and the everyday.

Speaker A: I think what strikes me most is the permanence the word implies. A constitution is not just any rule; it is the rule behind the rules.

Speaker B: That is exactly the right intuition. The French phrase, la loi fondamentale, the fundamental law, captures the same idea. A constitution does not just tell you what the rules are. It tells you where rules come from and what makes them legitimate.

Podcast 3 — Prompt engineering

Speaker B: Constitution is a powerful word in software prompts because it names the foundational layer: the rules that govern all other rules. When you use it in a prompt, you signal to the model that you want something principled, structured, and authoritative rather than improvised.

Speaker A: I had not thought of applying it to software design, but I can immediately see how it fits. A data model has a kind of constitution. An API has one. Even a UI pattern library could be described that way.

Speaker B: Exactly right. First prompt, a system constitution for an access control layer:

Speaker B: Design a role-based access control system for a multi-tenant SaaS platform. Implement a system constitution as a JSON configuration that defines the immutable rules: which resource types exist, which actions are permitted per role, and which permissions can never be delegated. Validate every incoming request against the constitution before reaching the business logic layer. Log all constitution violations to an access_violations table with timestamp, user_id, resource, and action.

Speaker B: Using constitution here signals that this JSON configuration is not just a settings file; it is the governing document. Other code obeys it. It cannot be overridden at runtime. That framing shapes how the model structures the code.

Speaker A: And the word violation picks up the constitutional metaphor nicely. Breaking a rule is not just an error; it is a constitutional violation.

Speaker B: Exactly. Second prompt, a PostgreSQL schema built around an organisational constitution:

Speaker B: Build a PostgreSQL database schema for a nonprofit management application. Include a constitution table storing the organisation's governing rules as versioned records with fields: clause_number, clause_title, clause_text, effective_date, and superseded_by. Add a constitution_amendments table tracking proposed changes with proposer_id, proposed_text, vote_date, votes_for, votes_against, and ratified boolean. Create a view showing the current ratified constitution with all active clauses in order.

Speaker B: The schema literally models constitutional governance. Every clause is versioned and auditable. Amendments follow a formal ratification process. This is domain-accurate for any organisation that operates under formal governing documents.

Speaker A: That superseded by column is elegant. It creates a chain of constitutional history in the data.

Speaker B: Third prompt, a UI for viewing and comparing national constitutions:

Speaker B: Build a React constitution viewer component. The left panel shows a tree navigation of articles and sections using data from a constitutions API. The right panel shows the full text of the selected clause with keyword highlighting. Add a split-screen comparison mode that loads two constitutions side by side, aligning equivalent sections where article titles match. Include a search bar that queries across all clauses and highlights matching text in both panels.

Speaker B: The word constitution here does real specification work: the data structure, the navigation metaphor, the comparison feature all follow naturally from what a constitution actually is.

Speaker A: The split-screen comparison is a genuinely useful research tool. I can see legal academics wanting exactly that.

Speaker B: Fourth prompt, an HR system governed by a company constitution:

Speaker B: Build a Node.js HR management API for a cooperative business. The company constitution defines mandatory approval workflows for hiring, redundancy, and pay changes. Store the constitution rules in a constitution_rules table with fields: rule_id, decision_type, quorum_required, approval_roles, and notice_days_required. Before processing any HR action, the API must validate the request against the matching constitution rule and reject it with a descriptive error if the rule is violated.

Speaker A: That is a very practical application. Co-operatives genuinely do operate under formal constitutions that govern employment decisions.

Speaker B: Last prompt, a full governance dashboard application:

Speaker B: Build a full-stack Next.js governance dashboard for a homeowners association. Include a constitution page where the current governing document is displayed clause by clause with version history. Add a meetings section for recording votes and resolutions, each linked to the constitution clause that authorised the decision. Add a complaints workflow that checks whether each complaint falls within the scope of any constitution clause before assigning it to a committee. Use PostgreSQL and Prisma.

Speaker A: Linking every resolution back to the authorising clause is a genuinely professional governance practice. That prompt would produce something a real organisation could use.

Speaker B: And that is the measure of a good prompt: it produces code that maps to a real world need. Constitution as a framing word keeps the whole system oriented around principle and legitimacy, which is exactly what governance software should be.