The Overnight Watch: Contradictions and the Attention Brief

The Overnight Watch: Contradictions and the Attention Brief

Two things run while everyone is asleep. Neither of them changes a record. Both of them exist so that a problem reaches a person while it is still small.

---

The nightly contradiction sweep

Institutional memory does not usually go wrong by being empty. It goes wrong by holding two things that cannot both be true, in two places nobody compares. Sera compares them every night.

She looks for the shapes that actually cause trouble:

• Two documents naming different owners for the same thing.
• A meeting decision that conflicts with a standing policy.
• A deadline that moved while the tasks depending on it did not.
• Someone saying a task is complete when nothing evidences it.
• A new decision that contradicts an earlier approved decision.

When she finds a genuine conflict, she files an Unresolved Contradiction with Status Open. Each one names the sources, the people involved, and the smallest decision that would reconcile them. That last part is the useful bit: most contradictions are not a crisis, they are a two-minute conversation with one person that nobody knew to have.

She cannot fix one, on purpose

Sera has no ability to resolve a contradiction. This is structural rather than a rule she follows: the service that runs the sweep can only create rows in that one database, so there is no path through it to edit, archive, or "just correct" an underlying record. The framing of every filing is fixed in code too, so the wording can never drift from "here are two conflicting versions" into a verdict about which is right.

A contradiction someone deliberately dismisses does not come back the next night. The sweep remembers what was already judged.

How to work the list

Once a week is plenty:

1. Open the Unresolved Contradictions with Status Open.
2. For each, read the two sources rather than the summary. The summary is the pointer, not the evidence.
3. Make the smallest reconciling decision it suggests, in the record that should hold it.
4. Close the contradiction, or dismiss it if the conflict is benign.

A list that stays short is the normal state. A list that grows steadily is telling you something real about how decisions are being recorded.

---

The Attention Brief

The other overnight job answers a plainer question: of everything happening, what deserves human attention right now?

The brief gathers candidates by ordinary query, with no model call at all:

• Tasks that are blocked or waiting.
• Tasks that are overdue.
• Open High-severity risks.
• Decisions with nobody accountable to decide them.
• Anything the stale sweep already flagged.

Each candidate is scored for significance, ranked, and then the list is hard-capped. The cap matters more than it sounds: it is written into the code rather than asked of a model, so the brief structurally cannot turn into a wall of everything. An assistant that surfaces fifty items a day is one you learn to ignore, and an ignored warning system is worse than none.

Reading it well

• Read it first, before the queues. It is the only list already ordered by what matters.
• It is a prompt, not a verdict. An item on the brief means "a person should look at this today", not "this is a failure".
• An empty brief is a good day. Sera going quiet because nothing needs attention is the product working. She is not optimized for having something to say.

---

Why both of these exist

Everything else in the hub waits for you to ask. These two do not: they run on their own and put a small number of things in front of a person. One catches the contradiction nobody would have compared. The other catches the item that would otherwise surface as a crisis in three weeks. Both stop at telling a human, which is exactly where an automated watch should stop.

Key points

The nightly contradiction sweep compares records and files genuine conflicts into Unresolved Contradictions with Status Open: two documents naming different owners, a decision that contradicts an earlier approved one, a deadline that moved while dependent tasks did not, a task called complete with no evidence. Each filing names the sources, the people involved, and the smallest decision that would reconcile them. Sera can never resolve one herself: the service can only create rows in that one database, so a fix always comes from a person. A contradiction a human dismisses does not come back the next night. The Attention Brief is assembled with no model call at all, from plain queries over blocked and overdue tasks, open High-severity risks, decisions with nobody accountable, and anything flagged stale, then ranked by significance and hard-capped so it can never nag. Work contradictions weekly and read the brief daily; both are early warning, not verdicts.