Todo

Todo

• Locate the self-driving car post and identify the SAE-level mismatch text.
• Replace the mismatched “Level 3 is here” framing with SAE Level 2 wording that preserves the milestone framing.
• Verify the edited wording in context for consistency.
• Commit only the files changed for this task.

Review

Updated the post to explicitly frame current consumer systems as SAE Level 2 while keeping the forward-looking milestone message toward SAE Level 3/4.

Navigator Theory Post

• Locate the Navigator Theory tab through browser/computer use and capture the source material.
• Identify the blog post format and choose the target filename/title.
• Draft a concise post based on the Navigator Theory material.
• Verify the new post renders or at least passes the repository’s available checks.
• Update this todo with results and commit only this task’s changes.

Review

Captured the “Navigator theory” Google Doc text from Chrome, created a Jekyll post expanding it into a concise philosophy essay, and verified the post front matter/body with Ruby because Jekyll is not installed in this repo environment.

State of AI Google Doc

• Locate the “State of AI, Jun 17, 2026” Google Doc tab.
• Identify the three GitHub links for the Chrome extension versions.
• Add those links to the post and revise the post text.
• Verify the Google Doc reflects the requested revisions.
• Update this todo with results and commit only this task’s local changes.

Review

Located the open Google Doc in Chrome, revised the “State of AI, Jun 17, 2026” draft, and added the three GitHub extension links: local LLM, Codex, and Claude Opus. Verified the edited document by copying the updated Google Doc content back out of Chrome and confirming the revised ending plus all three URLs were present.

Google Docs to Blog Pipeline

• Inspect the current post template and publishing conventions.
• Design a minimal pipeline that converts Google Docs exports into Jekyll posts without adding unnecessary services.
• Implement the pipeline script and supporting documentation.
• Verify conversion, front matter, filename generation, and repository checks.
• Add a review section with results.
• Commit only the pipeline-related changes.

Review

Added a scripts/gdoc_to_post.py CLI that converts Google Docs .docx exports through pandoc, with public Google Doc URL, zipped HTML export, and saved HTML fallback support. The pipeline writes Jekyll posts with front matter, slugged filenames, title-heading cleanup, and image copying into /assets/<slug>/. Documented the workflow in README.md, added focused unit tests, and added a minimal .gitignore for Python/Jekyll generated files.

Verified with python3 -m unittest discover -s tests, python3 -m py_compile scripts/gdoc_to_post.py tests/test_gdoc_to_post.py, git diff --check, the Ruby YAML front-matter check, and a .docx dry-run smoke test generated via pandoc. jekyll is not installed locally, so a full Jekyll build was not run.