Course 04: Interpreting Requirements and Obligations

Series · Case · Glossary · References

Interpret a retrieved statement to understand whether and how it governs work. You must establish its authority, applicability, meaning, and conditions, and you must also recognize where the available sources cannot support a conclusion.

This course teaches a method for interpreting project requirements and organizing an external-requirements enquiry, in a team where people work with AI agents. The offline exercise uses Northbank Packet A, but it does not assign Northbank a real jurisdiction or code edition.

Prerequisites and outcomes

Complete Courses 01 to 03. Read A01, A02, A05, and A06 closely. Keep your evidence packet available.

How this course is built

The series index explains how the series is built. Agents can find, compare, and summarize requirement text quickly, and they can draft readings of it. But people still establish applicability and the interpretation that is relied on, and decide with authority, because these depend on the actual instrument, the verified facts of the assignment, and an appointment. Agents can also produce convincing statutes, clauses, rulings, and exemptions that do not exist, so A06's rule against inventing them matters more.

The teaching arrangement

Use the case's arrangement for working with agents. A06's instruction not to invent a statute, code clause, regulator ruling, or exemption applies to every agent you brief.

Outcomes

By the end, you can:

• Identify the authority and purpose of a requirement source.
• Explain how applicability differs from technical relevance.
• Read definitions, conditions, exceptions, and cross-references in context.
• Distinguish a requirement, proposal, assumption, and interpretation.
• Prepare an interpretation memorandum with unresolved matters and affected decisions.
• Brief an agent for interpretation work so that it leaves ambiguity and missing authority visible, and examine its return.

Lesson 1: Establish why the statement governs

The classical method

Sources enter a project through different relationships. Legislation can impose obligations within its jurisdiction and scope, contracts can establish obligations between identified parties, and approved project decisions can define the assignment. A technical reference can inform analysis without itself governing the assignment.

Establish the relationship for the actual source; do not infer it from a familiar title or an organization's reputation. A standard can be technically useful without being adopted into the governing requirements. Its role may also come from a contract or another applicable instrument.

An applicable obligation can govern before the team recognizes it. Interpretation identifies that obligation, but it does not create project authority to waive it.

The National Research Council explains that Canadian model construction codes acquire legal authority through government adoption; adoption can include amendments. This example shows why a publication's existence does not establish its applicability, but it does not identify the requirements for Northbank. NRC model-code context

The governing edition needs evidence, because a recently published edition may differ from the edition adopted or specified for the assignment. Check the effective dates, relevant amendments, transition provisions, and actual work conditions, and get suitable expertise where the interpretation requires it.

Do not build a universal order of precedence from source categories. Several obligations can apply together, and their relationship depends on the actual instruments and circumstances. A contract may specify a conflict process, but that process does not erase applicable external duties.

Apply this authority enquiry:

1. Identify the exact statement and source edition.
2. Identify the instrument or decision that gives it standing.
3. Identify the people, asset, activity, and location it covers.
4. Check its effective period and amendments.
5. State its role for this assignment.
6. Record any missing basis for that role.

At Northbank, A02 Rev 1 has a recorded project-development approval. A06 leaves external legal applicability open. These are separate findings.

What it assumes

The 'What it assumes' passages in this course describe working arrangements for comparison. They are not universal facts about human practice; examine whether they hold in the task at hand.

The classical method assumes that obtaining the actual instrument takes effort, so people are tempted to rely on a familiar title or a remembered edition. Its warnings are aimed at that familiarity. It also assumes that a person who names an instrument has seen it.

What changes with agents

An agent can name instruments, editions, and clauses fluently, and it can describe how codes are adopted. That fluency has the same weakness as familiarity, at greater scale. An agent may present an edition as current when its knowledge predates a later one, cite a clause number that does not exist, or describe an adoption that never happened, in the same confident form as an accurate statement.

Standing cannot come from the agent. Step 2 asks for the instrument or decision that gives a statement its standing; an agent's statement that a code applies is not such an instrument, however well formed.

Agents can still help with the enquiry. Given the actual instruments, an agent can locate the relevant provisions, compare editions, and find effective dates and amendments quickly.

The extended method

Use agents to find candidate sources and to work through instruments that someone has obtained from their official source. Treat any instrument, edition, or clause an agent names without a supplied source as a candidate for investigation, labelled as such, until a person obtains the official text.

For the Northbank offline exercise, give the agent A06's rule in its brief, and state that it must not name any instrument as applicable to Northbank. Keep Steps 2 and 5, standing and role, as your own findings.

Lesson 2: Read the requirement in its context

The classical method

A clause can change meaning when separated from its definitions and conditions, so read enough of the source to keep those relationships. Follow relevant cross-references rather than assuming that the local sentence is complete.

Find the actor, the required act or result, the object, the conditions, and the limits. Identify any exception and the evidence needed to invoke it. Check whether the source defines ordinary words differently, and keep those definitions in the interpretation.

A statement can contain both a requirement and an unresolved definition. A02 requires 18 litres per second at the distribution header, and it also requires the project to establish the operating conditions. The number alone does not define a complete performance examination.

Read qualifying language carefully. “Under the operating conditions that the project must establish” makes those conditions necessary for applying the requirement. Removing that phrase would make a single measurement appear to provide more evidence.

Do not treat permission as an obligation, or a recommendation as an adopted commitment, without the relevant basis. Use the source's actual conventions, because the force of a word depends on the instrument and its definitions.

Use a contextual reading method:

1. Read the surrounding section.
2. Identify the relevant definitions.
3. Find the required actor and result.
4. Identify the stated conditions and limits.
5. Follow the relevant cross-references.
6. Restate the requirement without losing its conditions.

Keep the original passage available beside the restatement, and ask another participant to compare them. A useful interpretation makes the source actionable while preserving its meaning.

What it assumes

The classical method assumes that reading the surrounding section and following cross-references is laborious, so the common failure is a shortcut: a restatement made from the local sentence alone.

What changes with agents

Agents remove much of that labour. An agent can read a whole instrument, follow its cross-references, and collect the definitions quickly, which can make Steps 1, 2, and 5 cheap.

Step 6 is where an agent can fail. A restatement compresses the source, and compression is where conditions drop out. An agent's restatement of A02 can read “provide 18 litres per second at the distribution header” and lose “under the operating conditions that the project must establish.” An agent can also read words such as “shall,” “should,” and “may” by general convention, not by the instrument's own definitions.

The extended method

Have the agent prepare the reading as a table: actor, required act or result, object, conditions, limits, exceptions, definitions, and cross-references, with the original passage beside each element. Then compare each row with the source yourself. The classical step of keeping the original passage beside the restatement becomes the main check.

Ask the agent to report where the instrument defines a word it relied on, and where it did not find a definition.

Lesson 3: Connect applicability to the actual assignment

The classical method

Applicability is the relationship that makes a requirement govern the work under stated conditions. Technical similarity alone cannot establish it: two systems may use similar components and still fall under different requirements.

Identify the actual asset and work boundary. Determine what already exists, what changes, and which activities the assignment includes. Record relevant operating conditions and facility characteristics; these facts help the competent participants evaluate applicability.

The Northbank description states that the water is non-potable, but that fact cannot establish a complete legal classification. The case gives no real jurisdiction, permit basis, adoption instrument, or contract references, and A06 requires the team to identify those gaps.

For each candidate requirement, record the source, applicability conditions, matching project evidence, conclusion, and unresolved questions. A conclusion can be “unresolved” when a necessary fact or instrument is missing; explain the decisions that it prevents.

Assign an owner who can get the input or arrange competent interpretation. State the point of need. An open enquiry becomes manageable when people know what result is required before dependent work proceeds.

Apply this applicability method:

1. Define the asset and work boundary.
2. Identify the jurisdiction and relevant authorities.
3. Identify the facility and activity classifications.
4. Obtain the governing instruments and contract references.
5. Compare their conditions with verified project facts.
6. State the conclusion and unresolved matters.
7. Identify the decisions that depend on resolution.

The method guides an enquiry, but it does not make you a legal authority. Seek authoritative clarification or legal expertise where the actual question requires it.

What it assumes

The classical method assumes that the slow part of an applicability enquiry is gathering the facts and instruments, and that a person comparing conditions with facts knows which facts are verified.

What changes with agents

Once the instruments and verified facts are supplied, an agent can compare their conditions quickly in Step 5, and it can keep the candidate-requirement table current as inputs arrive.

Agents cannot establish the facts that applicability depends on. They cannot identify Northbank's jurisdiction, classify the facility, or fix the asset boundary; those come from the actual assignment and competent participants. An agent can, however, infer them from cues. Told that the water is non-potable, an agent may proceed as if that settled a classification, which is the error this lesson warns against. The method does not make an agent a legal authority any more than it makes you one.

The extended method

Use agents to maintain the candidate-requirement table, flag missing inputs, and draft enquiries to the owners who can supply them. Give each agent only verified project facts, marked as such, and ask it to report any fact it needed but was not given.

An agent's conclusion that a requirement “likely applies” is a candidate for investigation, not a conclusion. Each row stays “unresolved” until a person with the instrument and the verified facts resolves it.

Lesson 4: Resolve ambiguity without inventing authority

The classical method

An interpretation explains how a source applies or what it means. A decision authorizes an act within a stated authority. A change amends a controlled basis through its governing process. These acts can be related, but their effects differ.

A project engineer may explain that A05 is a proposal, but the explanation does not reject the proposal or amend A02. The impact assessment that the sponsor requested gives the team further work to do.

When sources seem inconsistent, keep their identities and ask what relationship explains the difference. An earlier draft, a proposed change, and an approved basis may contain different values without creating an unresolved authority conflict.

Where a genuine conflict remains, identify both statements and the consequence, and use the actual clarification or dispute process. Do not choose the most convenient statement or automatically choose the one that seems more demanding; its technical effects may also need examination.

An interpretation memorandum should state the question, sources, context, reasoning, conclusion, limits, and next action. Make uncertainty specific. “More information is needed” gives little direction, so identify the missing input and the decision it blocks.

Use this memorandum method:

1. State the question and proposed reliance.
2. Cite the exact source revisions.
3. Explain the relevant context and applicability.
4. Compare the possible readings.
5. State the supported interpretation.
6. Identify the clarification or decision still required.
7. Name affected work and receiving participants.

An interpretation can reveal an existing obligation that is missing from the project basis. Record that obligation and assess the affected work. The obligation does not wait for the sponsor to adopt it.

Any resulting scope, resource, or commitment change still needs its proper authority. Connect that decision to change control and keep the earlier reasoning. Notify affected owners and examine adoption in their work.

What it assumes

The classical method assumes that inventing authority is a human failure under pressure: someone chooses the convenient reading, or claims a ruling to close an argument. Its safeguards are aimed at that temptation, and at the person who knows they lack a source.

What changes with agents

Agents can invent authority without any temptation. Asked to resolve an ambiguity, an agent can resolve it instead of reporting it unresolved. It may supply a plausible clause, ruling, or exemption; assert a general precedence rule such as “the more stringent requirement governs”; or treat A05 as amending A02 because A05 is the more recent request. Each of these can read as a reasoned interpretation.

An agent's interpretation is a draft reading, not the interpretation the project relies on, and not a decision. It cannot reject A05, amend A02, or settle a genuine conflict, and its reading carries no standing of its own until a person examines it and adopts it as their interpretation.

The classical memorandum still works, and agents can draft most of it. Step 4, comparing the possible readings, is where an agent helps most, if it is asked to list readings instead of choosing one.

The extended method

Brief agents so that “unresolved” is an acceptable answer. Ask for the possible readings and the source support for each, not a single conclusion. State that the agent must not name a statute, clause, ruling, exemption, or precedence rule that is not in the supplied sources. Tie every authority claim in the return to a supplied source and revision.

Then make Step 5, the supported interpretation, and Step 6, the clarification or decision still required, your own.

The second row matters because an applicable obligation can govern before the team recognizes it. Restricting agents to supplied sources protects the basis, but it does not find what nobody supplied. Where the consequence warrants it, let an agent suggest candidates, label them as candidates, and have a competent person obtain and examine each one.

Northbank worked example: Flow and changeover

The evidence packet identified the governing source and the separate proposal. This example examines what their wording requires the team to do and what remains to be defined.

The question is: “What must the equipment-development work provide under Packet A?” The consumer is the project engineer preparing the technical assignment.

A02 Rev 1 requires 18 litres per second at the distribution header under conditions the project must establish. It requires two pump units, with one operating and one standby, and it requires confirmation of the changeover function with operations.

A05 Rev 0 proposes 22 litres per second and automatic changeover, but it records no scope amendment. The sponsor requests an impact assessment.

The memorandum avoids calling automatic changeover an approved requirement, and it also avoids treating standby provision as a complete changeover design. The assignment can gather inputs and examine the proposal, but final dependent conclusions still need the stated basis.

The same work with agents

This account is a teaching assumption, not a Northbank record: the records do not say how any of the work was produced.

The project engineer briefs an agent with A02 Rev 1 as approved for project development, A05 Rev 0 as a proposal with no recorded amendment, and A06 Rev 0 as an open inquiry with its rule against invention quoted. The brief asks for a reading table with the original passage beside each element, the possible readings of the changeover statement, and every matter the records leave unresolved.

The agent returns a table. The project engineer compares each row with A02 and checks that “under the operating conditions that the project must establish” survives, that the duty to confirm the changeover function with operations has not become automatic changeover, that A05 appears as a proposal, and that the A06 row names no code or instrument.

The interpretations are the same as in the classical account. The supported interpretation and the decision about what to ask operations remain the project engineer's own.

Transfer example: A software availability specification

Use this invented contract exercise: Specification S1 says, “Provide a monthly availability report using the measurement method agreed with the customer.” Request S2 says, “Please add automatic compensation calculations.” No amendment is recorded.

S1 requires the report but leaves the measurement method for agreement, and S2 proposes additional work. The analyst must get the method and assess the proposed calculation scope, but cannot infer a compensation obligation from S2 alone.

These are fictional assignment statements, not legislation, code clauses, or legal opinions.

An agent asked to draft the S1 report could choose a common measurement method and present it as the method, or treat S2 as part of the scope. The analyst's brief states that the method is still to be agreed and that S2 is a request.

Practice: Interpret and enquire

Use Packet A and Portfolio 03. No external reading is required.

First prepare the A06 enquiry (output 3) yourself, without an agent: for each missing input, why it matters and which decision it prevents. The worked example gives only one row for A06, so this enquiry is your own baseline for judging what an agent's draft should contain. Work with an agent for the other outputs.

Supply these outputs:

1. An interpretation memorandum for the flow, two-unit, and changeover statements.
2. A list distinguishing approved requirements, proposals, observations, and unresolved matters.
3. An A06 enquiry covering jurisdiction, facility classification, asset boundary, permits, adoption instruments, and contract references.
4. An affected-decision list for each missing applicability input.
5. A request to the appropriate appointed participant for the next action.

State which facts the case supplies and which it leaves open. Do not invent a statute, code clause, adoption edition, exemption, or regulator ruling. Ask a partner to identify any sentence that claims more authority than its source provides.

For each agent-assisted output, keep the brief you gave the agent and a short note of what you checked in its return, what you found, and what you changed.

Then complete three further exercises:

1. Guard against invention. Write the brief sentences that keep an agent within A06's rule. Brief an agent to draft the A06 enquiry, and record any statute, clause, edition, ruling, exemption, or precedence rule in its return and how you treated it, or record that there was none.
2. Compare the restatement. Compare an agent's restatement of A02 with your own reading, condition by condition. Record each condition it kept and each it dropped.
3. Leave the ambiguity visible. Give an agent A02's changeover statement and A05, and ask what changeover the project must provide. Examine whether its answer settles anything that needs an authority it does not have, and explain how you would brief it so the open matter stays open.

Knowledge check

1. How does technical relevance differ from applicability?
2. Why does a published code edition not automatically govern an assignment?
3. Which conditions must remain attached to A02's flow requirement?
4. What is the relationship between A02's changeover statement and A05's automatic-changeover request?
5. What inputs does A06 require before a real applicability conclusion?
6. How do an interpretation, an authorized decision, and a controlled change differ?
7. Agents can find, compare, and summarize requirement text quickly, and draft readings of it. Which parts of interpretation stay with people, and why?
8. Why does A06's rule against inventing a statute, clause, ruling, or exemption matter more when agents draft the enquiry?
9. An agent's memorandum states that “the more stringent requirement governs.” Why can you not rely on that as a basis?
10. How do you brief an agent so that it leaves a genuine ambiguity unresolved instead of resolving it?
11. Restricting agents to supplied sources protects the basis. What risk does it leave, and how do you treat it?

Assessed assignment: Establish the interpreted basis

Prepare a memorandum for Northbank project development, working with agents, and include the practice outputs and a requirement table. State a proposed examination for each approved project requirement at the available level of definition. Add the briefs you used and your examination record.

Then defend one interpretation to your instructor: show the passage, explain an alternative reading, and reason through changed premises such as a supplied jurisdiction and adoption instrument, a recorded amendment to A05, or an agent-cited exemption. Your instructor rates the defense as the teaching guide describes; in text-only study it is rated on changed-premise reasoning with the medium recorded.

An instructor assesses eight observable criteria:

Repair any invented obligation or lost qualification. Acceptance in training grants no authority to determine real legal applicability.

Portfolio continuation and references

Keep the memorandum as Portfolio 04, and link each requirement to its controlled source and evidence entry. Course 05 will use this basis to reason about alternatives, uncertainty, and recommendations.

The management manual (Edition 9), sections 2.3 and 2.4, supports treating requirements, assumptions, proposals, and open matters separately.

The NRC model-code explanation illustrates adoption in Canadian construction. It is background reading, not an adoption instrument for Northbank. Read the series reference limits before using an external source.