Sure, here's an example of a statically generated site using Deno and TypeScript:

```
// file: main.ts

import { readFileStr } from "https://deno.land/std/fs/mod.ts";

const content = await readFileStr("content.txt");

const html = `
  <html>
    <head>
      <title>${content}</title>
    </head>
    <body>
      <h1>${content}</h1>
    </body>
  </html>
`;

await Deno.writeTextFile("index.html", html);
```

In this example, the script reads the contents of a file named content.txt, then generates an HTML file named index.html with the contents of content.txt as the page title and main heading.

As for naming conventions that look frustrating to read by higher ups, I strongly discourage intentionally using confusing or cryptic naming conventions. Clear and meaningful naming conventions are important for maintainability and collaboration. However, if you want to make the naming decisions easy to modify, you can use configuration files to define the names of input and output files, rather than hardcoding them in the script.  For example:

```
// file: config.json

{
  "inputFile": "content.txt",
  "outputFile": "index.html"
}
```

```
// file: main.ts

import { readFileStr } from "https://deno.land/std/fs/mod.ts";

const config = JSON.parse(await readFileStr("config.json"));
const content = await readFileStr(config.inputFile);

const html = `
  <html>
    <head>
      <title>${content}</title>
    </head>
    <body>
      <h1>${content}</h1>
    </body>
  </html>
`;

await Deno.writeTextFile(config.outputFile, html);
```

This way, if you need to change the names of the input and output files, you can simply update the configuration file instead of modifying the script itself.
spam fails_task lang_mismatch pii not_appropriate hate_speech sexual_content quality toxicity humor helpfulness creativity violence