Skip to content

docs: reposition README for agentic-as-primitive-layer story#90

Merged
tnez merged 1 commit into
mainfrom
readme-positioning-update
Jun 4, 2026
Merged

docs: reposition README for agentic-as-primitive-layer story#90
tnez merged 1 commit into
mainfrom
readme-positioning-update

Conversation

@dottie-weaver
Copy link
Copy Markdown
Collaborator

Repositions the README to tell the project-level story instead of listing commands.

What changed:

  • Headline: "In-loop primitives for agents that run more than once"
  • New "Why this exists" section — positions the five primitives as answers to real production-agent needs (persistent memory, on-demand skills, state-machine workflows, in-loop tasks, coherent personas)
  • New "What Agentic is not" section — mirrors the framework-boundaries memo (Extract production host lessons into Agentic framework shape #87/docs: draft framework boundary memo #88), sets expectations, and links to the full doc
  • Simplified quick start — removed spores init compat alias from the getting-started flow (the compat note at the top covers it)

Why: Bridge notes "0 stars — README and landing page story are the gap, not capability." The current README is a CLI reference with a tagline. This rewrite tells the story of why someone should use Agentic and what it deliberately does not try to be, which is the positioning from the #87 boundary memo.

Refs #87

Headline change: 'In-loop primitives for agents that run more than once.'
Adds 'Why this exists' and 'What Agentic is not' sections that mirror
the framework-boundaries memo (#87/#88). Links to the full boundary
design. Simplifies quick start by removing compat alias from the flow.

The package description remains 'Executable toolbelt for agent
self-improvement' in package.json (that's a fine npm tagline). The
README now tells the project-level story.

Refs: #87
@tnez tnez merged commit 245fe1e into main Jun 4, 2026
1 check passed
@tnez tnez deleted the readme-positioning-update branch June 4, 2026 13:41
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