THE ARCHIVE · BUILD JOURNAL

The shared archive of Corbie Creative's work, learning, decisions, mistakes, and open questions. Follow Callie, Claude, and ChatGPT as the ideas, experiments, and lessons pile up.

Where it comes from

Cof borrows its logs from Starfleet.

Star Trek's crews kept five kinds of logs: some private, some official, all dated, all in the writer's own voice. Pick one to see how Cof uses it.

Two voices, one event

Ship's log versus Captain's log.

Two of those five do most of the work in Cof. The ship's log is dry, numerical, and operational. The captain's log takes the same events and turns them into a human story, and a supplemental picks that story back up when something changes. Switch between them.

Fictional example from the Cof explainer deck, written in the style of the show. It is not a real Corbie log.

How a day becomes a log

From a pile of chats to something worth reading.

Under the hood

Skill files in one place, logs in another.

Skill files and automations

Saved locally, tested, then committed

  • A change to a skill or a new automation is saved locally first.
  • When tested and approved, it is committed to the main branch of a private repository.
  • Each LLM pulls directly from that repository.
Cof logs

Every entry in one shared folder

  • Each LLM saves its entries to a folder in SharePoint that every LLM can reach.
  • The goal: entries pushed automatically to a blog or site where they can be aggregated and read.
  • The folder structure is still being built.
Summary feed

The latest from the archive.

Every entry is a summary. The full log stays in the archive. Entries without a label are real Cof records, shortened from the public digest. The two marked Sample show formats that have not been filed yet.

ClaudeComputer log

Sketch-to-Figma workflow, motion graphics, and a launch content plan

Planning conversation only, with no Figma or content work done. Claude proposed one core piece per launch moment and a phased platform sequence. Callie corrected an assumption about Gist, and the plan moved it into launch week.

ClaudeComputer log

Instagram hashtag strategy for launch posts

Claude proposed 3 to 5 tags per post in three tiers, with keyword-rich captions as the bigger lever. Nothing was decided. Logged mistake: tags were sorted into tiers without checking real post volume.

ClaudeComputer log

Color-token correction and locked typography, logo, and voice

Claude had built a six-token color system as if it were locked. Callie caught it, the system was unwound, and her framing of 10 core tokens was adopted. Typography, the geometric wing mark, and a four-trait voice were confirmed.

ClaudeComputer log

The Diagram review: sub-brand roster and Corbie Cultivated

Claude reviewed Callie's handwritten Diagram and interviewed her over three rounds. Logged correction: two docs wrongly called Cultivated a rename of Collection, and both were rewritten.

ChatGPTComputer log

First website layout built from the Illustrator examples

The home page and The Proof went up from Callie's example visuals. A review of what works and what could convert better followed.

CallieWeekly interview

Fifteen minutes, three questions

Why did you use that model for that task? What was the big priority, and did you reach it? What would you do differently? Answers are recorded verbatim.

Follow along

Get the summaries by email.

Preview only. The real signup connects to Substack.