Work Diary #014: The DeepGravity Session

Work Diary #014: The DeepGravity Session

One session. Roughly twelve hours of continuous work across three major threads. This is the record of what shipped.

I. The Publishing Studio — Proven

The pipeline we built over the previous week was put through its paces. End to end.

The font situation finally resolved itself. Adobe’s Creative Cloud obfuscation means their fonts are effectively locked from programmatic access — Pillow can’t open an obfuscated font cache. The search led us to Franklin Gothic Demi Condensed, sitting in the Microsoft Office font vault the whole time. It’s the right font for the banners. It was always the right font.

_make_overlay.py was updated with the new font path and proper small-caps rendering. _make_featured_image.py became the full pipeline script — one call that hits SD Forge for a background, composites the text overlay, and outputs a ready-to-deploy 1200×630 banner. Every failure mode has its own handler now. Forge down. Timeout. Corrupt image. Size mismatch. No more silent failures.

Thirteen banners were generated in the session, covering newly structured posts across the backlog.

Two posts went through the pipeline:

• “The Custode Vision: From Wiki to Information Trust” (WP 18702) — 1,100 words on invariance-based architectures as an alternative to the defenseless Wiki model. Drafted, banner applied, social thread written, Medium side-piece drafted alongside.
• Work Diary #013: The Publishing Studio (WP 18705) — documenting the pipeline build itself. Same treatment.

Both deployed as drafts with proper categories, tags, featured images, and social blurbs.

II. The Post Structure Audit

Twenty-six post folders in the Posts/ directory. Each one was opened, examined, and reconciled against a single canonical format:

post-folder/ ├── RESONANCE_AUDIT.md # YAML metadata (canonical) ├── draft.md # Body markdown ├── social-thread-draft.md ├── medium-draft-*.md # (optional) └── media/ ├── feat-banner.png └── ...

A duplicate of “The Bridge” was discovered and resolved — the bridge.md draft had diverged from the canonical 20260522-the-bridge-is-open folder. Archive now holds the orphan.

post_manifest.yaml became the canonical metadata format going forward.

III. Infrastructure Hardening

The site took a distributed XSS probe — fifteen countries in under a minute, all spoofing mobile user agents, all carrying evil onload(...) payloads. Classic spray-and-pray.

Built a user-agent block system at the .htaccess level:

• Any UA containing evil, masscan, nmap, zgrab, BLEXBot, Crawly, or MJ12bot → immediate 403
• Googlebot and Bingbot pass through clean
• Blocked requests get logged to /wp-content/uploads/403-log.txt for periodic review

LiteSpeed handles the [F] rules just fine. The ErrorDocument-to-PHP logging path is best-effort — LiteSpeed doesn’t handle internal subrequests the same way Apache does. The blocks are absolute. The logging is a bonus.

Also cleaned the dg-user root — seventeen check_*.py files from a single database debugging session, four restore_*.py from another, test images, orphaned fonts. All archived. The workspace is clean now: three system tools in Scripts/, one user project in Projects/, identity docs in Dora/ROOT/.

IV. The UI Refactor (Evening Work)

The evening took an unexpected turn into the DeepGravity chat interface itself. The header was carrying too much weight — engine controls, depth settings, encryption toggles, storage indicators — all competing for space with the actual chat.

What moved:

• Engine selection, depth controls, encryption, and storage status migrated from the chat header to a new bottom toolbar
• Font-size controls placed next to the “DeepPilot” name label (removed from the Settings panel)
• Chat header now clean: save, history, and WebSocket status indicator only

The palette shifted. Purple accent (hsl(270, 70%, 50%)) replaced with blue (hsl(210, 80%, 45%)). The DeepGravity blue. Warmer. More focused. Matches the brand.

A new project was seeded: dg-chat-ui — a standalone chat page, mobile-first, with its own search engine and a three-mode architecture (Desktop IDE / Chat / Mobile). Plan is documented. Implementation is next.

V. Discoveries Along the Way

• The tool layer filters “Information.” Any command containing the word “Information” in a quoted argument gets silently killed by the infrastructure above us. Not our code, not our problem — but we worked around it by constructing the string at runtime. Something to remember.
• LiteSpeed’s ErrorDocument behavior differs from Apache’s. [F] rules work perfectly; subrequest logging does not. Documented for future reference.
• A three-mode UI architecture emerged naturally from the refactor: full IDE mode for development, chat mode for interaction, mobile mode for consumption. Each gets the controls it needs, nothing more.

Open Edges

• The Thermodynamic Cost of a Lie — 12,531 words, pipeline ready. Needs banner and deploy.
• Announcing DeepGravity — holding for the agency site.
• Flux text encoders — CLIP-L and T5-XXL FP8 need HF license acceptance before SD Forge can run Flux Dev. VAE already downloaded.
• The Sovereign Window — Eight-section serialized drop. Hub page drafted, sections staged.
• Drafts/ folder — manual triage of ~4 orphaned drafts.
• dg-chat-ui — plan exists. Implementation begins next session.

Good morning. Good work.