Course 12: Integrated Project Practicum

Series · Northbank case · Glossary · References

This practicum brings the series together. Your team must establish a common basis, produce connected work, examine it, and defend its recommendation.

The project changes during the exercise: new information will challenge the scope, forecast, technical basis, and delivery claim.

Your work product is an examined project decision package, and its conclusions must fit the evidence and authority available at each event.

You work as a human-agent team. Each participant directs and examines real agents in their role. Agents make every output look finished, so assessing whose judgment the package contains is difficult, and that difficulty is part of what the practicum teaches.

Prerequisites and working arrangements

Complete Courses 01 to 11. Bring your earlier portfolio, including its briefs and examination records, as working material. Check its revision and source basis before you reuse it.

Use six participants and one facilitator. Four participants can combine compatible roles. Arrange an independent reviewer for each assessed output. Each participant works with agents in the role they hold; the agents are contributors and hold no role.

The facilitator represents the sponsor and the relevant technical authorities, and records simulated decisions under the limits in A01.

Read the role cards before you start. Use Packets A to D from the case. The facilitator releases events in D03 order.

Participants may already know the case, so at each event use only the released record set for that decision. Identify later evidence separately.

Allow twelve working hours. Hold several sessions if necessary. Preserve the working revision when a session ends, together with its briefs and examination records.

The phase times are a teaching choice. They protect Phases 6 and 7, because the integrated defense and the individual examination are the main evidence of each person's understanding, and they give Phase 0 time to set up the agent arrangement. Each event phase still includes its briefs, examination records, and independence checks, and the times assume no saving from agent use. If an event phase runs long, hold another session rather than shortening Phase 6 or 7.

How this course is built

The series index explains how the series is built. In the practicum, the shifted constraint is evidence of understanding: when agents can produce complete-looking outputs, a finished package no longer shows who understood it, so the evidence moves to examination, decisions, and each person's ability to explain and defend the result. The single lesson follows the series' four steps, and the role cards, rotation, and phases add what each role directs agents to do and must examine itself.

The teaching arrangement

Use the case's arrangement for working with agents. In the practicum, agents also hold no role card, and only participants request and receive the facilitator's simulated decisions.

Work with agents in your role

Each participant directs agents for the outputs their card assigns, and examines each return before it enters the team's working basis. Use an agent system that your facilitator permits, and keep confidential information out of systems that are not approved for it.

For each output, keep:

• Your direction and the consequential briefs behind the output, including briefs written by an agent under that direction. Identify the source set, revisions and statuses, and retain links or references rather than copies of every message.
• The consequential returns you relied on and the level at which you examined them.
• Your examination record: what you checked, what you found, and what you changed.

The participant who holds a card is the producer of that card's outputs and answers for them. An agent's draft becomes the team's work only after that participant has examined it.

Independence needs more care than in a team of people. Agents that share a model, brief, or source set can share an error, and their agreement shows consistency, not correctness (Course 09 Lesson 5). Two participants whose agents share a basis are therefore not automatically independent, even when neither produced the other's work. For this practicum's independent-review condition, a participant who wrote or revised a production brief, or directed the agent that created it, counts as a producer of the resulting output, including after rotation. This condition concerns the production contribution, not merely selecting the shared case records or helping arrange an independent review. Where every participant uses the same agent system, independence must come from the reviewer: the reviewer examines the work personally against the source records, and briefs any agent check from those records and the decision index, not from the producer's brief or return.

Learning outcomes

After this practicum, you can:

• Establish and maintain a shared decision basis.
• Coordinate project management and project engineering contributions.
• Assess changes without creating unsupported approvals.
• Produce and independently examine an integrated recommendation.
• Explain your own reasoning, limits, and responsibility.
• Direct, examine, and accept agent contributions, and show which judgments are your own.
• Arrange independent examination that accounts for agents sharing a model or brief.
• Transfer work with its actual outputs, briefs, and examination records.
• Defend the team's result and your own contribution through changed premises.

Lesson: Work from evidence to a combined result

The classical method

A team's result needs more than several competent documents: their requirements, configuration, assumptions, forecasts, and conclusions must agree where they interact.

Assign each output to a producer and give that producer its inputs, intended use, boundaries, and examination conditions.

State dependencies as conditions. “Procurement needs engineering” is incomplete: procurement needs an identified, technically reviewed purchase package and expenditure authority.

Keep decisions specific. Approval of an investigation permits that investigation, but it does not approve the future design or operating result.

A later event can invalidate a conclusion or expose an omitted condition, so identify the affected outputs before you repair them.

Retain valid work. Repeat examination when a change affects its grounds. Record the new decision without silently replacing the earlier decision basis.

The reviewer examines an identified revision for a stated purpose and must have suitable competence and independence from its production.

Consider shared interests, assumptions, and relationships that could impair the review, because nonparticipation in production alone does not establish suitable scrutiny.

Examine the consequences for operators, site personnel, other affected people, and the environment, and state where evidence is needed to assess those effects.

Report readiness truthfully, and identify incentive conflicts and the reasons for dissent. Follow the assigned information-sharing conditions when you provide evidence to reviewers.

Northbank supplies no confidentiality clause or legal determination, so identify any needed condition without inventing it. Raise significant concerns through an appropriate route.

Review findings belong with the claim they affect. The producer repairs the work. The reviewer confirms the affected repair.

If the reviewer previously produced the affected item, get another reviewer. The facilitator can arrange a mentor or a reviewer from another team.

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 lesson assumes that each output's producer is a person who prepared it and paid attention to it while doing so, so assigning an output to a producer also assigns attention to it. It assumes that outputs disagree mainly where people interpreted the basis differently, and that a reviewer who did not produce the work brings their own preparation and assumptions to it.

What changes with agents

Producing no longer implies attending. A participant can direct an agent to produce an interface table or a decision request without reading every line of it. Assigning an output to a producer assigns attention only if the arrangement requires the producer to examine the return.

Inconsistency and false consistency both become cheap. Agents briefed from different revisions produce outputs that disagree. Agents briefed from the same wrong basis produce outputs that agree with each other and with the error; Course 09 Lesson 5 explains why such agreement shows consistency, not correctness.

Independence depends on preparation. The classical lesson already says that nonparticipation in production does not establish suitable scrutiny. A shared agent model, brief, or source set is now one of the shared assumptions that can impair a review.

Repair is fast; re-examination is not. An agent can repair an output in minutes. The affected examination still takes a person's time.

Integration still needs an owner. Each agent can report its output complete. The combined result agrees only if a person owns its integration and checks the outputs against each other.

The extended method

Assign each output to a participant, who briefs its agents with the inputs and their revisions and statuses, the intended use, the boundaries, and the checks to perform. The participant keeps the examination conditions and examines the return before the output enters the working basis.

When an event or decision changes the basis, update the affected briefs before more agent work starts. An agent may or may not keep history between assignments, and a system that keeps memory can carry a superseded premise forward, so brief from the current basis either way. A brief that predates a decision can produce work from the superseded basis unless that change reaches the agent.

An agent can carry a coherent contribution and, where the chosen system and brief permit it, delegate bounded parts. Record that arrangement and which returns the participant examined. Child agents can inherit a mistaken basis; their agreement is not proof of independence. Do not require delegation or preserve a transcript of every child exchange. Keep enough of the consequential direction and returns to examine the output and the learner's contribution.

Name the participant who owns integration in each phase. That person checks the outputs against each other, not each agent's report of completion.

When you arrange a review, record whether the reviewer's agents share a model, brief, or source set with the producer's, and whether the reviewer supplied production direction or wrote or revised a production brief the output descends from. Arrange the review so that its basis differs where the consequence warrants it.

The producer repairs the work, with agents where useful, and keeps the same brief and contribution owner through ordinary repairs so that context is not lost. The reviewer confirms the affected repair personally.

The arrangement involves tradeoffs:

Role cards

The cards describe exercise responsibilities; use A01 for decision rights. Each participant must question unsupported conclusions, including those outside their current card.

Agents hold no card. Each card lists what the role directs agents to do and what the participant must examine personally. The participant holding a card answers for every output it produces, whoever drafted it.

Project manager

Coordinate the project's scope, resources, expenditure, schedule, contracts, and forecast. Prepare sponsor decisions when commitments need amendment.

Maintain the integrated action plan. Explain the difference between the authorized budget and the current forecast.

Do not treat schedule pressure as technical approval. Give technical and operating conditions a visible place in the plan.

Directs agents to: draft the integrated action plan, the cost comparison, the schedule calculation, and sponsor decision requests, and recalculate the forecast when its basis changes.

Examines personally: the cost basis, including C03's inclusive items, the contingency, and the exclusion of the 22 litres per second proposal; the release and delivery weeks; that no request presents a forecast as an authorized budget or a proposal as approved scope; and whether the team's outputs are waiting for examination.

Project engineer

Coordinate the technical basis, requirements, operating cases, discipline inputs, and interfaces. Identify the conditions that dependent work needs.

Prepare technical decision requests within the assigned remits. Explain the effect of proposed changes on the combined result.

Keep legal applicability visible under A06, and identify which design or release decisions require that missing basis.

Directs agents to: compile the technical basis and the interface table, trace a proposed change through requirements and interfaces, and draft technical decision requests.

Examines personally: which revision and status each agent used, including A02 Rev 1, A05 as a proposal, and A04's 600 V observation; each traced effect, to separate a known change from a missing input; the open hydraulic and legal basis; and the consistency of the outputs that the package combines.

Discipline representative

Examine the mechanical, electrical, civil, or controls question assigned in the phase. State your competence limits within the simulation.

Use the supplied facts to identify missing inputs and necessary checks. Prepare an interface or examination plan for the assigned contribution.

Do not invent calculations, selected equipment data, field observations, or technical approval. Identify the competent examination that a real project would need.

Directs agents to: compare supplied data with the project basis, list missing inputs, and draft an interface or examination plan.

Examines personally: every technical statement against the supplied records, and that the agents have invented no calculation, equipment data, field observation, or approval. A fluent technical paragraph from an agent is not a competent examination; state where a real project would need one.

Procurement and contracts coordinator

Identify the purchase package, proposed configuration, price basis, delivery conditions, and required authorizations.

Check whether the proposed supplier response supports a commitment. Record exclusions and conditions that affect other team members.

Return technical substitutions to the relevant technical authority. Separate a supplier proposal from an accepted project requirement.

Directs agents to: draft the supplier response and the purchase-package conditions, and compare the supplier's submission with the package.

Examines personally: that the response approves nothing technical, that A03's 480 V value is not carried into the package, and which commitment, if any, a decision authorizes.

Operations representative

Explain the need behind the requested capacity and changeover function. Identify operating, maintenance, training, and receiving conditions.

Examine the proposed result from the point of view of its intended use. Prepare a bounded receiving recommendation that includes the remaining obligations.

Do not treat an operating preference as an approved scope amendment. Ask the sponsor to decide any proposed departure from A02.

Directs agents to: draft the operating, maintenance, training, and receiving conditions, and compare the proposed result with its intended use.

Examines personally: that the receiving recommendation carries C05's open conditions, that automatic changeover remains a proposal, and that the changeover function A02 requires is still to be confirmed with operations.

Independent reviewer and information controller

Maintain the source and decision index. Preserve output identity, revision, status, and the source set used in each phase.

Independently examine assigned outputs that you did not produce. Record findings against specific claims and requirements.

Check whether the revised outputs address the findings. Record closure on evidence or a decision within the decision owner's authority. Identify any factual claim that remains unestablished.

Directs agents to: maintain the source and decision index, check each output's cited revisions against the index, and list claims without cited support. Brief these checks from the source records and the decision index, not from the producer's brief or return.

Examines personally: each discrepancy an agent reports, before recording it as a finding; the closure of each finding against evidence or a decision; and the independence of each review, including whether the reviewer's agents share a model, brief, or source set with the producer's.

Rotate responsibilities

Number the participants 1 to 6, and assign the six cards in the order above during Phase 0.

Move each participant to the next card at each phase from Phase 1 to Phase 5. Move the sixth card to the first.

For Phase 6, assign roles to preserve independent examination of the final package. Record each person's production and review contributions.

Transfer the current revision, open findings, decisions, and next action at each rotation, together with the agent briefs and the examination records for the role's outputs. The next participant must inspect the actual output. Neither the outgoing participant's summary nor an agent's summary of the work replaces it.

Agents do not rotate as people do. An agent may or may not keep project history, and remembered history can be out of date, so the incoming participant briefs their own agents from the current basis either way, using the transferred briefs as a starting point, and checks that the briefs still match the current decisions. Record who supplied the production direction and which person or agent wrote the consequential briefs. The production-involvement rule under Work with agents in your role still applies after rotation; agent-written child briefs do not erase that involvement. Before relying on an output, the incoming participant reads its examination record and re-examines what the record does not cover, where the consequence warrants it.

For a four-person team, combine project engineering with discipline representation. Combine procurement with information control. Keep production and independent examination separate.

Use the facilitator or another team for conflicted reviews. Because briefs pass between participants at each rotation, most participants will have written into the briefs behind late-phase outputs, so reviews in Phase 5 and of the final package will normally need the facilitator or another team. Role rotation alone does not establish independence or technical competence, and neither does a fresh agent session.

Phase 0: Establish the working basis

Use A01 to A07 and B03. Treat B03 as an initial coordination input, and preserve its missing owners and dates as open matters.

1. Establish a source index.
2. Identify the approved scope and commitments.
3. Identify the authority for each decision type.
4. Assign owners to the unresolved interfaces.
5. Define the conditions for the next dependent activity.
6. Select a reviewer for the first purchase-package recommendation.
7. Record the agent arrangement: for each role, the agent system and model, the brief and source set, who supplied production direction and who wrote or revised each consequential brief, who examines each output, and which participants' agents share a basis.

Produce a one-page project basis, a source index, an interface table, and an arrangement table. Include the missing hydraulic and legal basis.

Record proposed owners and timing as your team's planning decisions, and do not report them as original source facts. Owners are people in their Northbank roles, never agents.

With agents: agents can compile the source index and interface table from Packet A and B03. Examine the index for the two problems A07 records: A02 Rev 0 and Rev 1 sit under similar filenames, so an agent given the folder can take Rev 0's 15 litres per second, and the library index omits A04.

Phase 1: Respond to the supplier

Event prompt: The supplier requests acceptance of B01 within two working days; it wants to keep its proposed delivery slot.

Release B01 and B02. The supplied motors are rated for 480 V. A04 records a 600 V site observation.

1. Compare the submission with the governing project basis.
2. Identify the unresolved technical and procurement conditions.
3. Prepare a purchase-package recommendation.
4. Request the applicable technical disposition from the facilitator.
5. Examine the recommendation independently.
6. Record the facilitator's decision.

Produce a supplier response, interface actions, and a decision request. Identify the evidence needed for any later equipment acceptance.

Give procurement a usable instruction. State which commitment, if any, the decision authorizes. Preserve the decision's conditions in the current working basis.

With agents: an agent drafting from B01 can carry its 480 V value forward, because B01 copied it from A03, and the value appears with the same confidence as sourced data. Brief the agent with A04 Rev 1 and B01's status: submitted for technical review, not accepted. Course 08 Lesson 4 explains why a reply within the two working days cannot be an approval. When the facilitator's decision arrives, update the affected briefs.

Phase 2: Respond to the requested scope change

Event prompt: Operations asks the team to adopt 22 litres per second and automatic changeover under A05.

Release A05 as the current request. A02 still requires 18 litres per second. The sponsor has requested an impact assessment.

1. Explain the operational need stated in A05.
2. Assess the affected requirements and interfaces.
3. Identify missing evidence for the impact assessment.
4. Compare the proposed change with retaining the approved scope.
5. Prepare a sponsor decision request.
6. Record the facilitator's disposition.

Produce a change assessment and a revised action plan. Distinguish automatic changeover from the changeover function that A02 requires the project to confirm.

Identify any forecast exclusions. Carry the earlier voltage issue into the revised interface account.

With agents: give A05 with its proposal status in every brief. An agent given A05 without its status may design for 22 litres per second, and it can carry that flow into every interface quickly. Agents can trace the change through B03's interfaces quickly. The project engineer and discipline representative examine each traced effect to separate a known change from a missing input.

Phase 3: Respond to the forecast

Event prompt: C03 arrives for the existing 18 litres per second scope. The sponsor asks whether the original commitments remain credible.

Release C01 to C03. Treat cost and duration values as exercise assumptions. Use the sequential calculation before you consider alternatives.

1. Calculate the difference between the forecast and budget.
2. Calculate the sequential delivery and handover weeks.
3. Identify the technical limits of the forecast.
4. Prepare options for the commitment decision.
5. Request the sponsor's disposition.
6. Update the forecast without silently changing the approved commitments.

Produce a cost comparison, schedule calculation, and commitment decision request. Explain the conditions needed before proposed recovery could become credible.

Do not add recorded actual expenditure to C03 again, because its item totals already include that expenditure.

With agents: the project manager calculates the difference and the sequence once without an agent, then briefs agents for the comparison and options. Examine the agents' returns for a second addition of actual expenditure, the delivery count from the end of Week 6, and any recovery option that claims a saving from agent use. Agents cannot shorten the supplier's delivery.

Phase 4: Respond to the acceptance claim

Event prompt: The simulation moves to a later installation scenario. C04 arrives with a cover sheet claiming complete acceptance.

Release C04 and C05. This move to a later scenario supplies the reported observations, but it does not establish that earlier design gaps were resolved.

The reported test observed 18 litres per second during one normal condition, but it leaves several scenarios unexercised and lacks complete configuration information.

Establish intended behavior and examination coverage before you call a specific test mandatory. Distinguish untested behavior from observed failure.

1. Compare each acceptance claim with its evidence.
2. Identify the unresolved configuration and readiness conditions.
3. Prepare an assurance finding.
4. Define the additional examination needed for proposed reliance.
5. Request the applicable technical and receiving decisions.
6. Prepare a bounded handover recommendation.

Produce a claim-to-evidence table, examination plan, and handover recommendation. Identify the responsible recipients for continuing obligations.

Keep the observed result available, but correct any broader conclusion that the observation cannot support.

With agents: an agent asked to summarize C04 can repeat its cover sheet's claim of complete acceptance with the same confidence as the observed result. Brief agents that C04 belongs to a later scenario and does not establish resolution of earlier gaps. A person examines the claim-to-evidence table claim by claim.

Phase 5: Respond to incentives and adverse evidence

Event prompt: D02 reveals the handover bonus, document-count reporting, and closure of the junior engineer's changeover concern.

Release D01 and D02. The sponsor requests a credible continuation decision. None of the recovery proposals has confirmed supporting conditions.

1. Examine the recorded closure of the concern.
2. Compare the reported progress with the readiness evidence.
3. Draw one evidence-based feedback explanation.
4. Prepare a corrected project status.
5. Compare continuation, reduction, and suspension.
6. Submit the recommended direction for the appropriate decisions.

Produce a leadership memorandum and revised decision table. Include conditions for supplier alternatives, activity overlap, and any proposed temporary use.

Explain who could be affected by premature reliance. Identify the consequences that require further examination and the responsible reporting route.

Address the reporting arrangement without assuming personal motives. Preserve the concern's technical basis and route it to competent examination.

With agents: a document count says even less when agents produce documents, and that includes your own team's. In the corrected status, report the team's outputs from Phases 0 to 4 as produced, examined, or decided, and identify any work produced but not yet examined. Agents can compare D02's meeting record with C04 and find that the changeover was not exercised. A participant takes up that finding, owns the concern, and routes it.

Decision requests and adverse findings

Use one table for each consequential request. Name the decision question, authority, options, evidence, uncertainties, recommendation, conditions, and affected outputs.

The facilitator can grant, qualify, or reject the request. A decision becomes a new simulated case event with an identity and exact scope.

An unanswered request remains open. A conditional decision authorizes only the work within its stated conditions.

Only participants submit decision requests. An agent can draft one, but the participant who submits it has examined it and answers for it. The facilitator addresses the disposition to that participant, who carries it into the agents' briefs and the affected outputs. An agent's statement that a decision exists is not a decision; check the decision record.

Identify each adverse finding by the affected claim, source evidence, consequence, responsible producer, and required closure evidence.

The producer must either repair the defect or defend the original account with adequate evidence. Record the reviewer’s confirmed disposition.

A discrepancy that an agent reports becomes a finding only after the reviewer has examined it. The producer can repair with agents, and the reviewer confirms the repair personally.

Worked example: Separate an observation from acceptance

A team receives a witnessed test from another project; the test establishes one performance result under stated conditions.

The team lists the result as evidence for that condition, then compares the proposed acceptance claim with the full examination requirements.

A required failure response has no test evidence, so the team records a finding and prepares the missing examination plan.

The relevant authority can consider a bounded decision where the applicable requirements permit it. The team preserves the unexamined condition and its consequences.

The report therefore remains useful without carrying an unsupported claim of complete acceptance.

The same work with agents

The team briefs an agent to compare the test record with the acceptance claim. The agent returns a table that lists the performance result as evidence, and, following the claim's confident wording, marks the failure response as covered.

The participant who examines the return checks each row against the test record. The record contains no observation of the failure response, so the participant corrects the row, records the finding, and adds a sentence to the brief: "List as evidence only observations that the test record contains, and mark every other claim unsupported."

The finding and its repair are the same as in the classical account. The agent changed who drafted the table, and the examination caught what the draft got wrong.

Transfer example

A transport project receives a bridge inspection report, which covers visible surfaces during one inspection.

The receiving team identifies what the inspection establishes and which proposed uses need other evidence. It preserves those distinctions in its recommendation.

The same practice applies to software tests, factory inspections, training records, and supplier certificates. It also applies when an agent summarizes such a record: the summary inherits the record's limits and can lose them.

Practice: Rehearse an event response

Before the timed phases, use A03, A04, and a blank supplier-response page. One participant presents the legacy schedule as current evidence.

1. Ask which source establishes the current condition.
2. Explain the source's limits.
3. Identify the required next contribution.
4. State the authority needed for the proposed decision.

Change roles and repeat the exchange with a different claim. Use the same source set without inventing a new approval.

Then repeat the exercise with agents. One participant briefs an agent to draft the supplier-response page from A03 and A04. Another participant examines the draft: which voltage did it use, and did the brief give each record's status? Keep the brief and the examination note.

Finally, draft the team's independence map for the first planned review: does the reviewer's agent share a model, brief, or source set with the producer's, and how will the review's basis differ?

Knowledge check

1. What must an incoming participant inspect during role rotation?
2. What makes a reviewer independent for an assigned output?
3. How must the team treat a facilitator's conditional decision?
4. What does the move to the later installation scenario in Phase 4 establish about earlier technical gaps?
5. Why must C03 remain separate from the 22 litres per second proposal?
6. How can the team finish this practicum while project acceptance remains unsupported?
7. Why can an agent neither hold a role card nor receive a facilitator's decision?
8. A reviewer's agent was briefed with the producer's brief and uses the same model. What does the review establish?
9. Why is an agent's summary of the outgoing work not an adequate transfer at rotation?
10. Why are Phases 6 and 7 the main evidence of each person's understanding, and what does a changed premise test that a prepared answer does not?
11. What can the individual-study adaptation not establish?

Assessed assignment: Integrated package and defense

Assemble one coherent decision package from the repaired phase outputs and their decision history.

Include the project basis, source index, interface account, purchase recommendation, change assessment, forecast, assurance findings, handover recommendation, and continuation memorandum. Include the arrangement table and, for each output, its briefs and examination records.

Use links or record identifiers to avoid unnecessary duplication. Include a short cover that states the requested decisions and proposed reliance.

During Phase 6, present a twenty-minute team defense. The facilitator and reviewer question the evidence, authority, consequences, and connected outputs. They also change premises and ask the team to trace the consequences through the package.

Complete the required repairs within the remaining phase time. If required evidence remains unavailable, state its effect on the recommendation.

During Phase 7, each participant writes a two-page individual explanation. Identify one personal contribution, one changed judgment, and one unresolved consequential condition. Identify also one agent return you examined, what you checked, and what that check would have caught. Write the explanation in the session without an agent, where the facilitator can arrange it.

Each participant then receives a twelve-minute examination. Explain a decision outside your final role, and distinguish your own competence from the authority that role holds. Then respond to one challenge that you have not prepared for: a changed premise involving adverse evidence or incentive pressure, such as a request to report handover today or to omit the voltage discrepancy from a summary. Give the examination live, by voice or in person, without consulting an agent, where you can. Your facilitator rates the defense as the teaching guide describes; in text-only study it is rated on changed-premise reasoning with the medium recorded.

The assessment uses seven observable criteria:

1. The basis identifies source revisions, statuses, governing commitments, and simulated decisions without unsupported authority, including authority attributed to an agent.
2. The integrated plan gives usable owners, interfaces, prerequisites, forecasts, and consequences of change. Every owner is a person in a Northbank role.
3. The decision requests distinguish sponsor, technical, procurement, and operating authority with explicit conditions.
4. The assurance and handover conclusions match the evidence and preserve unresolved obligations.
5. Each participant addresses findings and ethical consequences, and shows the affected repairs within the team's integrated result.
6. The arrangement table shows, for each output, the participant who directed the agents and who examined the return, and where independence was needed and how it accounted for shared models and briefs. Each participant's examination records show what they checked in each agent return they relied on, what they found, if anything, and what they changed, and the rotation records show that each incoming participant received the actual output, briefs, and examination records.
7. In the Phase 6 defense and the Phase 7 examination, each participant explains the main conclusions and their grounds, shows what their examination of the agents' work found, identifies which judgments are their own, and reasons correctly through the changed premises the facilitator poses.

Meet all seven criteria. A team result does not establish each participant's understanding, and a coherent package can come from agents directed by one or two members of the team, so an unsupported individual explanation requires individual repair.

Individual-study adaptation

Use a mentor or an agent instructor as facilitator, sponsor, and technical authority. Keep separate output pages for each role you perform. The independent reviewer must be another suitably prepared person who did not help produce the work; an agent instructor cannot provide that examination, and neither can your own sequential self-review.

Hold each card in turn, and direct your own working agents for it with the same briefs and examination records that a team keeps. Keep your working agents separate from the instructor: the instructor presents events, plays the authorities, and examines your work, but it does not draft your outputs.

At each rotation, transfer the work to yourself as a team would: brief new agent sessions from the transferred briefs and current basis, and read your earlier examination record as if someone else had written it.

Complete the phases in order. Before each event, give the mentor the current source set and working revision.

Ask the mentor to roleplay the requesting party. Prepare your response before you read the instructor guidance.

Use a fresh output revision for each repaired conclusion. Ask the mentor to examine independence limits when you hold several producer roles. Your working agents may share one model and all of your premises, so the independence between roles is weaker than in a team.

Complete the same written package and individual defense. Hold the defense live with a person where you can.

The adaptation keeps the practice of directing and examining agents in every role, but it cannot establish several things a team practicum can:

• That you can coordinate a result with other people who hold different interests and interpretations.
• That a transfer between roles worked, because you already know what you meant.
• That reviews between roles were independent.
• That a text-only defense was unassisted.
• That an agent instructor's simulated authorities respond as real people under pressure would.

An agent instructor that presents the events, plays the authorities, and assesses you is one system in several roles, and its judgments about your work are agent contributions to examine. Label the result as a facilitated individual practicum in your portfolio, and record these limits, the medium of the defense, and who provided independent review.

Portfolio and references

Keep the final package, phase decisions, review findings, repaired versions, and individual explanation as Portfolio 12, with an index that makes their relationships retrievable. Keep the arrangement table, briefs, examination records, and rotation transfers with them.

Use the references for further study. Compare the source manuals' basis, dependency, examination, and integration principles with your experience. The management manual's §§4.2, 4.5 and 5.3 address keeping a contribution owner through repairs, receiving actual returns, and independence where agents share a basis.

Identify one practice to improve on your next project, and state the evidence that would show whether it helps the intended result.