# Site

## Pages

- [Page not found](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/404/): That page doesn't exist, or it has moved since you last looked
- [Assessment](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/assessments/): Every piece of graded work in the course, what it is worth, and when it is due.
- [Case Study Portfolio](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/assessments/case-study-portfolio/): A portfolio of three cases, each classified against the situationship failure modes and the four contract types, using the full model's terminology throughout
- [Final Audit: Full Model Application](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/assessments/final-audit/): A capstone audit applying all ten variables from the semester to one case, judged as a whole rather than criterion by criterion
- [Position Paper: Classify a Relationship](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/assessments/position-paper/): Classify one relationship (yours, a friend's, or a plausible composite) against the model's first five variables and defend the classification
- [Glossary and risk disclosures](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/glossary/): The model's variable notation, the two strategies it prices, and the disclosures that apply to using it on a real case.
- [Lectures](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/lectures/): What is covered, week by week, and which topics each lecture draws on.
- [Course Overview: Relationships as a Two-Party System](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/lectures/week-01/): What the model is and isn't, why a two-party framing beats a first-person one, and what a case review actually asks of you
- [Price Discovery: Attraction and the Front-End](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/lectures/week-02/): Attraction as the market's front-end — the signal a party broadcasts before any real information changes hands
- [Recurring Contracts: Interaction Frequency and Reliability](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/lectures/week-03/): Why a relationship is better modelled as a recurring contract than a single transaction, and what reliability adds that attraction can't
- [Dependency Formation: The Real Balance Sheet](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/lectures/week-04/): The five things a relationship actually puts on a party's balance sheet, and why counting only one of them causes most misreadings of "attachment"
- [Object Specificity: Why Substitutes Stop Working](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/lectures/week-05/): What it means for a relationship to become specific to one counterparty, and why that's the point past which "just meet someone else" stops helping
- [Reciprocal Investment: Small-Scale Trust Tests](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/lectures/week-06/): Why trust is built from small, reversible tests rather than declared, and what it means when one party keeps proposing tests the other declines
- [The Commitment Gate: Pricing Exclusivity](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/lectures/week-07/): Exclusivity as a priced option — what each party gives up by taking it, and why the gate is where most cases stall
- [Situationship Case Studies: Three Failure Modes](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/lectures/week-08/): Three named ways a commitment gate fails to close, and how to tell them apart from a case that's simply progressing slowly
- [Contract Design: Date / Exclusive / Official / Investment](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/lectures/week-09/): Four named contract types past the commitment gate, what each one commits each party to, and why picking the wrong one is a design error, not a feelings error
- [Portfolio Monitoring: Behavioral Signals Over Self-Report](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/lectures/week-10/): Why an ongoing position is monitored on behaviour, not on periodic self-report, and which signals are cheap to fake versus costly to fake
- [Risk Disclosure: Stop-Losses and the Black Swan Protocol](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/lectures/week-11/): Setting a stop-loss before you need one, and what a black swan event does to a position that never set one
- [Course Retrospective: Applying the Full Model](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/lectures/week-12/): Assembling framing, attraction, reliability, dependency, specificity, reciprocity, commitment, protocol, monitoring, and risk into one reading of a single case
- [People](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/people/): Who teaches the course, and how to reach them.
- [Idris Fenn](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/people/idris-fenn/): Teaching fellow and former quant. Runs the case reviews and marks the position papers against the model, not against vibes.
- [Marisol Quaye](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/people/marisol-quaye/): Founding convenor. Behavioural economist by training; spent a decade pricing risk before deciding relationships were the harder asset class.
- [Policies and support](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/policies/): The course-wide rules for late work, extensions, academic integrity and getting help.
- [Orientation](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/sessions/01-orientation/): The first case review — naming a real situation in the model's terms before the model has given you any terms to name it with
- [First price check](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/sessions/02-first-price-check/): Applying the front-end/back-end split to last week's cases — what did the first signal actually price?
- [The reliability audit](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/sessions/03-the-reliability-audit/): Turning "they're flaky" or "they're solid" into an actual rate, computed from your case's last five to ten interactions
- [Balance sheet workshop](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/sessions/04-balance-sheet-workshop/): Pricing your case's dependency across all five line items separately, instead of as one number called "how attached I am"
- [The specificity test](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/sessions/05-specificity-test/): Checking whether your case has crossed the line from fungible to specific provision, before you write it up for the position paper
- [Trust test design](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/sessions/06-trust-test-design/): Auditing who initiates the small reversible tests in your case, and who only ever responds to one
- [The commitment memo](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/sessions/07-the-commitment-memo/): Writing down which of the three stalled-gate diagnoses fits your case, and what evidence supports it
- [Situationship clinic](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/sessions/08-situationship-clinic/): Classifying stalled cases in the room against the three named failure modes, and proposing the specific fix each one implies
- [Contract drafting](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/sessions/09-contract-drafting/): Naming which of the four contract types each case is actually operating under, versus which one each party might assume it is
- [Signal versus self-report](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/sessions/10-signal-vs-self-report/): Scoring your case on all seven behavioural signals over the last month, instead of asking how things are going
- [Stress test](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/sessions/11-stress-test/): Naming a stop-loss condition for your case before you need one, and drafting the standing procedure your Black Swan Protocol falls back on
- [Portfolio close-out](https://comp4020-agentic-coding-studio.github.io/comp4020-ass2-Cichlider/sessions/12-portfolio-close-out/): A last full read of your case against every variable from the semester, before writing the final audit