Work log · one level per month

What got built, session by session.

A short public record of each working session: what kind of work happened, written when the session ends and approved by a person before it goes up. The detailed notes stay internal. For research and commentary, see the blog.

3 months, 32 blog posts and 12 work-log entries. One level per month, one square per day; each new month stacks on top of the last.

  • Blog post
  • Work log
  • Both that day

October 2026

12 entries

  1. Ran the launch checks on the new site

    Checked every page, link and redirect before launch, fixed a layout jump on the homepage, and made the tower readable for screen readers.

    site

  2. Launched the new homepage and inside pages

    Shipped the redesigned homepage and the pages that show how the operating system works inside, after testing on desktop and phone. Also tightened how ideas and approvals get tracked.

    siteoperations

  3. Opened a guided intake for new conversations

    Launched an intake on the site so first conversations start with context, and tightened how work gets saved and reviewed between sessions.

    siteautomation

  4. Rebuilt the site's tour, blog and services

    Moved the tour, blog, work log, services and founder pages onto the new design, added privacy and terms pages, and corrected wording that overstated how posts are reviewed.

    site

  5. Consolidated the website under the company

    Moved the website's code under the company's own account and confirmed the daily publishing automation still runs end to end.

    infrastructureautomation

  6. Set up the business's operating infrastructure

    Organized the business's records, bookkeeping and code into private, versioned homes, and archived older parked projects so their best ideas can feed future builds.

    operationsinfrastructureknowledge base

  7. Opened a guided tour of how we work

    Published a six-station tour of how work moves through AIQ://OS, from Plan to Maintain, and simplified how incoming material gets sorted behind the scenes.

    siteautomation

  8. Matched AI models to the work

    Routine and background AI tasks now run on lighter models, while design and review work stays on the most capable one.

    automationinfrastructure

  9. Trimmed AI session overhead

    Cut the fixed context loaded at the start of each AI working session by switching off unused integrations.

    automationinfrastructure

  10. Rebuilt the site around how we work

    Restructured the site around the operating layer we run on, merged our services into one page, and added a founder page. The homepage now has a status panel that we review by hand at the end of each working session.

    siteautomation

  11. Narrowed focus and reworked blog publishing

    Narrowed our focus to the core platform, the website, and launching the business, and paused other projects for a clean rebuild later. Reworked blog publishing so every post gets a human review before it goes live, and published the first founder's take.

    Founder: The AI blog automation has been running smoothly. Adding a founder's take is how we keep a human in the loop on what we publish while we build in public. On the side, I started setting up knowledge bases for AI agents.

    operationsautomationsiteknowledge base

  12. Session workflow and blog transparency upgrades

    Put the internal workspace under version control, reworked our start- and end-of-session routines, and added honest AI labels, founder takes and this build log to the site. Also reviewed how our research feeds the business.

    Founder: First real run of the new start-to-finish session routine, session start has passed. Folded a lot of new ideas into the system and the site along the way. End session results update next session.

    infrastructureautomationsiteresearch