Welcome to the Sculptor blog

We are starting a simple public blog: fixed markdown files in the repo, rendered as readable articles on the marketing site.

Why markdown in the repo

For now, posts are not stored in a database. Each article is a .md file under content/blog/ with a small YAML header (title, description, publishedAt, optional author). That keeps publishing predictable for a small team:

1. Add or edit a file.
2. Deploy the app (Docker rebuild when needed).
3. The post appears on /blog and at /blog/your-slug.

Later you can generate these files from agents or a CMS; the detail page already expects markdown bodies.

What you will find here

• Strategy and execution — how specialist coaching and Agentic runs fit together.
• Workspace practice — library outputs, combined documents, and collaboration patterns.
• Product notes — deeper context than the short bullets on What's new.