Skip to content

docs: LinkedIn launch post, CHANGELOG, 5-way comparison + live journey baseline - #14

Merged
RyanAlberts merged 2 commits into
mainfrom
claude/launch-docs
May 30, 2026
Merged

docs: LinkedIn launch post, CHANGELOG, 5-way comparison + live journey baseline#14
RyanAlberts merged 2 commits into
mainfrom
claude/launch-docs

Conversation

@RyanAlberts

Copy link
Copy Markdown
Owner

What's in here

  • docs/launch/LINKEDIN.md — the missing LinkedIn launch draft (native-video post + posting playbook for the operator/accelerator audience).
  • CHANGELOG.md — Unreleased section capturing all the Keel work + the 0.1.0 baseline.
  • README comparison table — expanded from Atlas-only to Atlas / LegalZoom / Clerky / Firstbase (4 competitors), with a "verify current terms" caveat and a fixed TOC anchor.
  • Live end-to-end journey baselinetests/baselines/claude-2026-05-30-journey.md + honest PARITY.md update.

Live e2e results (first full SDK run of the Founding Journey)

✅ All 5 steps ran; synthesized packet (19,556 chars) has all 6 required sections; all 9 artifacts generated. The deterministic compliance-deadlines.ics verified correct: 83(b) postmark 2026-07-01 (formation + 30 days), DE franchise tax 2027-03-01, valid RFC-5545.

⚠️ One real defect found (filed as #13): the Legal Docs specialist failed mid-run with an SDK error. The journey degraded gracefully — synthesis flagged it and marked docs "NEEDS ATTORNEY DRAFT" instead of fabricating. PARITY records this honestly.

Suite: 109 tests green, ruff clean.

Closes nothing; relates to #13.

https://claude.ai/code/session_01T3HcA2F6EaxyQeNUjbBuVn


Generated by Claude Code

claude added 2 commits May 30, 2026 23:10
- docs/launch/LINKEDIN.md: native-video launch post + posting playbook.
- CHANGELOG.md: Unreleased section capturing the Keel work + 0.1.0 baseline.
- README: expand the comparison table from Atlas-only to Atlas / LegalZoom /
  Clerky / Firstbase, with a 'verify current terms' caveat; fix the TOC anchor.
…-doc failure

First full live run of the Founding Journey via the real Agent SDK path
(enabled by the root permission_mode fix). All 5 steps ran, the synthesized
packet (19,556 chars) has all 6 required sections, all 9 artifacts generated,
and the deterministic .ics verified correct (83(b)=2026-07-01, DE FT=2027-03-01).

Real defect surfaced: the Founding Legal Docs specialist failed mid-run with
an SDK error; the journey degraded gracefully (synthesis flagged it + marked
docs NEEDS ATTORNEY DRAFT instead of fabricating). PARITY updated honestly;
baseline captured under the partial-failure condition. Bug tracked separately.
@RyanAlberts
RyanAlberts merged commit 34ac6e9 into main May 30, 2026
12 checks passed

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces comprehensive documentation updates, including a detailed CHANGELOG, an expanded comparison table in the README, and a live-run verification baseline for the Founding Journey orchestrator. Additionally, a draft for a LinkedIn launch post has been added. The review feedback points out a minor discrepancy in the baseline document where the compliance calendar filename is referred to as business-compliance-deadlines.ics instead of compliance-deadlines.ics.

| **Initial Board Resolutions / Unanimous Written Consent** | (NEEDS ATTORNEY DRAFT) | Have attorney draft; Ada and Ben sign on June 1; file in corporate minute book; Mercury will require the bank-account authorization resolution |
| **EIN Confirmation (IRS CP 575 equivalent)** | (NOT YET — apply June 1) | Apply online June 1 morning; save the online confirmation PDF immediately; do not wait for mailed CP 575 (takes 4–6 weeks) |
| **California Statement and Designation by Foreign Corporation** | (NOT YET — file after CA foreign qualification) | File with CA SoS within days of June 1; download stamped copy for Mercury bank application |
| **Compliance Calendar (.ics)** | ✅ READY | Save as `business-compliance-deadlines.ics`; import into Google Calendar, Apple Calendar, or Outlook; 20 events with 7-day-out reminders through Q1 2027 |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

There is a discrepancy between the filename of the compliance calendar generated by the orchestrator and the filename mentioned in this baseline document. The orchestrator in journey.py generates the file as compliance-deadlines.ics (and it is also referenced as such in PARITY.md), but here it is referred to as business-compliance-deadlines.ics. Updating this to match the actual generated filename will prevent confusion for users reading the baseline.

Suggested change:

| **Compliance Calendar (.ics)** | ✅ READY | Save as `compliance-deadlines.ics`; import into Google Calendar, Apple Calendar, or Outlook; 20 events with 7-day-out reminders through Q1 2027 |

RyanAlberts added a commit that referenced this pull request Jun 12, 2026
…ine (#14)

- docs/launch/LINKEDIN.md: native-video launch post + playbook
- CHANGELOG.md: Unreleased (Keel work) + 0.1.0 baseline
- README: comparison table expanded to Atlas / LegalZoom / Clerky / Firstbase
- Founding Journey: first live end-to-end Claude baseline captured; PARITY updated honestly (legal-doc specialist failure tracked as #13)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants