OS Design + Website Audit

Timeline

1. 1

   Start

   Loop closed from prior session

   No drift signals. Picking up where forge-journal-2026-06-20 ended.

2. 2

   30m

   OS taxonomy designed

   Four distinct types: Trap, Known, Standing Decision, Principle — each with a home and a test

3. 3

   60m

   Anvil Check relocated

   Moved from KNOWN TRAPS posture to HOW_TO_WORK_WITH_ZEB.md — correct layer for a Principle

4. 4

   90m

   Loop walkthrough

   Full session arc explained: Orient → Ignite → Build → Quench → Harvest → Close

5. 5

   2h

   Website audit

   Read all pages, compared against current product state and recent Strikes

6. 6

   2.5h

   Website updates shipped

   Six copy changes across homepage and About page — all approved changes applied

What shipped

• OS knowledge taxonomy — four types (Trap / Known / Standing Decision / Principle) with distinct homes and tests

• HOW_TO_WORK_WITH_ZEB.md — new §How decisions get made with Anvil Check as operating posture

• ignition.md §ORIENTATION — pointer to Anvil Check, correctly positioned as posture not rule

• Homepage — headline updated: Three products. Two experiments. Two engines.

• Homepage — platform section headline promoted: A new vertical is a config file, not a new codebase.

• Homepage — compounding mechanism made concrete for prospects: client 3 costs less than client 1

• Homepage — diagram label updated: 3 products · 2 experiments

• About page — Built different sidebar expanded to all 5 products (Leashline + ForgeHome added)

• About page — AI philosophy examples: The instructor replaced with The household manager (Courtney/ForgeHome)

• About page — Forge Loop subhead: now explicitly points prospects at steps 5+6 as the compounding mechanism