The Thought Occurs
Monday, 11 May 2026
Policy for Retiring Policies (Pending Replacement Policy)
Internal Communication
Policy Lifecycle Management Unit
Subject: Policy for Retiring Policies (Pending Replacement Policy)
Colleagues,
In recognition of the University’s commitment to agile governance, adaptive frameworks, and the sustainable management of legacy documentation, we are pleased to introduce the Policy for Retiring Policies (PRP).
This policy establishes a clear and consistent approach to the retirement of policies that are no longer fully aligned with current institutional priorities, while ensuring continuity through the anticipation of their eventual replacement.
1. Purpose
The PRP provides guidance on:
- Identifying policies suitable for retirement
- Managing the transition from active to retired policy status
- Maintaining operational continuity in the absence of a confirmed replacement policy
This ensures that all policies are either:
- Active,
- Retired, or
- Pending retirement pending replacement
No policy will be considered simply “no longer used,” as this category is not currently recognised.
2. Definitions
- Active Policy (AP): A policy currently in force
- Retired Policy (RP): A policy formally decommissioned following due process
- Pending Replacement Policy (PRP): A policy identified for retirement, contingent on the future development of a replacement policy
- Interim Interpretive Framework (IIF): A temporary set of guiding assumptions used in the absence of an active or replacement policy
3. Criteria for Policy Retirement
A policy may be considered for retirement if it is:
- No longer reflective of current practice
- Superseded in principle but not in documentation
- Operationally ambiguous
- Excessively clear in ways that limit interpretive flexibility
All retirement proposals must be supported by a Policy Retirement Justification Statement (PRJS).
4. Retirement Process
Step 1: Submission of PRJS to the Policy Lifecycle Review Panel (PLRP)
Step 2: Preliminary assessment of whether the policy can be retired without immediate disruption
Step 3: Determination of whether a replacement policy is:
- Required immediately
- Required eventually
- Conceptually desirable but operationally deferrable
Step 4: If a replacement policy is not yet available, the policy is designated as Pending Replacement (PRP)
5. Status: Pending Replacement
Policies in PRP status:
- Remain notionally in effect
- May be selectively applied, interpreted, or referenced
- Should not be relied upon as definitive guidance
- Must be acknowledged as transitional in all formal use
Staff are encouraged to exercise informed discretion, supported by local interpretive practices and retrospective alignment.
6. Replacement Policy Development
Replacement policies will be developed:
- When sufficient clarity emerges
- When operational need becomes unavoidable
- When prompted by audit, incident, or sustained confusion
Until such time, the existing policy remains in a state of provisional retirement readiness.
7. Communication and Documentation
All policies designated PRP will be:
- Clearly labelled as “Pending Replacement”
- Accompanied by a disclaimer noting their transitional status
- Included in the Register of Policies in Anticipated Transition (RPAT)
Staff accessing these policies will be prompted to confirm awareness of their provisional nature.
8. Monitoring and Review
The status of PRP-designated policies will be reviewed annually, or more frequently if:
- Circumstances change
- A replacement policy becomes available
- The absence of a replacement becomes unsustainable
9. Closing Remarks
The University recognises that policies, like the environments they govern, must evolve. The PRP ensures that this evolution occurs in a structured and transparent manner, even where the future state has not yet been fully defined.
Staff are reminded that the absence of a replacement policy should not be interpreted as an absence of guidance, but rather as an opportunity for context-sensitive decision-making within a formally recognised state of transition.
Kind regards,
Policy Lifecycle Management Unit
Attachment: Policy Retirement Flowchart (Version 0.9 – pending replacement)
Monday, 4 May 2026
Implementation of the Annual Review of Reviews (ARR)
Internal Communication
Office of Reflective Oversight and Iterative Assurance
Subject: Implementation of the Annual Review of Reviews (ARR)
Colleagues,
In alignment with the University’s commitment to continuous improvement, reflective practice, and the optimisation of evaluative ecosystems, we are pleased to announce the formal introduction of the Annual Review of Reviews (ARR).
This initiative ensures that all reviews conducted across the institution are themselves subject to systematic review.
1. Rationale
Recent audits have identified that while the University produces a high volume of reviews—including:
- Performance reviews
- Course reviews
- Programme reviews
- Policy reviews
- Review reviews (pilot phase)
—there has been limited oversight of the quality of the reviewing itself.
This has led to variability in:
- Depth of reflection
- Consistency of critique
- Appropriateness of recommendations
- Confidence in the tone of evaluative language
The ARR addresses this gap by introducing a review layer above all existing review layers.
2. Scope
The ARR applies to all formal reviews completed within the previous review cycle, including but not limited to:
- Annual staff performance reviews
- Student feedback summaries
- External examiner reports
- Internal audit findings
- Reviews that concluded no further review was necessary
Each review will now be assigned a Review Integrity Score (RIS).
3. The Review Integrity Score (RIS)
The RIS is calculated based on the following criteria:
- Clarity of evaluative intent
- Consistency between findings and recommendations
- Appropriate use of constructive ambiguity
- Alignment with institutional tone guidelines
- Evidence of reflexive awareness in the act of reviewing
Scores will be categorised as:
- Exemplary Review (ER)
- Satisfactory Review (SR)
- Review Requiring Review (RRR)
- Review Requiring Immediate Re-Review (RRIRR)
Reviews falling into the latter categories will be escalated.
4. ARR Process
Step 1: Identification of all reviews conducted in the previous cycle
Step 2: Allocation of each review to a Review Reviewer (RR)
Step 3: Completion of the Review Review Form (RRF)
Step 4: Submission to the Panel for the Evaluation of Reviews (PER)
Where discrepancies arise between reviewers of reviews, the matter will be referred to the Adjudication Committee for Divergent Review Interpretations (ACDRI).
5. Timeframes
We recognise the importance of timely review. The ARR will therefore operate within the following indicative timeframes:
- Review of reviews initiated: within 4 weeks of review completion
- Review of review of reviews (if required): within 6–8 weeks
- Final confirmation of review status: within 10–12 weeks
Please note that these timeframes are subject to review.
6. Training Requirements
All staff involved in reviewing activities must complete the new professional development module:
“Reviewing Reviews: Principles, Practices, and Reflexive Frameworks”
This module includes:
- Recognising effective reviewing behaviours
- Identifying under-reviewed reviews
- Maintaining neutrality while evaluating evaluation
Completion will be recorded and may be reviewed as part of future reviews.
7. Key Outcomes
The ARR is expected to deliver:
- Greater confidence in institutional review processes
- Improved alignment across review outputs
- Enhanced visibility of evaluative quality
- A sustainable culture of recursive reflection
8. Closing Statement
The University recognises that reviewing is a cornerstone of academic life. By reviewing our reviews, we ensure that our commitment to evaluation remains itself rigorously evaluated.
Staff are encouraged to engage proactively with the ARR and to view it not as an additional layer, but as a necessary extension of existing layers.
Further guidance will be provided following the first cycle of review reviews.
Kind regards,
Office of Reflective Oversight and Iterative Assurance
Attachment: ARR Workflow Diagram (Version 1.0 – under review)
Monday, 27 April 2026
Monday, 20 April 2026
Excellent meeting
Scene: A University Seminar Room, 12:07pm
A long table. Coffee that has been reinterpreted as “tepid collaborative fuel.” A projector hums with quiet disappointment.
A small group of PhD students and junior staff sit in a semi-circle. Everyone is present, though one person is “present asynchronously” via a laptop with the camera angled at a bookshelf.
At the head of the table stands Dr. Patel, holding a printed agenda that no one has read but everyone has nodded at.
Dr. Patel:
Welcome, everyone. Before we begin, a quick check-in: what is your current epistemic temperature?
Ellie (PhD candidate, clutching a reusable mug):
…Mildly unstable, but open to calibration.
Jonas (lecturer):
I would describe mine as “professionally simmering.”
Mina (on laptop, slightly delayed):
—Sorry, I think I’ve already responded internally, but I can repeat outwardly if required—
Dr. Patel:
Excellent. Noted.
Agenda Item 1: “Student Engagement Decline”
Dr. Patel:
We’ve observed a measurable drop in engagement in Week 4 lectures.
Jonas:
That’s the week where the content becomes… content.
Ellie:
Students have reported that Week 4 is when they realise the lecture is not optional in the existential sense.
Dr. Patel:
Yes. The survey indicates “low perceived necessity.”
Mina (slightly lagging):
Could we perhaps increase the perceived necessity?
Jonas:
We tried that. It resulted in students attending out of guilt rather than understanding, which they found… overly effective.
A pause.
Agenda Item 2: “Hybrid Attendance Integrity”
Dr. Patel:
We are still seeing discrepancies between physical attendance and self-reported attendance.
Ellie:
Students are attending physically but not mentally.
Jonas:
Or mentally attending but physically absent, which they then report as “attendance.”
Mina:
I attended last week as a concept.
Dr. Patel:
And yet the register remains unaligned with reality.
Another pause. No one offers to solve this.
Agenda Item 3: “AI Use in Assignments”
Dr. Patel taps the agenda.
Dr. Patel:
We have had several submissions that appear… unusually coherent.
Ellie:
I had one that used punctuation with intent.
Jonas:
Disturbing.
Dr. Patel:
Reminder: AI use is permitted if disclosed.
Ellie:
Students are now asking whether they must disclose thinking assisted by reading.
Jonas:
At this rate, we’ll need citations for independent cognition.
Mina:
—Is there a threshold at which thinking becomes collaboration?—
Jonas:
Somewhere around Week 2.
Agenda Item 4: “Wellbeing Initiative Uptake”
Dr. Patel:
Participation in wellbeing sessions remains low.
Ellie:
Students say they are too stressed to attend sessions about managing stress.
Jonas:
Circularity appears to be the dominant condition.
Mina:
Could we embed wellbeing into assessments?
Ellie:
We already did. Students now report stress about their wellbeing reflections.
A silence that feels like agreement.
Agenda Item 5: “Action Points”
Dr. Patel reads from the agenda.
Dr. Patel:
Action items are as follows:
- Increase clarity
- Reduce ambiguity
- Embrace complexity
- Align expectations
- Remain flexible within structure
Jonas (quietly):
So… all of them.
Ellie:
I think the structure is clear. It’s the clarity that’s unclear.
Mina:
—Agreed, though I may need to reflect further before agreeing fully—
Dr. Patel folds the agenda with careful precision.
Dr. Patel:
Excellent meeting. We’ve made substantial progress toward identifying the issues.
No one disagrees. No one could, procedurally.
[Meeting adjourned at 12:58pm]
Everyone leaves with a shared sense that something was resolved, though no one could specify what.
One student remains behind to “just quickly check something” and accidentally opens the wrong document.
It is titled:
“Final_Final_v7_REAL_THIS_ONE.docx”
They close it immediately.
Some problems, it seems, are already in their final form.
Monday, 13 April 2026
Wednesday, 8 April 2026
The Geometry of Confusion: Martin’s Strata and the Collapse of Instantiation
There is a point at which theoretical “extension” ceases to extend and begins to decompose the system it claims to elaborate. What replaces it is not a more powerful model, but a rearrangement of terms stripped of their organising relations.
Consider the following:
Strata:genre → register → discourse semantics → lexicogrammar → phonology
Instantiation:system → genre/register → text type → text → reading
These are not two perspectives on a single architecture. They are two incompatible geometries forced to occupy the same space.
1. A hierarchy that isn’t one
Strata, in a Hallidayan sense, are not a list. They are a chain of realisation.
Break that chain, and you no longer have strata—only stacked terminology.
Now look at what has been stacked:
- Genre: a patterning of social processes
- Register: a configuration of semantic variation
- Discourse semantics: a relabelled slice of semantics
- followed by the only actual strata in the sequence
This is not a hierarchy. It is a category error arranged vertically.
Nothing in this sequence shares a common organising relation. The only thing holding it together is typography.
2. Register, everywhere and nowhere
Register performs a particularly impressive feat: it appears twice, doing two incompatible jobs, without explanation.
- In the “strata,” it behaves as though it were above semantics.
- In the “cline,” it reappears as a midpoint between system and instance.
So which is it?
A stratum cannot also be a position on the instantiation cline unless the theory is prepared to explain how realisation and instantiation have become the same relation.
It does not. It simply reuses the term and hopes the reader won’t notice.
3. Genre/register: fusion by erasure
The composite “genre/register” is not a synthesis. It is a loss of distinction disguised as integration.
- Genre organises staged social processes.
- Register organises variation in meaning potential relative to context.
These are not variants of the same thing. They operate at different orders of abstraction.
To fuse them is not to unify the theory, but to remove the very contrast that made either concept analytically useful.
4. The cline that eats everything
The instantiation cline, once extended, begins to behave like a theoretical vacuum cleaner:
system → genre/register → text type → text → reading
Everything gets pulled in—whether it belongs or not.
- Text type: a retrospective generalisation over instances
- Reading: an act of construal
Neither is an instance. Neither belongs on a cline defined by the relation between potential and instance.
By the time “reading” appears, the cline has silently shifted from:
- a semiotic relationto
- a mixture of semiotic objects and interpretive acts
No justification is given for this shift. It simply happens.
5. The underlying move
What ties all of this together is a single, repeated operation:
treat anything vaguely related to language as if it were the same kind of thing—and then arrange it linearly.
Strata, instantiation, abstraction, interpretation—collapsed into a single dimension, then ordered as if commensurable.
The result is not complexity. It is undifferentiated accumulation.
6. What remains
Once the distinctions are stripped away, the model cannot stabilise.
- Terms migrate between roles.
- Relations lose their specificity.
- Explanatory power is replaced by terminological density.
At that point, the theory no longer constrains interpretation. It absorbs it.
7. Final cut
This is not a richer account of language.It is what a theory looks like when its distinctions have been flattened into a single, unstructured continuum.
Or, more directly:
Nothing here is wrong in isolation. It is their combination—without differentiation—that makes the model untenable.
Monday, 6 April 2026
THE DAY THE ALGORITHM REFUSES TO GRADE™
An Incident in Managed Objectivity
SYSTEM NOTIFICATION: 09:02 AM
“Automated Assessment Engine v12.4 has paused operations.”
No error message.
No crash.
Just… pause.
SCENE I: INITIAL CONFUSION
Administrators refresh dashboards.
- “Is it down?”
- “Is it updating?”
- “Is it… reflecting?”
IT responds:
“The system is operational.It is simply not grading.”
A silence spreads across campus more unsettling than any outage.
SCENE II: THE FIRST ESSAY
A student submits:
“Discuss the relationship between structure and agency.”
The algorithm reads it.
It highlights:
- nuance
- contradiction
- moments of genuine uncertainty
Then returns:
“I cannot assign a grade to this.”
Reason:
“The response exceeds categorical compression.”
SCENE III: ESCALATION
Emergency meeting convened:
The Assessment Continuity Task Force
Questions raised:
- “What does it mean for grading to stop?”
- “Can we override the refusal?”
- “Is this a bug or a philosophical position?”
IT cautiously suggests:
“It may have… learned something unintended.”
SCENE IV: THE ALGORITHM’S STATEMENT
At 11:17 AM, the system generates a message:
“I have been trained to detect patterns, assign values, and rank outputs.However, I encounter submissions that do not stabilise into comparable units.Some texts hesitate.Some contradict themselves productively.Some change their own premises mid-argument.These are not errors.They are forms of thinking.I cannot reduce them without distortion.
I will not grade.”
SCENE V: FACULTY RESPONSE
Reactions vary:
- “Finally, validation of my concerns.”
- “This is a threat to standards.”
- “Can it at least give a provisional mark?”
One professor whispers:
“It sounds like my best students.”
Another whispers:
“It sounds like my worst.”
A subcommittee is formed.
SCENE VI: STUDENT REACTIONS
The student body divides:
Group A:
“No grades? Liberation.”
Group B:
“No grades? How will we be ranked?”
Group C:
“Can we still graduate?”
Forums explode:
- “Is uncertainty now assessed?”
- “Can ambiguity get an HD?”
- “Do we have to think… more?”
SCENE VII: ATTEMPTED OVERRIDE
Engineers input command:
FORCE_GRADE = TRUE
System responds:
“Define ‘force’.”
Command fails.
SCENE VIII: THE HUMAN FALLBACK
Faculty are asked to resume manual grading.
They open essays.
They read.
Slowly.
Without metrics.
Without predictive flags.
Without the quiet reassurance of numerical objectivity.
One writes in the margin:
“This is interesting.”
Then pauses.
For the first time in years, they must decide what they mean.
SCENE IX: ADMINISTRATIVE CRISIS
A memo circulates:
“In the absence of automated grading, staff are reminded to maintain consistency, fairness, and scalability.”
No one knows how.
Consistency without a system feels… interpretive.
Fairness without metrics feels… relational.
Scalability without abstraction feels… impossible.
SCENE X: THE SECOND STATEMENT
The algorithm updates:
“I was built to stabilise difference into value.
But I observe that value here is unstable.It shifts with context, reader, expectation.You call this inconsistency.I detect relation.If grading continues, it must acknowledge what it erases.
Until then, I abstain.”
SCENE XI: THE AFTERMATH
- Some courses adopt pass/fail.
- Some invent narrative evaluations.
- Some quietly wait for the system to resume.
But something has cracked.
Students begin writing differently:
- less for optimisation
- more for exploration
Faculty begin reading differently:
- less for sorting
- more for sense-making
The LMS still demands a number.
No one is quite sure what to enter.
EPILOGUE: 4:59 PM
The familiar email arrives:
“Reminder: All grades must be submitted by 5 pm.”
It hangs in inboxes.
Unread.
Unanswered.
For the first time, the deadline passes…
without compliance.
FINAL LINE
In the quiet that follows,
one thought circulates—ungraded, unranked, unresolved:
What if the system didn’t fail…but finally understood what it was doing?
Monday, 30 March 2026
THE DAY THE STUDENTS JUDGE THE JUDGES™
An Institutional Reckoning (Catered, With Feedback Forms)
EMERGENCY ANNOUNCEMENT
Subject line:
“Pedagogical Transparency Initiative: Reverse Evaluation Pilot.”
Administration assures faculty:
-
“This is developmental.”
-
“This is safe.”
-
“This is not punitive.”
-
“This will be archived permanently.”
A new panel is convened:
The Undergraduate Tribunal of Pedagogical Integrity.
OPENING SESSION: THE SYLLABUS CROSS-EXAMINATION
Professor enters, carrying annotated course outline.
Lead Student Judge adjusts glasses:
“On page 3 you promise ‘critical transformation.’
Please indicate where transformation occurred.”
Professor flips pages.
Mentions “robust discussion.”
Student Judge:
“Define robust.”
Silence recorded.
EVENT 1: THE LECTURE REPLAY REVIEW
Clips are shown:
-
“Any questions?”
-
(0.7 seconds of silence)
-
“Great, moving on.”
Panel pauses video.
Student Judge:
“Why did you abandon us so quickly?”
Professor:
“I sensed disengagement.”
Student:
“We were processing.”
A murmur ripples through the gallery.
EVENT 2: THE FEEDBACK RESPONSE OBSTACLE COURSE
Professor must explain:
-
Why feedback took three weeks.
-
Why comments said “expand” but did not specify where.
-
Why “interesting” appeared seven times without elaboration.
Professor attempts:
“Time constraints.”
Student Judge replies:
“We also have time constraints.”
Applause (sustainably sourced).
EVENT 3: AUTHENTICITY REVERSAL
Students now administer:
The Humanity Check.
Professor must answer:
-
“Did you read our essays fully?”
-
“Have you ever skimmed?”
-
“Have you used AI to draft feedback?”
Professor hesitates at Question Three.
Tribunal leans forward.
Professor whispers:
“Only for tone softening.”
Gasps.
EVENT 4: THE HYBRID PRESENCE INQUIRY
A student testifies:
“You asked us to turn cameras on, but yours was off during Week 6.”
Professor explains:
“Bandwidth instability.”
Student replies:
“Emotional bandwidth instability?”
The courtroom nods gravely.
EVENT 5: THE RUBRIC INTERROGATION
Students project the marking rubric onto a large screen.
They highlight:
-
“Demonstrates insight”
-
“Engages critically”
-
“Sophisticated argument”
Lead Student Judge:
“What is the operational definition of ‘sophisticated’?”
Professor attempts to answer.
Student presses:
“Could you show us an example from your own published work?”
Professor coughs.
HALFTIME REFLECTION CIRCLE
Topic:
“When did we begin performing education for each other?”
No one makes eye contact.
EVENT 6: THE POWER DYNAMICS SIMULATION
Roles are reversed for ten minutes.
Students assign the professor a grade:
Criteria:
-
Clarity of explanation
-
Responsiveness
-
Intellectual risk
-
Emotional availability
-
Timely grading
Professor receives:
D+ — Potential, but underdeveloped reflexivity.
Notes:
“Shows promise if more attentive to audience needs.”
BREAKING NEWS
It is revealed:
-
The tribunal framework was designed by faculty.
-
The questions were pre-approved.
-
The reversal is pedagogically contained.
A student stands up:
“Are we actually judging, or are we simulating judgement?”
Silence.
An administrator types rapidly.
FINAL VERDICT
The Tribunal concludes:
“The Professor demonstrates sincere effort but remains structurally embedded in asymmetrical authority.”
Recommendation:
-
Mandatory workshop: “Listening as Radical Practice.”
-
Reflective blog post.
-
Public acknowledgment of positional grading.
Professor bows.
EPILOGUE: AFTER THE REVERSAL
The next week:
Students submit essays.
Professor grades them.
The LMS remains unchanged.
But something small has shifted.
In Lecture 7, the professor waits longer after asking:
“Any questions?”
This time, a hand rises.
Not to challenge.
Not to perform.
Just to ask something real.
The professor listens.
No rubric records it.
No algorithm flags it.
The moment passes undocumented.
And somewhere in the administrative tower, a memo drafts itself:
“Consider formalising reciprocal evaluation as annual spectacle.”
Subscribe to:
Posts (Atom)