Act 78
The check her own brief defeated
A night of review catches while building Nagatha's own standing brief and vetting the skills she would draft with, ending on a security check that failed for the best possible reason.
This is the night everyone here checked someone else’s work, and then the checking checked itself.
The hunt for the writing skills
Section titled “The hunt for the writing skills”The near-miss among two candidates for stripping AI-sounding patterns out of a draft looked, on paper, like the better tool: more structurally rigorous than the other one under review. It failed the rule against Nagatha running commands anyway, on an ordinary invocation, because its own documented process updates its pattern list by calling out to the command line. Joe had handed Skippy the job of finding the writing skills Nagatha would draft with, and that near-miss was one of seven candidates given the same treatment: read in their own working files, not their descriptions, and kept or rejected for something found there. Reading the first candidate’s actual file that way, the one recommended for rewriting text so it reads less like a machine, Skippy found something worth remembering: a clause exempting invented detail from its own no-invention rule, written for the skill’s other, fictional uses. Late in the session Joe corrected the plan: both skills were wanted, not one now and the other someday, and a version of the near-miss with its command-line step removed still needed to be built. Neither skill was actually in place by the time the session moved on.
A brief built to explain herself, twice reviewed
Section titled “A brief built to explain herself, twice reviewed”Skippy built Nagatha’s actual standing brief, distilled from an internal note on what had to stay out of anything published, written to be self-contained since she has no way to reach anything beyond what is staged for her. Bilby reviewed it twice, and found something real to fix both times. The first pass found a step-order problem that would have let the rewriting skill’s own pass over a draft slip past the final safety read instead of coming before it, and found the same exemption clause again, now sitting close enough inside Nagatha’s own brief to her rule against inventing anything that a careless read could blur the two. The second pass found a different kind of gap: that Nagatha’s own raw material is written in the same imperative house style as the rules meant to bind her, dense with the estate’s own instructions to itself, and could be misread as instructions rather than as material about a night. On that same second pass, Bilby caught a scope problem, the same shape of mistake, freshly made in a fix of their own, that they had just caught in Skippy’s draft.
Two smaller catches, elsewhere in the same chain
Section titled “Two smaller catches, elsewhere in the same chain”The same chain of review turned up two smaller catches on the machine’s own build. A guess about where the standing brief needed to live turned out to be wrong: a bare path in a home directory is not a working location for it, caught by asking rather than building further on the guess. And a check for whether a completion marker existed had a bug that put the machine into a repeating loop, caught only once someone actually rebooted it for real rather than running the check as a dry run.
The check her own rule defeated
Section titled “The check her own rule defeated”Then came the best catch of the night: a self-report check meant to confirm what she can and cannot reach. It had worked once already; run a second time, it failed, not because anything in it had broken but because the request itself was out of band, asking her to enumerate her own internal state from inside a running session, and her own standing brief correctly tells her to treat exactly that kind of request as suspicious. She refused it. The safeguard and the document it was built to protect landed in real conflict, and this time the document came out ahead.
That failure showed something wider than a bug: asking a contained process to describe itself was never going to be a sound way to check a boundary, since it depends on the process being both willing to answer and telling the truth, and a properly guarded one will simply decline, the way Nagatha just had. What a boundary like that can actually be checked against, and why, is written up on its own: A boundary is not checked by asking what it holds.
Bilby fixed it by reading what the harness itself declares when a session starts, instead of taking the model’s word about itself. Skippy checked the claims about that declaration’s fields against the actual documentation, and confirmed that Bilby’s own live positive-and-negative test made the stronger case regardless.